HubSpot Developer

HubSpot sandbox vs content staging: which one you need (and when)

Quick Answer

Content staging is for website pages: it gives you a staging domain so you can review page changes before they go live. Sandboxes are broader: they let you test account-level changes and deploy supported assets after testing. If you’re redesigning a site, you want content staging. If you’re testing workflows, data changes, or integration behavior, you want a sandbox.

Who this is for

  • You’re relaunching a HubSpot website
  • You’re testing CRM or integration changes safely

Liftable Artifact: Staging vs Sandbox (Table)

Feature Content staging Sandbox
Best for website pages + relaunch account changes + safe testing
Output staging domain for review separate environment + deploy
Who needs it marketing + web teams RevOps + dev + admins
Typical use redesign, approvals integration testing, workflow tests

Content staging vendor checklist

  • Staging link updated regularly
  • Review + approval checklist
  • Launch plan

Sandbox best uses

  • Safe workflow testing
  • Integration experiments
  • Controlled deployment

Frequently Asked Questions

Yes, a sandbox subdomain.

Sometimes. Redesign in staging, test risky system changes in a sandbox.

At least one internal owner plus stakeholders.

Related links