Shopify Theme Store Updates Are Wiping Global Settings and Logos: The Backup Workflow to Run First

You clicked Update in the Theme Store, previewed the draft, and the logo was gone. Colours back to the default. Fonts reset. If a Shopify theme update lost your settings this year, you are not alone, and you did not do anything wrong.

Since roughly 20 March 2026, store owners and theme developers have been reporting that updating an official Shopify theme wipes previously-set global customisations. One developer thread on Shopify's community forum, posted on 24 March, says Shopify Support described it as a known internal issue affecting several, possibly all, official themes. We have not seen an official Shopify status post confirming a fix at the time of writing. So this is a practical guide: what actually gets wiped, why the update process can behave this way, and the backup workflow we run before touching any client theme.

What a Shopify theme update actually wipes (and what it usually keeps)

The reports are consistent. Global theme settings reset: logo image, colour schemes, typography, button styles, spacing, and anything else under the theme settings panel in the editor. Section content on your templates, such as homepage blocks, product page layout and collection filters, is usually intact. That is cold comfort when your live store is suddenly showing a placeholder header, but it matters for recovery, because the two live in different places.

Global settings live in a single file, config/settings_data.json. Per-template section content lives in the JSON files inside the templates directory. Shopify's own documentation on settings_data.json explains that the current object holds every value saved in the theme editor. If that one file is swapped out or fails to merge, your whole visual identity resets while the page content survives. That is exactly the pattern people are describing.

Why a Theme Store update can wipe customisations

A Theme Store update does not patch your live theme in place. According to Shopify's help centre, the update is added to your draft themes as a new copy of the latest version, and Shopify then attempts to copy your theme editor changes into it: theme settings, section layout and content edits. Code edits that cannot be reconciled are dropped, and you get a message saying the code edits could not be included.

So the update is really a fresh install plus a migration step. When the migration step works, you barely notice. When it fails, you get a clean theme with default settings. The reports since March suggest that the settings portion of the migration is failing intermittently on official themes, which is why the same update can wipe one store and work fine on another.

The current workaround circulating online is to keep retrying the update until one attempt happens to work. One developer in the forum thread said it could take 5-10 attempts. That is not a workflow. That is gambling with your storefront, and it tells you how thin the advice is right now. The Horizon theme has its own version of this problem, which we covered in customising Horizon without losing your changes on the next update. This piece is the theme-agnostic version.

The backup workflow to run before any Shopify theme update

This is what we do before updating a client theme, bug or no bug. It takes about fifteen minutes and it means a wiped update costs you an hour instead of a week.

Duplicate the live theme. In Online Store, Themes, open the live theme's menu and choose Duplicate. Rename the copy with today's date and the current version number. This is your rollback point and it never gets touched.Export settings_data.json. Open the code editor on the live theme (or the duplicate), find config/settings_data.json and copy the full contents into a file on your machine or in version control. If you use Shopify CLI, run shopify theme pull against the live theme ID so the whole theme, settings included, lands in a git repo.Download the full theme file. Use Download theme file from the theme menu. You get a zip emailed to you. Shopify can already restore from a duplicate, but a zip sits outside the store and survives anything that happens inside it.Screenshot the theme settings panel. Logo, favicon, every colour scheme, typography, buttons, layout and cart settings. Boring, but if you have to rebuild by hand this is what you rebuild from. JSON is precise; screenshots are fast to read.Record the custom code. List every file you or an agency edited directly. Snippets added as separate files usually copy across. Edits to existing theme files frequently do not. Knowing which is which before you update saves a lot of searching after.Update into a draft, never straight to live. Add the update to draft themes, open it in the editor, and compare against your screenshots section by section before publishing.

Once the update is in a draft and you can see the settings were wiped, you have two routes. The quick route is to paste your saved settings_data.json back into the draft, provided the theme's settings schema has not changed between versions. The careful route is to rebuild the global settings by hand from your screenshots, which is tedious but guaranteed to match the new schema. For a minor version bump, the paste usually works. For a major version jump, expect to rebuild.

A theme update is a fresh install with a migration step bolted on. Plan for the migration step to fail and you will never lose a logo again.

Why the retry advice is worse than it looks

Each failed attempt leaves another draft theme in your library. Shopify caps unpublished themes at 20 on most plans, so ten failed tries can fill the quota, block further duplicates and leave you unsure which draft actually worked. Worse, a store owner who publishes a half-checked draft late on a Friday is not shipping a theme update, they are shipping a conversion problem: a missing logo and default colours on a brand that spent years earning trust. Most Shopify brands do not have a traffic problem, they have a conversion problem, and a broken header makes it worse overnight. If you do retry, delete each failed draft first and only compare against the dated duplicate you made at the start.

When to tell a client not to self-serve the update

Theme updates are marketed as a one-click job, and for a stock theme with no code changes they usually are. We tell clients to leave the update to us when any of the following is true:

The theme has direct code edits, custom sections or snippets added by a developer. These are the edits most likely to be dropped silently.Apps have injected code into theme files rather than using app blocks or app embeds. The update may strip them and break checkout trust badges, bundles or reviews.It is a major version jump (for example, 10.x to 15.x) rather than a point release. The settings schema has probably changed and a paste-back will not line up.It is peak season. A November theme update on a UK store heading into Black Friday needs a staging check, not a hopeful click.The store has multiple markets or languages. Translations and market-specific content live in their own files and need checking separately.

None of this means you should stop updating. Theme updates carry performance fixes, accessibility improvements and new sections you will want. The question is who runs them and how. For most established stores the answer is a short, repeatable process run by someone who has done it a hundred times, which is what our Shopify support and maintenance service covers month to month. If you are weighing whether an update is even worth it versus a fresh build, read when to redesign vs optimise your Shopify theme first.

A note on the wider Shopify theme update bug in 2026

The settings wipe is not the only update problem reported this year. A separate community thread from May 2026 describes the Update theme option disappearing for some Theme Store installs, with Shopify saying a backend fix was in progress with no ETA. Shopify also tells theme partners that automatic updates only run when every theme file, other than settings_data.json and the template JSON files, is in its original state. In plain terms: the more you have customised, the more the update has to do, and the more it can get wrong. The fix is not an app or a trick. It is a backup habit that assumes the migration will fail.

The takeaway

Before you click Update on any Shopify theme: duplicate the live theme with a dated name, save a copy of settings_data.json, download the theme zip, and screenshot the theme settings panel. Update into a draft and compare before publishing. If your theme carries custom code or you are heading into peak, hand it to someone who does this weekly.

Uncover Commerce is a senior-only Shopify agency based in Glasgow, working with brands across Scotland, the UK and internationally for over 12 years. If you have already lost settings to an update and want them restored properly, or you want theme updates handled as part of a conversion growth retainer rather than as a Friday afternoon gamble, get in touch and we will take a look at your theme first.