Update Your Shopify Theme Without Losing Customizations

Updating a Shopify theme replaces its files with a new version. Whether your work survives that swap depends entirely on where the work lives. Some customizations copy across untouched; others are part of exactly what gets replaced. Once you know which is which, updating stops being a gamble.

This is the hub for the whole topic. It explains what an update actually does to your files, the one rule that predicts what survives, and where to go next for the specific task you are facing — backing up first, diagnosing code that vanished, or moving to a completely different theme.

What a theme update actually does

In Shopify's admin, a theme is a bundle of files: .liquid templates and sections, CSS, JavaScript, and a set of settings that record the choices a merchant made in the theme editor. When you "update" a theme — installing a newer version of Dawn, or of a paid theme from the Theme Store — Shopify does not patch your existing files line by line. It publishes a fresh copy of the theme's code from the new release.

That distinction is the whole story. A version-controlled merge would try to keep your hand edits and layer the new code on top. A fresh copy does not: the new release's files are what you get, and anything you added by hand to the old copy is simply not part of the new bundle.

Shopify has been improving this. Themes that support the newer update flow can carry your theme-editor settings into the updated version automatically. But that flow moves settings and content — not code you typed into .liquid or CSS files. The gap between "settings" and "code" is where customizations get lost.

The one rule that predicts what survives

You can reason about almost any theme update with a single rule:

Changes you made in the theme editor survive. Changes you made by editing theme files do not. Anything rendered by an app survives, because its code was never in the theme.

Break that into the three buckets it implies:

• Theme-editor settings and content — survive. Section arrangements, text you typed into settings, images you picked, colors, fonts, and the blocks you added and reordered are stored as data, not as code. A supported update copies them over. This includes content in flexible built-in sections like Rich text, Image with text, and Custom Liquid settings.
• Direct edits to theme files — do not survive. A new section file you added to sections/, a snippet you created in snippets/, CSS you pasted into assets/theme.css, or a tweak to theme.liquid are all part of the code the update replaces. They are gone from the new copy unless you re-apply them.
• App-rendered sections — survive. A section delivered by an app through a Theme App Extension lives outside your theme's files. A theme update swaps theme files; it never touches the app, so the section and its settings come through intact.

If you remember nothing else, remember the boundary: editor = data that copies; file edits = code that gets replaced.

Why the wipe surprises people

The reason this catches merchants off guard is that both kinds of change look identical on the live site. A custom announcement bar you built by editing theme.liquid and one you configured in the editor render the same way to a visitor. The difference only shows up months later, at update time, when one survives and the other disappears.

It is also common to forget which changes were code. "I added a size chart" might mean a merchant configured a built-in section (safe) or a developer wrote a new .liquid file (at risk) — and the person clicking Update is often not the person who wrote the code. That is why a written record of your custom files matters more than any single technique.

Where to go next

The cluster guides below take each part of this in turn. Start with the one that matches your situation:

• Does a Shopify theme update delete your customizations? — the direct answer, with the exact list of what copies over and what gets replaced.
• Back up your theme customizations before updating — the duplicate-and-export routine to run before you click Update.
• A theme update removed my custom code — how to get it back — recover work that already vanished, from backups, older theme versions, or Git.
• Switch Shopify themes without losing your work — moving to a different theme, where even editor settings do not automatically carry over.

The workflow that avoids the problem entirely

The disciplined answer is process: duplicate before updating, keep a documented list of every custom file, and re-apply that list to the new theme. It works, and the cluster guides above give you the exact steps.

There is also a structural answer. If a section is something you rely on across theme updates and theme swaps, rendering it from an app instead of a theme file takes it out of the blast radius completely — because a theme update only replaces theme files. That trade-off (survives an update vs. survives an uninstall) is laid out honestly in file-based vs. app-based sections, and it is the approach SectionGuard uses so your sections come through every theme update and swap without a re-apply step.

Neither route is "correct" in the abstract. A one-off tweak on a theme you rarely touch is fine to hand-code and re-apply. A section your store depends on is safer rendered from outside the theme. The guides here help you do either one with your eyes open.