/browser/ — Steel Browser Sessions
Create cloud browser sessions with custom proxies, stored browser state and configurable idle release.
Hosted browser. Official documentation · Checked · Review due .
documented capabilities
CDP / WebSocket- Default session
- The configuration guide specifies a desktop, headful session with a five-minute timeout; proxies and CAPTCHA solving are off by default.[1]
- Custom proxies
- Use useProxy.server or proxyUrl; proxyUrl takes precedence over useProxy.[1]
- Idle release
- inactivityTimeout can release a session before its total timeout; CDP commands and remote input reset the idle timer.[1]
- Stored state
- sessionContext supplies cookies/storage, while profiles preserve browser state across sessions.[1]
- Browser connection
- Attach Playwright or Puppeteer using the session ID and API key on the Steel WebSocket endpoint.[2]
Billing: Session time; exact plan rates and proxy add-on prices were not verified.
Outputs: browser-session
Documented for: Playwright, Puppeteer
getting started
documentation reviewed- Create a Steel API key and browser session.
- Select custom proxy, stored state and timeout options at creation.
- Attach a browser framework to the returned session and release it after the task.
Requirements & limitations
- The maximum permitted timeout depends on account limits.
- The current configuration guide lists us-east as the browser region; proxy geography determines the public exit location.
- Exact concurrency and billing add-ons remain unverified.
We reviewed the linked documentation. No live service connection, checkout or performance test is claimed for this listing.
primary sources
3 references- Browser session settings and proxy configurationChecked 2026-09-27
- Session lifecycle and browser attachmentChecked 2026-09-27
- Official Playwright example and time billing noteChecked 2026-09-27