Run a photo session3 min read

Choose originals, Live Photo and slideshow outputs

Composite photos, originals, Live Photos, GIFs and slideshows serve different purposes. Enable only the outputs the event needs to control processing time and file size.

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

Prepare local working space and test the camera source. Original/RAW terminology in this workflow does not promise sensor RAW files such as DNG/CR3.

The guest journey — Workflow diagram. Optional steps depend on event configuration.

Android steps

1Open Events → Create/Edit and review offered outputs such as originals, GIF or motion.
2Select outputs, save and run a capture. Inspect the composite and original files separately.
3For motion/GIF, open and play the result. If cloud sharing is enabled, also check playback in a guest browser after upload.

Android output and save-to-gallery settings. Native UI on a physical Android tablet with demo data.

iPhone and iPad steps

1Open Events → Edit and choose outputs. For Live Photo, follow the displayed countdown and camera-support requirements.
2Run a session with gentle movement. Inspect the still, motion/Live Photo pair, GIF or slideshow that you enabled.
3If motion fails but the still succeeds, keep the available still and inspect the processing message. Do not repeat the whole session unnecessarily.
4When permanent saving is disabled, working files are still needed until processing, upload and active use finish.

iPad event, offline and saving form. Native SwiftUI UI on iPad Simulator with demo data.

iPad Result. Native SwiftUI UI on iPad Simulator with demo data.

Check the result

Operator check

Every selected output opens; motion actually plays and still photos remain usable.

If something goes wrong

Symptom	Next step
Motion is missing	Check source support, countdown and processing status; a moving preview does not prove a motion file was created.
Upload is slow	Check output sizes/count and the network. Keep local files that have not been acknowledged.

Android steps

1Open Events → Create/Edit and review offered outputs such as originals, GIF or motion.

2Select outputs, save and run a capture. Inspect the composite and original files separately.

3For motion/GIF, open and play the result. If cloud sharing is enabled, also check playback in a guest browser after upload.

Android output and save-to-gallery settings. Native UI on a physical Android tablet with demo data.

iPhone and iPad steps

1Open Events → Edit and choose outputs. For Live Photo, follow the displayed countdown and camera-support requirements.

2Run a session with gentle movement. Inspect the still, motion/Live Photo pair, GIF or slideshow that you enabled.

3If motion fails but the still succeeds, keep the available still and inspect the processing message. Do not repeat the whole session unnecessarily.

4When permanent saving is disabled, working files are still needed until processing, upload and active use finish.

iPad event, offline and saving form. Native SwiftUI UI on iPad Simulator with demo data.

iPad Result. Native SwiftUI UI on iPad Simulator with demo data.

Symptom

Next step

Motion is missing

Check source support, countdown and processing status; a moving preview does not prove a motion file was created.

Upload is slow

Check output sizes/count and the network. Keep local files that have not been acknowledged.