---
site: steel.dev
collection: docs
canonical_url: https://steel.dev/docs/self-hosting/steel-browser
markdown_url: https://steel.dev/docs/self-hosting/steel-browser.md
content_signal: ai-input=yes, ai-train=yes, search=yes
title: Steel Browser
description: Steel Browser is the open-source browser API that you can run yourself. See how it differs from Steel Cloud and when to choose it.
summary: Steel Browser is the open-source browser API that you can run yourself.
type: concept
reviewed: 2026-11-12
prerequisites: []
related:
  - https://steel.dev/docs/self-hosting/docker.md
  - https://steel.dev/docs/self-hosting/configuration.md
agent_setup: https://setup.steel.dev/install.md
docs_index: https://steel.dev/docs/sitemap.md
---

# Steel Browser

Steel Browser is Steel's open-source browser API. It runs one Chrome browser behind a REST API, on a machine that you control. The code is on [GitHub](https://github.com/steel-dev/steel-browser) under the Apache 2.0 license.

Steel Cloud is the service at `api.steel.dev`. Steel runs its browsers for you, adds features that Steel Browser does not have, and bills you for usage. With Steel Browser, you run the browser yourself, and you take care of its capacity, updates and security.

## What you get

Steel Browser is a Node.js server that starts Chrome and controls it with Puppeteer over CDP (Chrome DevTools Protocol). It serves its API on port `3000`. The Docker image includes Chromium, so you do not need a browser on the host.

For the features that both have, Steel Browser uses the same API paths as Steel Cloud:

- Sessions, with `POST /v1/sessions` and options such as `proxyUrl`, `blockAds`, `dimensions` and `userAgent`. You can list, read and release sessions.
- Quick actions, `POST /v1/scrape`, `/v1/screenshot` and `/v1/pdf`, which work on a page in one request.
- Commands, at `POST /v1/sessions/{sessionId}/commands`, which drive the session. They are Experimental and off by default. See [Configuration](https://steel.dev/docs/self-hosting/configuration#enable-the-commands-api).
- Session files, under `/v1/sessions/{sessionId}/files`, which move files in and out of the browser.

Playwright and Puppeteer connect to a session's `websocketUrl`, as they do with Steel Cloud. The TypeScript and Python Steel SDKs work with Steel Browser for sessions, scrapes and session files when you change their base URL. See [Create a session](https://steel.dev/docs/self-hosting/docker#create-a-session).

Screenshots and PDFs work differently. Steel Browser's `/v1/screenshot` and `/v1/pdf` return the image or the PDF file itself, while Steel Cloud returns JSON with the file's `url`. The SDK's `screenshot` and `pdf` methods expect that JSON, so call these two endpoints with an HTTP client and save the response body. A scrape with `screenshot` or `pdf` set returns each file as a base64 string, not as an object with a `url`.

Steel Browser also has a UI to watch the browser, at `/ui` in the single Docker image. Its OpenAPI documentation, at `/documentation`, describes the API of the version that you run.

Steel Browser runs one browser, so it has one session at a time. Creating a session ends the session that is running. Steel Browser does not check an API key, so anyone who can reach its ports can control the browser.

## How Steel Browser differs from Steel Cloud

Steel Browser and Steel Cloud are separate code bases, and they change separately. For the API of the version that you run, see `/documentation` on your instance.

| Feature | Steel Cloud | Steel Browser |
| - | - | - |
| Sessions at the same time | Depends on the plan. See [Limits](https://steel.dev/docs/platform/limits). | One |
| Authentication | An API key on every request | None |
| Screenshot and PDF responses | JSON with the file's `url` | The file itself |
| Proxies | [Steel proxies](https://steel.dev/docs/stealth/proxies) and your own proxy | Your own proxy, with `proxyUrl` |
| [Dedicated IPs](https://steel.dev/docs/stealth/dedicated-ips) | Yes | No. The browser uses the host's network. |
| [CAPTCHA solving](https://steel.dev/docs/stealth/captcha-solving) | Yes | No |
| Bot detection | Steel's [fingerprints](https://steel.dev/docs/stealth/fingerprints) and stealth features | Basic: stealth plugins and fingerprint injection |
| [Commands](https://steel.dev/docs/control/commands) | Yes | Off by default. Turn it on with `ENABLE_COMMANDS_API=true`. |
| [Extensions](https://steel.dev/docs/sessions/extensions) | Upload them with the Extensions API | Put them in the `api/extensions` folder, build the image, and name them in the `extensions` option of the session |
| [Profiles](https://steel.dev/docs/logins/profiles) | Profiles API | No Profiles API. `persist: true` keeps one browser data folder. |
| [Credentials](https://steel.dev/docs/logins/credentials) | Yes | No |
| [Files](https://steel.dev/docs/sessions/files) | The Files API and session files | Session files only |
| [Live view](https://steel.dev/docs/observability/live-view) | Yes | A UI at `/ui` |
| [Agent traces](https://steel.dev/docs/observability/agent-traces), [signals](https://steel.dev/docs/observability/signals), [session cost](https://steel.dev/docs/production/session-cost) | Yes | No |
| [MCP server](https://steel.dev/docs/control/mcp-server) | Hosted at `https://mcp.steel.dev/mcp` | No |
| Updates and capacity | Steel handles them | You handle them |

## When to self-host

Self-host when the browser must run on your own network, for example to reach an application that is not on the internet. The browser then uses your network's DNS, routes and IP address.

Self-host to develop and test against a browser on your own machine, or when you want to change the server itself. Steel Browser is open source, so you can read and change every part of it.

Choose Steel Cloud when you need many sessions at the same time, Steel proxies, CAPTCHA solving, profiles or credentials, or when you do not want to run and secure the servers. Your code changes little between the two, because the Steel SDK takes a base URL and the shared parts have the same paths.

To start, [run Steel Browser with Docker](https://steel.dev/docs/self-hosting/docker) on your machine or on a server that you manage.
