Does Shopify back up your theme?

29 July 2026 · 5 min read

Does Shopify back up your theme? Partly — and the half it does not cover is the half that bites. Shopify preserves whole themes in some situations and preserves nothing at all in others, and the difference is not obvious from the admin. This post lays out which is which.

What Shopify does keep

Your previously published theme

When you publish a different theme, the one that was live is not deleted. It returns to your theme library as an unpublished theme. If a new theme goes live and turns out to be wrong, publishing the old one again puts the store back.

Themes you duplicated

A duplicate is a full, independent copy at the moment it was made. It stays in your library until someone removes it, and it counts against your theme limit.

What Shopify does not keep

A history of file edits

This is the important one. Edit a file in the code editor, save, and the previous content is not retrievable from the admin. There is no per-file version list, no diff view, no undo that survives the page. The same is true of theme editor changes, which save as you go.

Anything about a theme you deleted

Deleting a theme removes it. Treat the confirmation dialog as final, because for practical purposes it is.

A copy of your theme settings over time

Your colours, fonts, and section configuration live in the theme's own config files. They travel with the theme — and they change with it. There is no separate history of "how the settings looked last Tuesday".

The gap this leaves

Put the two lists together and a clear shape appears. Shopify protects you against the rare, deliberate, whole-theme mistake. It does not protect you against the common, small, file-level one:

• A developer edits a snippet and overwrites someone else's fix from last month.
• A theme update replaces a customised section with the vendor's version.
• An app writes into a template and the change is only noticed a week later.
• Someone edits the live theme directly "just this once" and the change is not reproducible anywhere else.

None of those are recoverable from the Shopify admin, because nothing kept the previous version of the file.

What about backup apps?

Apps can close the file-history gap, and several do. Two things are worth checking before trusting one, because they are where these tools differ most:

• Does it capture every file, or only the ones it changed itself? A tool that backs up its own writes protects you from itself, not from your theme.
• Does capture happen automatically, or only when someone presses a button? Manual capture has the same failure mode as duplicating by hand.
• How long is the history kept? If it is shorter than the time you typically take to notice breakage, it expires before it is useful.
• Can it restore a single file, or only the whole theme? Whole-theme-only restores mean reverting unrelated work to fix one snippet.

Note that a backup app needs permission to read your theme files, and to restore anything it needs permission to write them — Shopify grants theme write access separately and reviews each app for it.

How long before you notice?

This is the number that decides how much history you need. In practice breakage is rarely spotted the same day: it surfaces when a customer emails about a broken page, when someone opens the site on a phone, or during the next reporting cycle. If your history is seven days and your average discovery delay is two weeks, the history is decorative.

What to do about it

Two habits close most of the gap:

1. Never edit the live theme directly. Work on an unpublished copy and publish it when it is right — that way the old live theme is preserved for you automatically.
2. Keep a real backup of every file, taken on a schedule or by an event rather than by someone remembering. What matters is that the copy exists before the mistake, not after it.

If you use the Shopify CLI, shopify theme pull gives you a local copy of a theme's files, which is a reasonable manual option for developers. It relies on someone running it, which is exactly the dependency worth removing.

Auto Theme Sync does the second habit for you: it captures every file of a theme automatically when the theme is published, and keeps a searchable dated history. See the complete guide to theme backups for what a backup should contain.

Keep reading

Shopify staging theme: a workflow that does not lose work
How to run a Shopify staging theme properly — where to make changes, how to move them live, and how to avoid the drift that makes staging useless.

Shopify theme version control: what agencies actually use
Shopify keeps no file history of its own. The real options for Shopify theme version control: Git, the GitHub integration, CLI pulls, automatic capture.