Skip to content

Limits

Set up your agent

Give your coding agent a Steel browser and the Steel skills, so that it browses and writes Steel code the right way. Learn more

Install the Steel CLI. It signs you in and installs the skills for your coding agents.

curl -fsS https://setup.steel.dev | sh

Or send this prompt to your coding agent, and it does the same:

Read https://setup.steel.dev/install.md and follow it to set up Steel for this coding client.
Then continue my requested task using the installed Steel skill.

Set up your agent →

Each plan limits concurrent sessions, session length, session creates per minute and data retention. A request that goes past one of these limits gets an error that names the limit. The prices are on Pricing, and every error code is on Errors.

Limits by plan

LimitLaunchScaleEnterprise
Concurrent sessions101001,000+
Session length15 minutes1 hourUp to 24 hours
Session creates per minute60600No limit
Data retention7 days14 daysCustom

The limits apply to the whole organization, across all its projects. On Enterprise, your contract sets the concurrent sessions, session length and data retention.

If your organization is on a legacy plan, its limits differ from this table.

Concurrent sessions

A session counts toward the limit from the moment it is created until it is released or it times out. A client that disconnects does not release the session, so release each session when its work ends.

When your organization reaches the limit, a request to create a session gets a 429 response with the code concurrency_limit_reached. Know your limits shows how to check how many sessions are live and what to do at the limit.

Session length

A session's timeout option sets how long it can run. The timeout cannot be longer than your plan's session length. A request with a longer timeout gets a 400 response with the code session_timeout_exceeded, and no session is created. See Set timeouts.

Rate limits

RequestsLimitCounted for
Create a session (POST /v1/sessions)Your plan's session creates per minuteEach organization
Scrape (POST /v1/scrape)20 a minuteEach client IP address
Screenshot (POST /v1/screenshot)20 a minuteEach client IP address
PDF (POST /v1/pdf)20 a minuteEach client IP address
The MCP server's scrape tool20 a minuteEach organization
The MCP server's session_create toolYour plan's session creates per minuteEach organization

Your plan's per-minute limit counts only the requests that create a session: POST /v1/sessions and the MCP server's session_create tool. Other API requests do not count toward it. Scrape, Screenshot and PDF each have their own limit of 20 requests a minute. Steel enforces the plan's limit only on Launch and Scale. Enterprise has no limit on session creates.

A request over a rate limit gets a 429 response with the code rate_limited. This is the response to a session create over the Launch limit:

{
  "error": "Too Many Requests",
  "code": "rate_limited",
  "message": "Session create rate limit reached: your plan allows 60 session creates per minute. Retry in 12 seconds.",
  "retryable": true,
  "retryAfterSeconds": 12,
  "linkToDocs": "https://docs.steel.dev/overview/pricinglimits"
}

Scrape, Screenshot and PDF return the same fields with another message. rate_limited has both messages.

Wait for the number of seconds in retryAfterSeconds, or in the retry-after header, before you try again. Each response from a limited endpoint also has the headers x-ratelimit-limit, x-ratelimit-remaining and x-ratelimit-reset.

The MCP server's tools do not return 429. A tool over its limit returns an error that says how many seconds to wait. See MCP server troubleshooting.

If many workers retry at the same moment, they reach the limit again. Queue the work, and retry with a backoff. See Run sessions at scale.

Data retention

Each plan has a data retention period: 7 days on Launch, 14 days on Scale, and a custom period on Enterprise. Download the recordings, logs and files that you need before the period ends.

Some data has its own lifetime:

DataHow long Steel keeps it
A profileUntil it goes 30 days without use. Then Steel deletes it.
A credentialUntil you delete it

Security and compliance explains how Steel handles this data.

Size limits

UploadLargest size
A file, to a session or to global files500 MB
A profile300 MB
An extension file500 MB
The value of a credential64 KB

You can lease at most 25 dedicated IPs in one checkout on the dashboard's Dedicated IPs page.

Raise a limit

To getDo this
Scale's limitsChange your plan to Scale. See Billing and usage.
More than Scale's limitsContact sales about Enterprise. Enterprise has custom limits, and Steel can reserve browser pools for your workload.
A limit that does not match your planContact Support with your organization, the error and the session ID.