Save Final Photo: Overview

Save Final Photo is an explicit checkpoint. It composites the photos and processing results available at that point into the active layout and writes the session's Final Photo.

The step is useful when the exact save point matters, but it is not mandatory in every photo workflow. FMX for Windows and FMX for iPadOS can prepare final media on demand in common Preview, Print, sharing, and session-end paths.

---

What Is the Save Final Photo Step?

When the step runs, FMX:

• Resolves the current raw photos, AI results, layout assignments, and drawing state
• Applies the active layout's backgrounds, overlays, and branding
• Writes the composited image as the session's Final Photo
• Gives later steps a known file representing the workflow state at this point

It has no settings and no guest-facing screen.

An explicit save also fixes the composition before later workflow activity. If a later AI, Drag & Drop, or Sign & Draw step should change the delivered image, put the checkpoint after that work or save again at the intentional boundary.

---

When Should You Use It?

Add Save Final Photo when you need one of these guarantees:

• A Final Photo file must exist before a Webhook or other immediate file consumer runs
• A branch should preserve the current composition before later choices can change it
• Preview, print, and sharing should all consume the same explicitly saved version
• You want a clear diagnostic boundary between processing and delivery

Place it after all work that belongs in that version of the image:

• After every Take Photo needed by a multi-photo layout
• After the AI batch whose result should appear
• After Drag & Drop Layout assignments
• After Sign & Draw when the drawing belongs in the delivered image

You normally do not need it in video-only, flipbook-only, lenticular-only, scan, survey, or other flows with no Final Photo output.

---

How It Fits in a Workflow

A workflow with an explicit checkpoint can look like this:

1. Live View (Start)
2. Countdown animation
3. Take Photo
4. Live View (Stop)
5. AI, Drag & Drop, or Sign & Draw steps
6. Save Final Photo
7. Preview
8. Print Copies, Email, SMS, QR Code, or Webhook

Multi-photo layouts

Capture every required frame before one Save Final Photo step. Saving after each Take Photo can intentionally create intermediate versions, but it is not required to fill a multi-photo layout.

Branching workflows

If several branches merge into the same finished composition, place one checkpoint after the merge. If branches intentionally produce different final images, give each branch its own checkpoint after its branch-specific processing.

Workflows without the step

Omitting Save Final Photo does not automatically break printing or sharing. The runtimes can materialize final media when those consumers need it and save at the session boundary. Use the explicit step when you need deterministic timing or want to freeze a particular version, rather than adding it only as ritual.

---

Common Mistakes

Saving before AI or drawing work. The checkpoint contains only the state that existed when it ran. Move it after the work that should appear.

Assuming every consumer requires the node. Preview, print, and sharing paths can prepare final media on demand. Add the node when its explicit timing is useful.

Assuming a later change updates an earlier checkpoint. If the guest changes a layout assignment or adds a drawing after the save, run another Save Final Photo before a consumer that needs the revised version.

Using several accidental checkpoints. Multiple saves can be valid, but each should mark an intentional version boundary. Remove duplicates that do not serve one.