Version History & Restore
Theme snapshots — rolling back when an edit doesn't work out.
Code editor changes share the same versioning model as visual editor changes: edits accumulate in your draft until you publish, and every publish creates a snapshot you can restore.
Snapshots
Every time you click Publish in the code editor, the previously-live state of your theme becomes a snapshot. Open Themes to see your full snapshot history. Each one lists when it was published, who published it, and a green badge if it's the version currently live.
Restoring a snapshot
Click Restore on any snapshot to make it live again. Your storefront flips to that exact state — every file at the version it had at the time. Restoration is instant and non-destructive — the snapshot you were just on stays in your history, so you can flip back if you change your mind.
Duplicating a snapshot for safe experimentation
Click Duplicate on a snapshot to create a fresh draft based on that version. Your existing draft is untouched. This is the safest way to try a risky edit:
- Duplicate your current published snapshot.
- Edit the duplicate freely.
- If you're happy, publish it. If you're not, just discard.
You'll find this especially useful when restoring an old snapshot for reference but not wanting to make it live yet.
Discarding a draft
If your draft has gone off the rails and you want to start over, use Discard draft from the code editor or the Themes page. Your draft is deleted; the editor reverts to the currently-published state.
This is irreversible — discarded drafts can't be recovered. If you might want the draft back later, publish it first (and restore the previous snapshot to keep the live storefront unchanged).
Working with imported themes
If you imported a theme from a ZIP, the import itself becomes a snapshot. You can restore back to the freshly-imported state at any time, undoing any edits you made afterward.
FAQ
Can I see the diff between two snapshots?
Snapshot-level diff isn't surfaced in the dashboard. For per-file diffs, the practical workflow is to restore the older snapshot into a duplicate (so it doesn't go live), open the file in the code editor, and copy the contents — then compare against your current draft externally.
How long are snapshots kept?
Snapshots are retained indefinitely. Theme snapshot storage is negligible, so there's no time-based deletion to worry about.
I broke the theme so badly the storefront won't render. What now?
Your live storefront keeps serving the most recently published snapshot — broken drafts never reach customers. So your storefront is fine; you just have a bad draft to fix. Either correct the issue in the code editor, or discard the draft and start fresh from the live version.
Can I restore a single file without rolling back the whole theme?
Currently no — restoration is theme-wide. If you only need one file from an old snapshot, the workflow is: duplicate the old snapshot into a new draft, copy the file content out, then go back to your real draft and paste it in.
Updated recently