How many dedicated vCPU does a VPS for web scraping with headless Chrome need?

How many headless browsers can each plan run?

One headless Chrome browser needs between 1.5 and 2 vCPU: two published rules land in that range. Playwright Test starts, by default, half as many workers as there are logical CPU cores. BrowserStack, which runs real browsers as its business, asks self-hosted customers for 1.5 CPUs per browser on Linux for standard websites, and at least 2 for intensive sites or round-the-clock use. Applied to each plan:

Why does headless Chrome use so much CPU?

A headless browser does everything a visible one does except paint to a screen. It downloads the page, parses HTML and CSS, runs every script, lays the page out and keeps timers firing. Chromium splits that work over several processes: a browser process that manages the rest, and renderer processes for web content, with each new tab or window as a rule opening in its own. Ten tabs cost close to ten renderers' worth of CPU.

Three changes cut the bill without changing the result:

• Block what is never read. Images, fonts and media cost bandwidth and decode time; request interception in Puppeteer or routing in Playwright refuses them.
• Reuse one browser, open fresh contexts. Starting Chrome is the expensive step; a new context or page inside a running browser is far cheaper.
• Skip the browser when the data allows it. Data that sits in the HTML or in a JSON API the page calls comes back from a plain HTTP client, which runs no script at all.

Since Chrome 132, the old headless mode ships only as a separate binary, chrome-headless-shell; --headless on regular Chrome runs the new mode.

Do dedicated vCPU matter for scraping workers?

A starved browser fails instead of slowing down. Navigation and selector timeouts are set in seconds. When a neighbour takes CPU time, pages finish rendering late, waits expire, and a job that would have succeeded is retried, which costs more CPU. Browserless, which sells hosted Chrome, states it in its documentation: lower concurrency gives each browser more CPU and memory, reduces timeouts and improves stability. Lost CPU time shows up as steal, explained in what CPU steal time is and how to check it on a VPS.

At Cobaltfell the CPU side of that trade is fixed. A vCPU is one hardware thread of the host processor. Yours are pinned one to one to your VPS and never lent to another customer, and the two threads of a physical core stay together, so every 2 vCPU make one whole core that no neighbour shares. Full load is allowed for as long as your work needs it: no CPU credits, no burst window and no throttling after some minutes at 100%.

Concurrency is found the same way on any host: start at one browser per two vCPU, raise it while the error rate holds steady, and stop at the first rise in timeouts.

Hosts that sell dedicated vCPU, ranked on the same written criteria, are in which is the best dedicated CPU VPS provider in 2026.

How do I run Chrome workers safely on a VPS?

Keep the Chrome sandbox on, run as a normal user and give the container an init process. Scraped pages are untrusted code by definition, and the official guides agree on each point:

• Sandbox. Puppeteer's troubleshooting guide calls running without a sandbox strongly discouraged. Playwright's Docker guide notes that running as root disables the Chromium sandbox, and recommends a separate user plus its seccomp profile for scraping and crawling.
• Init process. Both guides recommend Docker's --init flag, so finished Chrome child processes are reaped instead of piling up as zombies.
• Shared memory. Playwright recommends --ipc=host for Chromium, because without it Chromium can run out of memory and crash.

Two numbers tell how a pool is doing: the memory held by all Chrome processes, and the steal column of mpstat.

# total resident memory of chrome / chromium / headless shell processes, in MB
ps -eo rss=,comm= | awk '/chrom/ {s+=$1} END {printf "%.0f MB\n", s/1024}'

# how many renderer processes are alive right now
pgrep -fc -- '--type=renderer'

# per-vCPU load and %steal while the pool works (package sysstat)
mpstat -P ALL 5 3

What about the websites' rules, and proxies?

Scraping stays within each site's terms and the law that applies to the operator and to the site. This page sizes the machine, not the legality of a project. Attacks on systems that are not yours, including brute-forcing and denial of service, are banned under what Cobaltfell's acceptable use policy allows, so request rates stay polite.

Proxies and IP rotation are a separate subject, and Cobaltfell sells neither. Each VPS gets one IPv4 address and an IPv6 /64 on a 1 Gbit/s port. The monthly traffic of your plan counts outgoing data only, and going past it never adds a charge by itself. Plan prices are listed under how much a dedicated-core VPS costs.