---
schema_version: "1"
id: 58759a5201d13a65f57dd1e2722399a875bd75cb416dfcabbe880cd52666764e
title: Create, Clone, or Refresh a Sandbox
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/data_sandbox_create_parent.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.data_sandbox_create_parent.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 6491958a94f5d25c936713a22cadd1628e114bae9185d97337243721e3154711
description: Create a sandbox to use for development, testing, and training. Clone a sandbox to copy its data and metadata into another sandbox. Refresh an existing sandbox to update its contents.
products:
  - Salesforce Platform
release: "264"
---
# Create, Clone, or Refresh a Sandbox

Create a sandbox to use for development, testing, and training. Clone a sandbox to copy its data and metadata into another sandbox. Refresh an existing sandbox to update its contents.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: both Salesforce Classic and Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Professional</strong>, <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Database.com</strong> Editions</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
      <colgroup>
        <col style="width:50%">
        <col style="width:50%">
      </colgroup>
      <thead class="slds-text-title_caps ">
        <tr class="">
          <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d17269e73">User Permissions
            Needed</th>
        </tr>
      </thead>
      <tbody>
        <tr class="">
          <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d17269e73 ">To view a sandbox:</td>

          <td class="slds-cell-wrap" style="vertical-align:top;" headers="d17269e73 ">View Setup and Configuration</td>

        </tr>
        <tr class="">
          <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d17269e73 ">To create, refresh, activate, and delete a sandbox:</td>

          <td class="slds-cell-wrap" style="vertical-align:top;" headers="d17269e73 ">Manage Dev Sandboxes (Developer or Developer Pro only) or Manage Sandboxes (all
            sandbox types)</td>

        </tr>
      </tbody>
    </table>

You have a few ways to copy metadata and data to a sandbox. What data gets copied during creation and cloning depends on sandbox type.

## Where Are Sandboxes Created?

Sandboxes are created on sandbox instances. The location of the sandbox instance depends on where it’s corresponding production org is located.

- Sandboxes created from a production org in Salesforce First-Party are created on a Salesforce First-Party instance in the same region.
- Sandboxes created from a production org in Hyperforce are created on a Hyperforce instance in the same country.
- Sandboxes created from a production org in Government Cloud or Government Cloud Plus are created on a Government Cloud instance.

If a production org is migrated to a different infrastructure type (example: Salesforce First-Party to Hyperforce), new sandboxes created post-migration are also created on the new infrastructure type. Existing sandboxes remain on their current instance until they are refreshed or deleted by an admin, or migrated by Salesforce.

- **[Salesforce AI Skills for Sandboxes](https://help.salesforce.com/s/articleView?id=platform.data_sandbox_ai_skills.htm&release=264.0.0&type=5)**  
    Use AI Skills to manage the full lifecycle of your sandboxes from your AI coding client.
- **[Enable Source Tracking in Sandboxes](https://help.salesforce.com/s/articleView?id=platform.data_sandbox_enable_source_tracking.htm&release=264.0.0&type=5)**  
    By enabling source tracking in Developer and Developer Pro sandboxes, Salesforce DX tooling can automatically track new, changed, and deleted metadata components. You can then select and determine which changes to move forward in the development cycle and release. For DX tooling that uses a Salesforce DX project or source control repository, source tracking can aid in conflict detection and resolution. And best of all, because source tracking identifies which metadata components changed, you no longer have to manually keep track of changes.
- **[Sandbox Data Storage Upgrades](https://help.salesforce.com/s/articleView?id=platform.data_sandbox_storage_upgrades.htm&release=264.0.0&type=5)**  
    Upgrade the data storage of new or existing Developer or Developer Pro sandboxes, which supports developing and testing with larger data sets.
- **[Create a Sandbox](https://help.salesforce.com/s/articleView?id=platform.data_sandbox_create.htm&release=264.0.0&type=5)**  
    When you create a sandbox, Salesforce copies the metadata from your production org to a sandbox org. What data gets copied depends on the sandbox type.
- **[Refresh Your Sandbox](https://help.salesforce.com/s/articleView?id=platform.data_sandbox_refresh.htm&release=264.0.0&type=5)**  
    Refreshing a sandbox updates its metadata from the source org. If the sandbox is a clone or if it uses a sandbox template, the refresh process updates the org’s data and its metadata. The org ID of the sandbox changes each time it’s refreshed.
- **[Activate Your Refreshed Sandbox](https://help.salesforce.com/s/articleView?id=platform.data_sandbox_refresh_activate.htm&release=264.0.0&type=5)**  
    If you didn’t select **Auto Activate** while refreshing your sandbox, you must activate your sandbox before you can use it.
- **[What are Preview and Non-Preview Sandboxes?](https://help.salesforce.com/s/articleView?id=platform.data_sandbox_preview.htm&release=264.0.0&type=5)**  
    During the Salesforce major release transitions, sandboxes get upgraded on different timelines based on their release type. The two release types for sandboxes are preview and non-preview.
- **[Best Practices for Salesforce Sandbox Creation and Refresh Times](https://help.salesforce.com/s/articleView?id=platform.data_sandbox_what_impacts_sandbox_creation_time.htm&release=264.0.0&type=5)**  
    Although Salesforce can’t speed up the process of creating or refreshing sandboxes, these strategies can help you to minimize sandbox copy times.
- **[Some Considerations](https://help.salesforce.com/s/articleView?id=platform.data_sandbox_create_refresh_delete.htm&release=264.0.0&type=5)**  
    Review these considerations when you create, refresh, or delete a sandbox.
- **[Sandbox Cloning](https://help.salesforce.com/s/articleView?id=platform.data_sandbox_cloning_overview.htm&release=264.0.0&type=5)**  
    You can create a sandbox by cloning an existing sandbox rather than using your production org as your source. Save time by customizing a sandbox with a set of data and metadata and then replicating it. Sandbox cloning simplifies having multiple concurrent streams of work in your application life cycle. You can set up a sandbox for each type of work, such as development, testing, and staging. Your colleagues can easily clone individual sandboxes instead of sharing one sandbox and avoid stepping on each other’s toes.
- **[Monitor Your Sandbox’s Progress](https://help.salesforce.com/s/articleView?id=platform.data_sandbox_monitor.htm&release=264.0.0&type=5)**  
    From Setup, enter Sandboxes in the Quick Find box, then select **Sandboxes**. The list displays all your sandboxes. Select a sandbox to view details about its copy or refresh progress.
- **[Determine Who Has Sandbox Access](https://help.salesforce.com/s/articleView?id=platform.data_sandbox_selective_access.htm&release=264.0.0&type=5)**  
    Selective Sandbox Access helps you limit access to only required users who are included in a public group. It also removes the additional step for a Salesforce admin to change user email addresses back to their original format.