What is Headless Browser?
A headless browser is a real browser engine running without a visible window. It loads pages and runs their JavaScript the way a visible browser does, rendering to an off-screen buffer and taking instructions from a script rather than a person. Puppeteer, Playwright and Selenium all drive browsers in this mode.
Chrome starts headless with the --headless=new flag, and adding --remote-debugging-port=9222 lets an external process attach; Firefox uses -headless. The controlling script speaks the Chrome DevTools Protocol or WebDriver BiDi over a WebSocket, issuing commands to navigate, click, evaluate JavaScript and capture screenshots or PDFs. Chrome's newer headless mode runs the same binary as the visible browser instead of the separate implementation that shipped for years, which erased a batch of behavioural differences that detection scripts used to test for.
What it does well is anything requiring a page to finish executing. Server-rendered HTML answers only a fraction of scraping targets now, since prices, reviews and listings often arrive from XHR calls that a plain HTTP client would have to reverse-engineer first. Headless browsers also generate PDFs and preview images, run end-to-end test suites in CI, and complete login flows. The cost is resources. Each instance holds hundreds of megabytes of memory, so achievable concurrency is far below what a request library gives you.
Detectors look for the seams. navigator.webdriver reads true when a browser runs under automation control, a GPU-less container reports SwiftShader as its WebGL renderer, and the plugin and mimeType arrays come back empty. Permission and notification states return combinations that a genuine profile does not produce. The old headless build even carried HeadlessChrome in its user agent. Beyond those flags, timing gives you away, because a script that clicks the same number of milliseconds after DOMContentLoaded on every page is not a person.
There are two directions out of the obvious tells. Run the browser headful inside a virtual display such as Xvfb, which removes the whole class of headless-specific checks at the cost of more overhead, or stay headless and apply a patching layer that repairs the known giveaways. Neither touches the network layer. The TLS fingerprint and HTTP/2 header ordering come from the browser itself, which is the argument for driving a real Chrome rather than emulating one, and the exit IP still has to stand on its own.
Where you meet it
You reach for one when requests plus an HTML parser returns an empty shell and the data only appears after JavaScript runs. The trade is throughput - a few megabytes per worker becomes a whole browser per worker, and a hundred concurrent sessions turns into a fleet question. Watch for the job that works on your laptop and fails in Docker, because a container with no GPU and no display changes the fingerprint even though the code is identical.
Common questions
How do websites detect a headless browser?
By checking values that differ under automation: navigator.webdriver, a software WebGL renderer like SwiftShader, empty plugin arrays, odd screen or window dimensions, inconsistent permission states, and artifacts of the DevTools protocol. Behaviour adds more, since fixed intervals between actions and a total absence of mouse movement cluster easily across many sessions.
Is headless mode faster than running a visible browser?
Somewhat. Skipping compositing and painting to a screen saves real work, but parsing, JavaScript execution and network waits dominate the total, so expect a modest gain rather than a transformation. The larger speed decision is whether you need a browser at all, since an HTTP client is orders of magnitude cheaper per page.
Do I need proxies with a headless browser?
If you are sending more than a handful of requests to one site, yes. Rate limits, reputation scoring and blocks are applied per IP address, and a headless browser making a thousand visits from a single datacenter address is caught by volume alone, long before any fingerprint analysis is needed.
Related terms
Real 4G/5G mobile and residential IPs
PROXIES.SX runs carrier IPs in 100+ countries with HTTP and SOCKS5 on every endpoint. $4/GB down to $2.40/GB at volume, free endpoints and rotation, and your GB never expire.