Web Design

Website Backup: What to Back Up, How Often, and What Your Platform Already Keeps

Most pages about website backup are selling a backup service or describe a WordPress server. Most small business sites today run on a hosted builder, and each one keeps some things for you and quietly leaves others out. This guide sets out what a backup must cover, how often to take one, and what Webflow, Wix, Squarespace, Shopify and WordPress actually keep, from their own help pages read on 14 November 2026.

Website Backup: What to Back Up, How Often, and What Your Platform Already Keeps

Key takeaways

  • A backup is only useful if it can be restored. The WordPress handbook says to check automated backups with a manual one now and then, to make sure the process works.
  • Hosted builders keep versions, not full backups. Webflow and Wix save versions of your site as you edit; Shopify points you to CSV exports and backup apps; Squarespace exports only part of a site.
  • Restoring a version does not undo everything. Wix lists store, blog, bookings and CMS data among the things a site restore does not revert.
  • Some of your data lives outside the site. Form entries, email, analytics and payment records sit in other services and need their own copies.
  • Frequency follows how often the site changes. The WordPress handbook suggests weekly for smaller sites and daily for busy ones. A store that takes orders every day needs more than a brochure site.
  • Keep copies in more than one place. The handbook suggests three to five recent backups, kept on the host, in cloud storage and on your own computer.

The short answer

Back up three things: the site itself (pages, design, code), its content and data (posts, products, customers, orders, form entries), and the access to it (domain, hosting and account logins). How you do it depends on the platform. On WordPress or your own server, back up the database and the files together, at least weekly, and keep copies away from the server. On Webflow and Wix, the platform saves versions as you work, so your job is to export the content the version history does not cover. On Shopify, export your CSV files on a schedule or use a backup app. On Squarespace, know that a full export is not possible and keep your own copies of images and text. Then test a restore once, before you need it.

About us: Amariq builds and looks after websites on Webflow, Framer, WordPress, Shopify, Wix, Squarespace and static hosting. The platform rules below come from each maker's help pages, read on 14 November 2026.

What ranks for this search, and what is missing

We searched Google (US, English) on 14 November 2026. Google's AI summary described a backup as a copy of files and database and gave the 3-2-1 rule. The results were mostly backup products: GoDaddy's backup page and help article, HostGator's automatic backup add-on, Domains Priced Right and Dropmysite. Then came Elementor's knowledge base (1 September 2026), Wix's guide to website backup (20 July 2026), Quora and Reddit.

The Wix guide covers the types of backup and good habits, and suggests using a builder that takes care of backups for you. It does not say what Wix's own restore leaves out, which its help centre lists in detail. None of the results compares what each hosted platform keeps, or reminds you that form entries and email often live somewhere else.

What a backup has to cover

PartExamplesWhere it usually lives
Site design and codePages, templates, theme, custom codeThe platform or host
ContentPosts, CMS items, images, documentsThe platform or host
Store dataProducts, customers, orders, discount codesThe store platform
Form entries and leadsContact and quote requestsThe platform, a form tool or an email inbox
EmailYour business mailboxThe email provider, not the website
AnalyticsVisitor historyThe analytics tool
AccessDomain, DNS records, hosting and admin loginsRegistrar, host, password manager

The last row is the one people forget. A perfect copy of the site is little help if nobody can log in to the domain registrar. Keep a current list of every account, in the business's name, and a copy of your DNS records. Our guide to DNS records shows what each record does.

What each platform keeps for you

PlatformWhat it keepsWhat you should keep yourself
WebflowAutomatic backups on every 50th auto-save; paid site plans have unlimited backups you can restore at any time; images and assets are restored with a backupExports of CMS content you cannot afford to lose; a note of settings that a restore changes
WixA saved version in site history each time you editData in Wix Stores, Blog, Events, Bookings and other apps; contacts; CMS collections (Wix has separate CMS backups)
SquarespaceNo full export; an .xml export of some content for WordPressCopies of images, store and video content, custom CSS and any page type the export skips
ShopifyCSV exports you can run for products, customers, orders, gift card codes, discount codes and financial data; theme downloadRegular CSV exports or a backup app from the Shopify App Store
WordPressWhatever your host or backup plugin is set to keepThe database and the files, as one set, in more than one place

A few details from those pages matter in practice.

Webflow does not offer scheduled backups. Free Starter sites can restore only from one of the two most recent backups unless the workspace is on a paid plan. A restore can change several things: scheduled CMS items move to the publish queue, "Published on" dates update to the restore date, reCAPTCHA keys need re-adding, bot protection is turned off, and inventory levels reset unless you tick the option to include them. Read Webflow's list before you restore a live store or a site with scheduled posts.

Wix says content in its own apps does not revert when you restore a version: Stores, Blog, Events, Bookings, Video, FAQ, Restaurants and Hotels. Contacts, inbox messages and member permissions do not revert either, and nor do the content and structure of CMS collections, which have their own backup tool.

