Saving to output

Everything else in the editor is reversible and stays in a stash. Save to output is the one action that changes your actual deliverable. It takes the version you’re happy with and promotes it over the canonical output file.

What it does

Click Save to output (the purple button with the save icon) and Piixie:

Regenerates one more time if you have unsaved edits, so the saved file matches the list exactly.
Promotes that version over the real output file — the one in your output folder.
Updates the stored replacement table for the run so history reflects your edits, not just the original detection.

After this, opening the output file (or revealing it in Finder) shows your edited result. The history entry for the run now carries the entries as you left them.

When to save

There’s no autosave to your deliverable — that’s deliberate. Save when you’ve finished reviewing and you’d be comfortable sending the file. Until then, edit and regenerate as much as you like; nothing leaves the stash.

Closing with unsaved changes

If you close the window (or press ⌘W) with edits that aren’t saved to output — including a method switch you refreshed but didn’t promote — Piixie asks:

Save & close — promote the current version, then close.
Discard — close and drop the unsaved edits.
Cancel — keep the editor open.

So you can’t lose work by reflex-closing a window.

Saving from the versions list

You can also promote any version directly from the Versions dropdown in the status bar — pick it and it becomes the output. Handy when you generated several attempts and the one you want isn’t the most recent.

After saving

The output file is now your edited version. From here:

Send it wherever the original couldn’t go.
Promote its replacements into a dictionary if you want the same fake values reused across documents.
Save your edits as a template to apply the same treatment to the next document of this shape.