Kaizendex HelpOpen the app

Storage

See how much space Kaizendex uses on this device, adjust the media cache, or clear it — your photos always stay safe in your account.

Every photo you add to Kaizendex lives safely in your account — not just on one device. What you see in Settings → Storage is only the small local copy your device keeps to make browsing feel instant.

Where to find it

Open Settings — the gear icon next to your name at the bottom of the sidebar — then choose Storage. On phone, open the Settings tab in the bottom bar and tap Storage.

What your device keeps

To make feeds, galleries, and Files & Photos load instantly — even offline — Kaizendex keeps two small local copies of each photo:

  • Thumbnails — a small preview of every photo you've ever added, so lists and cards always have something to show. These are tiny and stay on your device permanently.
  • Cached originals — the full-size version of photos you've opened recently (say, in the entry page or a lightbox). These make reopening a photo instant, but they're temporary — freed up automatically as needed.

The Usage on this device section breaks this down, alongside how much total storage Kaizendex is using in this browser.

The Media budget

The Media budget controls how much space cached originals are allowed to use before the oldest ones get freed up automatically — pick 512 MB, 1 GB (the default), 2 GB, or 4 GB.

Kaizendex also automatically caps the cache at a share of your device's available storage, so it never crowds out space you need for other apps — even if you pick a larger budget than your device can spare.

Clear media cache

Want the space back right away? Tap Clear media cache in Storage settings.

Waiting to sync

When you add a photo, it needs to finish uploading to your account before it's safe anywhere else. While that's happening, you'll see a Waiting to sync count in Storage settings.

Photos waiting to sync are kept safe on this device no matter what — they're never cleared or freed up, even under a tight Media budget, because until the upload finishes they're the only copy that exists. If you go offline mid-upload, it just picks back up once you're back online.

Next