Reviewed October 19, 2026

Backing up a Shopify store: what to save and how often

Shopify protects its platform, not your configuration. Products can be exported, themes downloaded, and settings documented, but only if you do it before you need it. A practical backup routine for a small store.

What the platform backup does not cover

The platform keeps its own infrastructure resilient, and your store will be there tomorrow. What it does not keep is your version of the store: the theme as you customized it, the product data as you edited it, the pages, blogs, discounts, and settings accumulated over months. Deletions and bad edits, by staff, apps, or account compromise, are generally yours to recover from, and recovery without a backup means reconstruction from memory.

That distinction surprises founders because the store feels hosted and therefore handled. Think of it like a rented shop: the landlord maintains the building, but your stock, fittings, and records are your insurance problem. A backup routine is a small store's insurance, priced in minutes per month rather than money.

The core backup set

Products and customers can be exported as spreadsheets from the admin, and those exports should be saved, dated, outside the store itself. The theme can be downloaded as a file, and a fresh download after every significant customization is the single highest value backup a merchant can keep, since theme work is the hardest to reconstruct and the easiest to save.

Beyond those two, keep copies of your pages and blog content, your discount code list with its rules, shipping and tax settings as screenshots or notes, and any custom files or code snippets an app or developer added. Navigation menus can be rebuilt from the storefront itself in a pinch, but a screenshot set of the menu structure shortens that pinch considerably.

A rhythm a small team can keep

Match frequency to change rate. Theme downloads after every editing session, product exports weekly for active stores and monthly for quiet ones, and a full settings review each quarter. Automate what can be automated with a backup app if your change volume justifies its cost and its own speed footprint, and otherwise calendar the manual version like any other recurring chore.

Store backups in two places, one of them outside your everyday accounts, with dates in the filenames. Test restoration once: import the product file into a development store or preview the downloaded theme. An untested backup is a hope with a filename. The test takes half an hour and converts hope into a procedure your future stressed self can follow.

The incidents backups actually save you from

The realistic disasters are mundane: an app bulk edit gone wrong, a well meaning staffer deleting a collection, a theme update overwriting customizations, a discount list lost before a sale. Each is a bad afternoon with backups and a bad month without them. Account level incidents are rarer but total, which is why the copies live outside the account they protect.

Write the restore steps on one page while you are calm: where the files live, in what order to restore theme, products, and settings, and who holds account access. Incident day is a poor classroom. A store that can rebuild itself in a day owns a quiet competitive advantage: it can take risks, test boldly, and let staff learn, because the cost of a mistake is capped.

Frequently asked questions

Does Shopify keep a backup I can restore from?

The platform maintains its own system backups for its infrastructure, but merchants cannot generally roll their store back to yesterday's state from those. Some individual items may be recoverable briefly, and support can advise in specific cases, but the reliable restore point is the one you exported yourself. Plan on self sufficiency and treat any platform help as a welcome bonus.

Are backup apps worth paying for?

For stores with frequent edits, large catalogs, or several staff, usually yes: they automate versioned backups of products, themes, and more, and make restoration a few clicks. Quiet, small stores can achieve the essentials free with disciplined manual exports. The deciding factor is honesty about whether the manual routine will actually happen every month.

How long should I keep old backups?

Keep a rolling set: recent weekly copies for a month or two, then one monthly snapshot retained for a year. Theme versions deserve longer memories, since a customization from last season sometimes needs resurrecting. Storage is cheap; the expensive version is the single backup from an unknown date that turns out to be the wrong one.

What is the first backup to take before a big change?

The theme download, immediately before the change, plus a product export if the change touches catalog data. Label them with the date and the change they precede. That pairing covers the two assets big changes actually endanger, and it takes minutes. Make it a standing rule: no significant edit session starts until the pre change backup exists.