# Limits for Render Sandboxes


> *Render Sandboxes is in public beta.*
>
> APIs, defaults, and limits might change during the beta period.

The following limits apply to [Render Sandboxes](sandboxes). All limits are subject to change during the beta period.

## Compute plans

Each sandbox uses one of the following compute plans, which you specify when you [create a sandbox](sandboxes-creating#compute-plan):

| Plan | Specs |
| --- | --- |
| `1c-2g` (default) | 1 CPU 2 GB RAM |
| `2c-4g` | 2 CPU 4 GB RAM |
| `4c-8g` | 4 CPU 8 GB RAM |
| `8c-16g` | 8 CPU 16 GB RAM |

## General limits

------

##### Writable filesystem storage per sandbox

40 GB

##### Maximum continuous runtime

- 30 days with a *Pro* workspace or higher
- 24 hours with a *Hobby* workspace

If a sandbox is [suspended](sandboxes-creating#suspension-on-idle) and later resumed, this limit resets.

##### Maximum idle timeout

24 hours (you can also [disable idle timeout entirely](sandboxes-creating#suspension-on-idle))

##### Suspended sandbox resumability period

30 days

##### Sandbox groups per workspace

10

##### Concurrent sandboxes per sandbox group

1,000

[See details below.](#concurrency-per-group)

##### Environment variables per sandbox

100 variables, with a combined size of 256 KB across names and values

##### Supported regions

1 (Oregon)

------

> *Need to increase these sandbox limits?*
>
> Reach out with details about your use case:

### Concurrency per group

- Each sandbox group can have up to 1,000 concurrent sandboxes.
    - [Suspended](sandboxes-creating#suspension-on-idle) sandboxes do not count toward this limit.
    - You can [reduce the concurrency limit](sandboxes-creating#setting-group-concurrency) for an individual group.
- To resume a suspended sandbox, its group must have available capacity.
- While a group is at its concurrency limit, requests to create or resume a sandbox fail with HTTP code `429`.
    - To reclaim capacity, [terminate](sandboxes-creating#terminating-a-sandbox) sandboxes you no longer need.

## API rate limits

Sandbox API operations have separate default rate limits. These limits apply per user, shared across that user's API keys. Requests that exceed a rate limit fail with HTTP code `429`.

| Operation | Requests per minute |
| --- | --- |
| *[Create a sandbox](sandboxes-creating)* | 100 |
| *[Terminate a sandbox](sandboxes-creating#terminating-a-sandbox)* | 1,000 |
| *Execute a [command](sandboxes-executing)* | 1,000 |
| *[Upload or download](sandboxes-files) a file or directory* | 1,000 |
| *Read sandbox and sandbox group resources* | 400 |
| *Write sandbox group resources* | 100 |
| *Capture a [snapshot](sandboxes-snapshots)* | 10 |


---

##### Appendix: Glossary definitions

###### compute plan

Specifies the CPU and RAM available to your service's *instances*.

Common compute plans for a new web service include:

- *`free`*: 0.1 CPU / 512 MB RAM
- *`0.5c-512mb`*: 0.5 CPU / 512 MB RAM
- *`1c-2g`*: 1 CPU / 2 GB RAM

Compute plans were previously known as *instance types*.

Related article: https://render.com/docs/compute-plans.md

###### region

Each Render service runs in one of the following regions: *Oregon*, *Ohio*, *Virginia*, *Frankfurt*, or *Singapore*.

Services in the same region can communicate over their *private network*.

Related article: https://render.com/docs/regions.md