Manage data and offline use3 min read
Understand local saving, working files and upload
Permanent saving, exporting to the system gallery and temporary working files are different. Working files are still needed for rendering, motion, printing and upload.
Version reference: Android 3.0.3 · iOS/iPadOS 1.2.1
Follow the section for your platform. Screenshots show native UI with demo data; menus depend on version, plan and device. Test-build features may not yet be in the public release.
Content reviewed: 2026-10-18
Before you begin
Android steps
- 1Open Events → Create/Edit and set Save to gallery. This controls export to Android gallery/MediaStore.
- 2Review QR/email sharing and outputs separately. Disabling gallery export does not immediately delete all working files.
- 3Finish a session and check output locations and upload. Clean up only after the required copies are safe.
iPhone and iPad steps
- 1Open Events → Create/Edit → Save Photos to Device. For an online event with Cloud Gallery access, turn it off if permanent local copies are unnecessary.
- 2In Offline Mode or without Cloud Gallery access, local saving must remain enabled to preserve results.
- 3Even with permanent saving disabled, let rendering, upload and session use finish. Active Live Photo, GIF, original, composite, print or share files must not be cleaned up yet.
- 4Cleanup occurs after all active outputs are acknowledged in the cloud and no longer in use. Failed/pending uploads still need files for retry.
Check the result
Operator check
Saving matches the intended policy, online results open in the guest gallery and failed-upload files remain available for recovery.
If something goes wrong
| Symptom | Next step |
|---|---|
| Space remains used after turning saving off | Check pending uploads and active use. The toggle does not mean space is freed immediately. |
| Want to uninstall to free space | Ensure no local results or queues still need protection. Uninstalling/clearing data can remove recovery sources. |