# Do paused sandboxes count toward the concurrency limit? (/docs/faq/paused-sandboxes-concurrency)

<!-- agent-signals: reading_time_min: 1 · est_tokens: 221 · updated: 2026-07-30 -->
Related: [How do I increase my concurrency limit?](/docs/faq/increase-concurrency.md), [Is there a limit on how many templates I can create?](/docs/faq/template-limit.md), [Can I make a template public so other projects can use it?](/docs/faq/public-templates.md), [Can I run sandboxes in the EU?](/docs/faq/eu-region.md), [Why does iptables fail with 'xt_owner module missing' in a sandbox?](/docs/faq/iptables-xt-owner.md), [Why does pip install fail when building a template?](/docs/faq/pip-install-error.md)

No. Only running sandboxes count toward your concurrency limit. Paused sandboxes are excluded, so you can keep many paused sandboxes around without affecting how many sandboxes you can run at the same time.

Paused sandboxes are also not billed. You are only charged for sandboxes while they are running, so keeping a sandbox paused has no impact on your bill.

There is also no time limit on how long a sandbox can remain paused. Paused sandboxes are kept indefinitely, with no automatic deletion or time-to-live, and you can [resume](/docs/sandbox/persistence#resuming-sandbox) them at any time.

E2B never kills paused sandboxes on its own. A paused sandbox is only removed when you explicitly call `kill` on it (either via `sandbox.kill()` or `Sandbox.kill(sandboxId)`).

For more details on pausing and resuming, see the [Sandbox persistence](/docs/sandbox/persistence) page.