---
url: 'https://dxpr.com/hc/documentation/learn-dxpr-builder/advanced/backup-restore'
title: 'Back up and restore your builder pages | DXPR'
author:
  name: docs-sync
  url: 'https://dxpr.com/users/docs-sync'
date: '2026-10-23T14:31:17+00:00'
copyright: 'Copyright DXPR. All rights reserved.'
type: article
summary: 'What to back up and how to restore builder content'
tags:
  - 'Meet compliance requirements'
image: 'https://dxpr.com/themes/custom/dxpr_com/images/dxpr-share-card.jpg'
published: true
og:
  site_name: DXPR
  updated_time: '2026-10-23T14:31:17+0000'
  'image:alt': 'DXPR, powered by Drupal: AI-powered Drupal for marketers.'
schema:
  '@context': 'https://schema.org'
  '@graph':
    -
      mainEntity: {  }
    -
      '@type': TechArticle
      headline: 'Back up and restore your builder pages'
      description: 'What to back up and how to restore builder content'
      image:
        '@type': ImageObject
        url: 'https://dxpr.com/themes/custom/dxpr_com/images/dxpr-share-card.jpg'
        width: '1200'
        height: '630'
      datePublished: '2026-10-23T14:31:17+0000'
      dateModified: '2026-10-23T14:31:17+0000'
      author:
        '@type': Organization
        '@id': 'https://dxpr.com/#organization'
        name: DXPR
        url: 'https://dxpr.com/'
        logo:
          '@type': ImageObject
          url: 'https://dxpr.com/themes/custom/dxpr_com/dxpr-logo-dark.svg'
          width: '1348'
          height: '501'
      publisher:
        '@type': Organization
        '@id': 'https://dxpr.com/#organization'
        name: DXPR
        url: 'https://dxpr.com/'
        logo:
          '@type': ImageObject
          url: 'https://dxpr.com/themes/custom/dxpr_com/dxpr-logo-dark.svg'
          width: '1348'
          height: '501'
      mainEntityOfPage: 'https://dxpr.com/hc/documentation/learn-dxpr-builder/advanced/backup-restore'
      articleSection: 'Meet compliance requirements'
    -
      '@type': WebPage
      '@id': 'https://dxpr.com/hc/documentation/learn-dxpr-builder/advanced/backup-restore'
      description: 'What to back up and how to restore builder content'
      breadcrumb:
        '@type': BreadcrumbList
        itemListElement:
          -
            '@type': ListItem
            position: 1
            name: Home
            item: 'https://dxpr.com/'
      publisher:
        '@type': Organization
        '@id': 'https://dxpr.com/#organization'
        name: DXPR
      inLanguage: en
---
[Help Center](/hc)/[Documentation](/hc/documentation) /[Learn DXPR Builder](/hc/documentation/learn-dxpr-builder) /[Manage the site](/hc/documentation/learn-dxpr-builder/manage) /[Meet compliance requirements](/hc/documentation/learn-dxpr-builder/manage/compliance) # Back up and restore your builder pages.

What to back up and how to restore builder content

 Learn DXPR BuilderManage the siteMeet compliance requirements

   ## In this guide

 Related guides

- [Version control](/hc/documentation/learn-dxpr-builder/advanced/version-control)

You keep a copy of every builder page, image and setting, and you can bring back a whole site or a single page. DXPR Builder keeps pages in Drupal's database and uploads in the files directory, so a normal Drupal backup covers it. This page lists what to include and how to restore it.

## What to back up

| Component | Location | Contains |
|---|---|---|
| Database | MySQL, MariaDB or PostgreSQL | Page content and every revision, plus the active configuration |
| Files directory | `sites/default/files/` | Uploads in `dxpr_builder_images`, `dxpr_builder_videos` and `dxpr_builder_files` |
| Configuration export | Your sync directory, often `config/sync/` | Settings, page templates, user templates, user profiles and the product key's Key entity |

The editor's undo history lives in each editor's browser and is not part of any backup.

## Back up a site

1. Dump the database:

    ```bash
    drush sql:dump --result-file=backup.sql

    ```
2. Copy the files directory:

    ```bash
    cp -r sites/default/files/ /backup/files/

    ```
3. If you keep configuration in code, export it as well:

    ```bash
    drush config:export

    ```

## Restore a site

1. Import the database:

    ```bash
    drush sql:cli < backup.sql

    ```
2. Copy the files directory back to `sites/default/files/`.
3. If your configuration lives in code, import it:

    ```bash
    drush config:import

    ```
4. Rebuild caches:

    ```bash
    drush cache:rebuild

    ```

## Roll back one page

Every builder save creates a revision, so one page comes back without a full restore.

1. Open the page's **Revisions** tab.
2. Find the revision before the unwanted change. Builder saves show the log message `Saved with DXPR builder`.
3. Click **Revert**.

## What you see

The restored pages open in the editor with their layouts, images show for visitors, and the **License** section under **General Settings** still holds your product key.

## If you don't see your content

- **Pages are back but images are broken.** The files directory was not restored. Copy the `dxpr_builder_images`, `dxpr_builder_videos` and `dxpr_builder_files` folders back.
- **The editor asks for a product key.** The Key entity that holds the key was not restored, or its environment variable is missing on this server. Check the **License** section at **DXPR Studio**

    > **DXPR Builder** &gt; **General Settings**.
- **Visitors still see the pages from before the restore.** A cache in front of the site serves old copies. Run `drush cache:rebuild`and purge Varnish or your CDN.

## What's next?

[Version control for tracking changes](/hc/documentation/learn-dxpr-builder/advanced/version-control) to continue exploring DXPR Builder.