Squarespace says many features rely on its own code, so some content does not export. Its export includes layout pages, one blog with its posts, text and image blocks, and gallery pages. It leaves out other page types (including store, portfolio and index pages), more than one blog, product, video and audio blocks, drafts, style settings and custom CSS. You also cannot import the export into another Squarespace site.

Shopify lists limits on moving that data into a new store: orders cannot be imported through the admin, discount codes and issued gift cards cannot be transferred, and visitor traffic data stays behind. For a backup, that means the CSV files protect your records, but a full rebuild still takes manual work.

How often to back up

Your siteSuggested rhythmWhy
Brochure site, changed a few times a yearBefore and after each change, plus monthlyLittle changes between edits
Blog or news site, posts weeklyWeekly, as the WordPress handbook suggests for smaller sitesLose at most a week of posts
Busy site, posts or edits dailyDaily, as the handbook suggests for high-activity sitesContent changes every day
Online storeDaily exports of orders and customers, and before any app or theme changeOrders and customers change all day
Any siteAlways before an update, a redesign, a platform move or a plugin changeThe riskiest moments for a site

The handbook's own rule for the database is short: back it up regularly, and always before an upgrade. For WordPress, our step-by-step guide to backing up before a PHP update shows the exact process.

Where to keep the copies

The WordPress handbook suggests keeping at least three to five recent backups, with copies in different places: one on the hosting server, one in cloud storage and one on your own computer. A backup that sits only on the same server as the site disappears with the site if the account is closed, hacked or not paid.

Name each copy with the date and what it contains, so you can find the right one quickly. For WordPress, the handbook advises treating the database and the files as one set made at the same time, backing up the database first and restoring the files first.

Test a restore once

A backup you have never restored is a hope, not a plan. Backups are one part of our wider website security checklist. Once a year, or after changing how backups are made:

  1. Restore to a test copy, not the live site. A staging site on WordPress, a duplicate site on Webflow, or a development store on Shopify.
  2. Click through the main pages, a form, and for a store, a product and the cart.
  3. Write down how long it took and what you had to fix by hand. That is your real recovery time.

Our guide to testing on a WordPress staging site covers the WordPress side.

How our own site is backed up

amariq.com is a static site. Every change to it is a commit in a git repository, so any earlier version of any page can be brought back and compared line by line. Our forms send leads to a Google Sheet rather than storing them on the site, so the site and the leads are kept in separate places. That is the same split we suggest above: copies of the site in one place, the data it collects in another.

When something has already gone wrong

If the site has been changed by someone else, restore only after you know how they got in, or the problem comes back. Our guide to checking a hacked WordPress site covers the order of steps. If an update broke the site, restore the last version from before the update, then try the update again on a test copy. If you are unsure, stop editing so you do not overwrite the version you need.

How Amariq can help

Backups are part of how we hand over and look after a site. At launch we check what your platform keeps, set up exports for what it does not, and make sure the domain, hosting and analytics accounts are in your name. On a care plan, backups and a restore test are on the list; our guide to what a monthly maintenance plan should include shows the rest. Projects are priced from scope, never by the hour, and paid 40% at the start, 30% when the design is approved and 30% before launch. Once the final payment is made, the design, copy and code belong to you. See our WordPress development service or our Webflow maintenance service.

Frequently asked questions

Does my website builder back up my site automatically?

Partly. Webflow saves backups as you edit and Wix keeps site history, but neither restore covers everything: Wix says app content such as Stores, Blog and Bookings does not revert. Shopify relies on CSV exports and apps. Squarespace offers only a partial export.

How often should I back up my website?

The WordPress handbook suggests weekly for smaller sites and daily for busy ones. Back up before every update, redesign or platform change, and take daily copies of orders on an online store.

What should a website backup include?

The site's design and code, its content and media, any store data, and copies of data that lives elsewhere, such as form entries. For WordPress, that means the database and the files, made at the same time.

Can I download a full backup of my Squarespace site?

No. Squarespace exports an .xml file of some content, such as layout pages, one blog and text and image blocks. Store pages, product and video blocks, drafts, style settings and custom CSS do not export.

How do I back up a Shopify store?

Export CSV files for products, customers, orders, gift card codes, discount codes and financial data from the admin, and download your theme. For scheduled backups, Shopify points to apps in its App Store.

Where should I store website backups?

In more than one place. The WordPress handbook suggests one copy on the host, one in cloud storage and one on your own computer, with three to five recent backups kept.

Is a host's backup enough?

It is a good start, but the WordPress handbook notes that getting a copy back from a host's server backup can take time. Keep your own copy too, so a closed or unpaid hosting account does not take your only backup with it.

Rahat Khondokar, founder of Amariq

Rahat Khondokar

Founder & CEO, Amariq

Rahat designs and builds websites for marketing teams and ecommerce brands, and writes here about the structure, copy and conversion work behind them. More about Amariq. Find him on YouTube, Dribbble and LinkedIn.

Keep reading

Related articles.

All articles