ANEARST · 2026-09-22 · 5 min
How website screenshots actually render
What happens between paste and PNG: navigation, wait strategy, cleanup, and the render report.
A screenshot is not a GET of HTML. A browser has to parse, run script, fetch fonts, and paint. ANEARST opens an isolated browser context and navigates with a hard timeout.
After DOM content loads, the wait strategy decides when the still is fair. Network idle is the default. A CSS selector is more precise when a hero is late. A delay is a last resort and is capped.
Cleanup is CSS, not a second pass through a third-party proxy. Cookie SDKs, chat iframes, and common ad frames are hidden when you ask. If a banner uses an unknown class, the report says none matched.
The render report is the part most APIs skip. HTTP status, duration, final dimensions, ads blocked, console errors, and wait strategy travel with the file so a failed paint is diagnosable.
