Lesson 7 of 7 · 4 min
How edits are saved
Understand that every edit becomes a new child version with the original preserved, find earlier versions, and predict which edits will cost credits.
Video walkthrough coming soon
Edit Studio
Edits never overwrite
Every tool in this chapter runs through one shared edit path, and every save lands as a child of the creative you started from (editArtifactAction, with the new file carrying its parent_artifact_id). The original stays exactly as it was. It works like Save As: the copy is new, the file you opened is untouched. So you can edit as freely as you like without risking the version you already approved, and every output traces straight back to its parent.
Finding earlier versions
Because each edit is linked to its parent, the whole lineage is walkable. After an AI operation the editor reloads the new child in place, and the library grid updates itself over the live connection, so the new version appears without a manual refresh.
One rule for cost
Deterministic work is free; model work bills. Anything that only moves pixels or samples, trimming, cropping, splitting, concatenating, reframing, manual text and shapes, arranging tracks, costs nothing. Anything that calls a model, generative fill, erase, upscale, background removal, caption transcription, and audio isolation and denoise, costs credits and makes a new child.
Plan your edits around it
If you are iterating, get the free deterministic work done first and save the model operations for when everything else is settled. That keeps your credit spend on the steps that truly need a model, instead of on drafts you were going to change anyway.