How to duplicate a Shopify theme — and when a copy is not a backup

29 July 2026 · 5 min read

To duplicate a Shopify theme: Online Store → Themes, find the theme, open the ⋯ menu next to it and choose Duplicate. The copy appears in your theme library within a few seconds, unpublished, named "Copy of …". That is the whole procedure — and for a one-off safety net before a risky change, it is genuinely the right tool.

The interesting question is the one nobody asks until later: what does a duplicate actually protect you from, and where does the habit fall apart?

What a duplicate contains

A duplicate is a full, independent copy of the theme at that instant — every template, section, snippet, asset and locale file, plus the theme's settings. Nothing is shared with the original afterwards: edit one and the other is untouched. That independence is exactly what makes it useful, and also what makes it easy to forget which copy is the real one.

Rename the duplicate immediately. "Copy of Dawn" tells you nothing in three weeks; "Dawn — before checkout rework, 29 Jul" tells you everything. This is the single highest-value habit in this whole post.

Where duplicating a Shopify theme stops working

The theme library is capped

A store can hold a limited number of themes (20 on most plans at the time of writing). Duplicate before every meaningful change and you hit the ceiling within weeks, at which point you are deleting old copies to make room — usually the oldest ones, which are the ones covering the longest-standing damage.

It only happens when someone remembers

Nobody duplicates before a two-line snippet edit. The habit survives for big, scary changes — which are the changes already partly protected, because publishing a theme leaves the previous one in your library. The small everyday edit, the one with no history at all, is precisely the one that never gets a duplicate.

It captures the whole theme or nothing

A duplicate has no notion of files. To recover one snippet you open both themes in the code editor and copy across by hand, and to know which file to look at you first have to work out what changed — which the admin will not tell you.

Duplicate, export, backup — three different things

These get used interchangeably and they are not the same:

• Duplicate — a second theme inside the same store. Fast, but consumes a library slot and lives or dies with the store.
• Export/download — the theme as a ZIP, or files pulled with the Shopify CLI. Lives outside Shopify, which is its advantage and its risk: it is only as safe as wherever you put it.
• Backup — a dated series of copies with history, taken automatically. The only one of the three that answers "what did this look like last Tuesday?"

A duplicate answers "what did this look like at the moment I remembered to click Duplicate?" — which is a much narrower question than it first appears.

When to duplicate anyway

• Before installing an app that writes to the theme.
• Before a theme update, so you can compare afterwards.
• Before handing the store to a developer or agency for the first time.
• As the working copy for any change at all — edit the duplicate, never the live theme.

The habit that replaces it

Duplicating is a manual snapshot with no schedule, no labels and a hard ceiling. The version of the habit that survives contact with a real store is a copy taken automatically at the moments that matter — when a theme is published, and before anything writes to a theme — kept as history rather than as themes, so it costs no slots in your library.

Auto Theme Sync does that: every file of a theme captured automatically, stored content-addressed so repeat captures of a barely-changed theme cost almost nothing, and searchable by file. See the complete guide to theme backups for what a backup needs to 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.