---
site: steel.dev
collection: docs
canonical_url: https://steel.dev/docs/production/make-sessions-faster-and-cheaper
markdown_url: https://steel.dev/docs/production/make-sessions-faster-and-cheaper.md
content_signal: ai-input=yes, ai-train=yes, search=yes
title: Make sessions faster and cheaper
description: Cut what a session costs and how long it takes. Release it early, load less, skip the sign-in, and turn on proxies and CAPTCHA solving only where they help.
summary: Cut what a session costs and how long it takes.
type: how-to
reviewed: 2026-11-16
prerequisites:
  - https://steel.dev/docs/production/projects-and-namespaces.md
related:
  - https://steel.dev/docs/production/checklist.md
  - https://steel.dev/docs/production/run-sessions-at-scale.md
  - https://steel.dev/docs/production/session-cost.md
  - https://steel.dev/docs/production/track-cost-per-customer.md
  - https://steel.dev/docs/production/projects-and-namespaces.md
agent_setup: https://setup.steel.dev/install.md
docs_index: https://steel.dev/docs/sitemap.md
---

# Make sessions faster and cheaper

A session costs browser time for as long as it is open, and proxy bandwidth and CAPTCHA solves when it uses them. [Pricing](https://steel.dev/docs/platform/pricing#usage-rates) has the rates. Most of a run's cost and time comes from a few habits: a session that stays open after its work ends, pages that load more than the task needs, and steps that every run repeats. Go through the items below, and compare a run's cost before and after each change.

## Release sessions on time

- **Release each session as soon as its work ends.** Steel bills a session until it is released or it times out. Release it in a `finally` block, so that an error does not leave it open. See [Always release sessions](https://steel.dev/docs/production/run-sessions-at-scale#always-release-sessions).
- **Let idle sessions end on their own.** Set `inactivityTimeout`, so that a session that your code forgets ends after a short time without activity. See [Release idle sessions](https://steel.dev/docs/sessions/timeouts#release-idle-sessions).

## Load less

- **Block what the task does not need.** Steel blocks ads by default. Set `optimizeBandwidth` to `true` to block images, media and stylesheets as well, or block the hosts that you choose. Pages load faster, and a session on a Steel proxy uses less bandwidth. Keep stylesheets for a task that needs the page to look right, such as a screenshot. See [Reduce bandwidth](https://steel.dev/docs/sessions/bandwidth).

## Skip the sign-in

- **Start each run signed in.** Sign in once, save the browser as a [profile](https://steel.dev/docs/logins/profiles), and start the next sessions from it with `profileId`. Each run then skips the sign-in steps, and the site sees a browser that it knows instead of a new login. See [Stay signed in across sessions](https://steel.dev/docs/logins/stay-signed-in).

## Turn on paid features only where they help

- **Add a proxy only for the sites that need one.** A session without a proxy uses no proxy bandwidth. When a site needs a proxy and you have one, bringing your own adds no proxy bandwidth charge. See [Bring your own proxy](https://steel.dev/docs/stealth/proxies#bring-your-own-proxy).
- **Keep one address for a site that checks it.** A site that sees a sign-in from a new address can ask for another check, which costs time and can cost a CAPTCHA solve. A [dedicated IP](https://steel.dev/docs/stealth/dedicated-ips) keeps one address from one session to the next, for a monthly price for each IP. See [Plans and pricing](https://steel.dev/docs/stealth/dedicated-ips#plans-and-pricing).
- **Solve only the CAPTCHAs that block the task.** With `solveCaptcha` on, Steel solves each CAPTCHA that it detects, and each solve is billed. To choose which ones to solve, set `stealthConfig.autoCaptchaSolving` to `false` and ask for each solve yourself. See [Solve on request](https://steel.dev/docs/stealth/captcha-solving#solve-on-request).

## Measure the result

- **Read what a session cost.** The API returns each session's cost and the usage behind it, so you can compare runs before and after a change. See [Session cost](https://steel.dev/docs/production/session-cost).
- **Add up the cost by customer or by job.** Tag sessions with metadata, and add up their costs. See [Track cost per customer](https://steel.dev/docs/production/track-cost-per-customer).

## Next steps

- [Prepare for production](https://steel.dev/docs/production/checklist): Check your keys, timeouts, retries, limits, cost, security and monitoring before you go live.
- [Run sessions at scale](https://steel.dev/docs/production/run-sessions-at-scale): Queue work behind your concurrency limit, and retry and release sessions safely.
- [Pricing](https://steel.dev/docs/platform/pricing): See each plan's price and its rates for browser hours, proxy bandwidth and CAPTCHA solves.
