In memory. In cold starts. In tokens. In infrastructure you didn't need. Here's the math — and the middle ground between curl and Chrome.
Adjust the sliders to match your workload. Everything updates in real time. Pick a preset to start from a realistic scenario.
The tax compounds. Every task pays it — in cloud compute and in LLM tokens. Here's what your current setup costs, and what you'd save with a lighter tool.
A cheaper tool that can't do your task isn't a savings. Here's what each browser tool actually supports. Click a column to highlight.
| Capability | curl | WebFetch | unbrowser | Playwright | Browserbase |
|---|
The pain grows linearly — but the gap between Chrome and lighter tools grows with it. Drag to see how your costs change from 1 to 500 concurrent sessions.
Answer honestly. We'll recommend the lightest tool that handles your workload — and tell you when you actually need Chrome.
Every metric, side by side. This is the data behind the calculator.
unbrowser is a 10MB binary that gives your agent JavaScript execution, cookies, forms, and clicks — without the 280MB per-session tax.
Try unbrowser