In a sandpit, children can build, knock down and make a mess. Nothing outside gets touched. Software has sandpits too.
In a sandpit, children can dig, build castles and knock them down. Sand goes everywhere inside the pit. The lawn around it stays tidy.
A sandbox does that for software. It’s a closed-off space where something can run or be tried safely, without affecting anything outside.
Where you’ll meet them
- your phone: every app is kept in its own sandbox
- your browser: each website is boxed in, so one can't snoop on another
- test accounts: payment companies offer a sandbox where you can try payments with fake money
- security checks: suspicious files are opened in a sandbox to see what they do
Why it matters
Mistakes and nasty surprises stay inside the box. That makes it safe to experiment and harder for malware to spread.
What it isn’t
It isn’t unbreakable. Very rarely, a flaw lets something escape, which is why browsers and phones get urgent security updates.
Where the comparison breaks down
A sandpit has a visible edge. Software sandboxes are invisible. What’s allowed across the edge is set by permissions.
How the words fit together
A sandbox keeps things apart. Permissions decide what can cross over. Staging is like a sandbox for a whole website.
Your phone already keeps each app in its own sandbox, which is why one app can't simply read another app's data without your permission.

When you'll hear it
“Try it in the sandbox.” Use the safe test version, where nothing you do affects real data or money.
“Each app is sandboxed.” Apps are kept in separate boxes, so one can't meddle with another.
“It escaped the sandbox.” A security flaw let something break out of its safe box.
“Is there a safe test version where people can try this without touching real customer data?”

