Skip to content

Photos and files

Your files, or attachments, are the photos, videos, audio, PDFs and other files you add to entries. They are big, so they are kept apart from your data: as real files, once on each device that keeps them, and in Cloud Sync. Cloud Sync keeps 200 MB of files on Free and 50 GB on Pro.

Two entries, Morning run and Running plan, use one photo: one real file, Attachments/2026-10/run-map.png. The database keeps only its record. Our Worker checks each upload first; then it goes to file storage (R2), part of Cloud Sync: every file on Pro, up to 200 MB on Free. The desktop app keeps every original; a linked browser keeps nothing; a browser on its own keeps a small cache on Pro and every file on Free; a phone keeps previews and recent files on Pro and every file on Free.Workouts: Morning runuses run-map.pngNotes: Running planuses the same photoOne real fileAttachments/2026-10/run-map.pngthe database keeps its recordFile storage (R2)Pro: every fileFree: up to 200 MBpart of Cloud Syncour Worker first checksthe size and allowanceWhat each device keepsDesktop appevery original, once,in ~/KaizendexLinked browsernothing: it showsthe computer’s filesBrowser onlyPro: a small cacheof recent files,which you can emptyFree: every filePhone (later)Pro: previews andrecent files, 2 GBdefault; others loadwhen you open themFree: every file
Two entries, one photo, one file. The database keeps only a record of it: name, size, fingerprint and which entries use it.

Add a file

Drag a file onto an entry, or pick one. It shows at once, and it uploads by itself in the background. There is nothing to press and nothing to wait for. A file can be up to 2 GB. If your connection drops or you restart the app, the upload goes on where it stopped.

Example: you drag a 900 MB video of your race onto “Morning run”. It plays from your device at once. On Pro, it is in Cloud Sync a few minutes later, on its own.

A picture for a design (a card skin, a background) is added the same way, with stricter rules, because the app shows it everywhere:

  • Only a PNG, JPEG, GIF, WebP, AVIF or SVG picture, read from what is inside the file. A program renamed cat.png is refused.
  • Up to 10 MB; an SVG up to 2 MB.
  • An SVG keeps only shapes, gradients and text: no scripts, links, styles or pages inside it. One that has them is refused, with the reason.
  • The same picture added twice is kept once.

Where a file goes

You add a photo of your route, run-map.png, to “Morning run”. It is saved as Attachments/2026-10/run-map.png, and the entry links to it as ![[Attachments/2026-10/run-map.png]]. You use the same photo in your note “Running plan”. It is still one file.

  • The database never holds the bytes of a file. It keeps a record: the name, the size, a fingerprint and which entries use it. The read-only database copy holds no files either.
  • In the entry’s file, the photo is that ![[...]] line. Type a line that names a photo in Attachments/, and it becomes a picture in the app.
  • A photo you put into Attachments/ yourself is not added. Photos come in through the app (drag one onto an entry). Its ![[...]] line stays plain text, and the app lists it under Fix these.
  • Moving an entry to another collection never moves its files.
  • Sharing or exporting a collection takes its files along, because the database knows which entry uses which file.
  • Collections set to Database only or Not in the folder keep their files once in the app’s data folder instead.
  • Locked collections keep their files once, encrypted, as .enc files in the folder.

Your 2 GB of files, everywhere

Example: you have 2 GB of photos and files.

Where you use the app Your 2 GB of files
Desktop app All 2 GB on your computer, once, as real files in ~/Kaizendex/Attachments/2026-10/…
Browser, linked to the desktop app Nothing stored in the browser. It shows them from your computer.
Browser only, Pro Small previews and the files you opened lately, in a small cache you can empty. Any other file downloads from Cloud Sync when you open it.
Browser only, Free All 2 GB in browser storage. Cloud Sync keeps 200 MB of them. The app says “1.8 GB of files are only in this browser”.
Phone (later) On Pro: previews and recent files, in a cache you size (2 GB by default). Any other file downloads when you open it. By default, files wait for Wi-Fi. On Free, where the phone can be your one device: every file.
Cloud, Pro A copy of every file, in Cloud Sync. 50 GB is included.
Cloud, Free Up to 200 MB, in Cloud Sync. The other 1.8 GB stay only on your device.
“This device only” collections and entries Their files never go to the cloud, on any plan

“Browser only” means a browser on a computer without the desktop app. On Free, files over 200 MB stay only on your device, and the status mark says so plainly. Your data always syncs. See Offline, and clearing your browser.

Previews and caches

  • A preview is a small copy of a photo, for cards and lists. Previews are free: they never count toward your storage.
  • A cache is a store of files a device keeps so it can open them fast and offline.
  • A browser on its own, on Pro, keeps a small cache of previews and recently opened files. Settings shows its size, and you can empty it.
  • A phone keeps a cache you size, 2 GB by default.
  • A linked browser keeps no cache at all. It shows files from your computer. Each file is sent with “do not keep”, so after you lock the browser again it cannot show a Hidden file from before. A file shows only when you may see every entry that holds those same bytes.
  • A file that is not in the cache downloads when you open it, so it needs the internet.

On a phone

Each phone has a setting: “Use mobile data for: Nothing · Text only · Everything”. The default is Text only. So text changes sync at once, and photos and files wait for Wi-Fi.

“This device only” files

A collection or entry set to This device only never leaves its device, and neither do its files, on any plan. They never upload to the cloud, and your other devices never get them. If you lose that device, you lose them. If the ~/Kaizendex folder sits inside a cloud drive (OneDrive, iCloud Drive, Dropbox, Google Drive), that cloud drive uploads them, and the app warns you. On a computer with the desktop app, your own backup of the ~/Kaizendex folder (Time Machine, File History) keeps a copy, as long as the collection’s folder choice is In the folder.

Stored once, by fingerprint

  • On your computer, a photo is one file, however many entries use it.
  • In the cloud, each file is stored once per account. Files are matched by their fingerprint (checksum), so the same file twice counts once.
  • Your files are never matched with another person’s files.

Sizes and allowances

Rule Number
One file, at most 2 GB
Files in Cloud Sync on Free 200 MB
Files in Cloud Sync on Pro 50 GB
More on Pro +100 GB for about $3 a month, add as many as you need
A phone’s file cache you choose; 2 GB by default
Files on your computer no limit from us: it is your disk
  • Only originals count. Previews are on us.
  • The Trash counts for its 30 days.
  • Data that arrives by itself, such as sleep and heart rate from a service, does not count.

All the numbers are on Storage.

How your files are protected

  • Our Worker checks every upload first (our small cloud program). It checks the size and your allowance.
  • Locked collections keep their files encrypted in your folder, as .enc files.
  • A file is shown, never run. The app shows a file by its id, from your Attachments folder only. Its type comes from its bytes, not its name, so a page named photo.png is never opened as a page. A browser you linked to the desktop app gets a file only after you paired it. A file that only Hidden entries hold stays out until you unlock that browser.
  • In an end-to-end encrypted collection (later), your devices encrypt its files before they upload them. See End-to-end encryption.

Every layer, on every device and in the cloud, is on How your data is protected.

Cleanup

  • A photo you send only in a chat goes to the Trash 30 days after you sent it. The chat then says “photo removed after 30 days”. A setting changes the 30 days, or keeps chat photos forever.
  • A chat photo you also log into an entry (a meal photo logged as food) belongs to that entry and stays.
  • A file that no entry uses any more: what happens to it is not decided yet.