Developer Sandbox
A Developer Sandbox is a sandbox environment that copies only the metadata (configuration) from production with no production data, providing a clean slate for development and testing.
Definition
A Developer Sandbox is a sandbox environment that copies only the metadata (configuration) from production with no production data, providing a clean slate for development and testing. It is the smallest and fastest-to-refresh sandbox type, ideal for isolated feature development.
In plain English
“A Developer Sandbox is the smallest sandbox type. It copies your org's metadata (settings, code, layouts) but no production data. It refreshes quickly and is perfect for individual feature development and isolated testing.”
Worked example
Three developers on Tarryton Capital's Salesforce team each work in their own Developer Sandbox - small, metadata-only sandboxes that copy production's configuration without any production data. Each developer builds and tests features in isolation; merging their work into a shared Integration sandbox happens after individual testing passes. Developer Sandboxes refresh quickly (under an hour for most metadata) and have minimal storage (200 MB), making them perfect for parallel feature development. The cost is low; each Salesforce edition includes multiple Developer Sandboxes.
Why Developer Sandbox matters
A Developer Sandbox is a sandbox type that copies only an org's metadata (configuration, Apex code, layouts, custom objects, and other Setup-defined components) with no production data. It provides 200 MB of test data storage and 200 MB of file storage. It's the smallest sandbox type and the fastest to refresh, making it ideal for isolated feature development and unit testing where production data isn't needed.
Developer Sandboxes are typically the workhorse for individual developer environments. Each developer might have their own Developer Sandbox for feature work, allowing them to make changes without stepping on each other. They can be refreshed once per day, so a developer can quickly reset to a clean state when they need to start over. For larger test data needs, Developer Pro Sandboxes offer 1 GB of storage; for actual production data, Partial Copy or Full sandboxes are required. Developer Sandboxes are included in most paid Salesforce editions.
How organizations use Developer Sandbox
Maintains one Developer Sandbox per developer so each engineer has their own isolated environment for feature work. Developers refresh whenever they need a clean starting point.
Uses Developer Sandboxes for isolated unit testing of new Apex code. The fast refresh cycle lets them reset to a known state between test runs.
Treats Developer Sandboxes as personal workspaces and uses Partial Copy or Full sandboxes for integration testing with realistic data.
Trust & references
Straight from the source - Salesforce's reference material on Developer Sandbox.
- Sandbox Licenses and Storage Limits by TypeSalesforce Help
- Create a SandboxSalesforce Help
Test your knowledge
Q1. What does a Developer Sandbox copy from production?
Q2. How often can you refresh a Developer Sandbox?
Q3. What's the typical use case for Developer Sandboxes?
Discussion
Loading discussion…