Browser-like captures for previews, QA, and monitoring
Website Screenshot
Capture any public URL as PNG, JPEG, WebP, or PDF through BrowserSolver headless stack. Emulate devices, scroll lazy content, wait for selectors, and strip cookie banners, no local Chrome fleet.
- Output formats: PNG, JPEG, WebP, or PDF: full viewport, full page, or CSS selector
- Device profiles (iPhone, Pixel, Galaxy, iPad) plus custom viewport and scale factor
- Same headless stack and API key as Website Rendering
PNG
JPEG · WebP · PDF
Full page
or selector
Devices
emulated
Visual capture without headless ops
QA teams, monitoring jobs, and compliance archives need pixels, not DOM strings. BrowserSolver runs the browser session, scroll logic, and egress so you GET a URL and receive an image or PDF.
- Same realistic sessions as Website Rendering, tuned for raster output
- Block images, scripts, or fonts when you need faster loads before capture
- Optional S3 upload with a signed URL in the JSON response
Controls for production screenshot pipelines
Wait for network idle or a selector, delay before shutter, remove ads and cookie banners, then export at the resolution your dashboard or diff tool expects.
- `wait_for_selector`, `wait_until`, and post-load delays for SPAs
- `full_page` with optional lazy-load scroll before the shutter
- Need markup instead of pixels? Switch to Website Rendering on the same API key
Pixels when HTML is not enough
Previews, visual regression, and archival jobs on the same browser stack as your render scrapers.
Full page
Capture beyond the viewport with lazy-load scroll.
Multi-format
PNG, JPEG, WebP, or PDF output.
Device profiles
iPhone, Pixel, Galaxy, iPad presets.
Selector capture
Screenshot one element, not the whole page.
Viewport control
Custom width, height, and scale factor.
Headless stack
Same browser engine as Website Rendering.
Frequently asked questions
Credits, scrape types, and billing before your first production job.
How is Website Screenshot different from Website Rendering?
Rendering returns HTML after JavaScript runs. Screenshot returns a PNG, JPEG, WebP, or PDF file, ideal for QA diffs, thumbnails, compliance PDFs, and monitoring dashboards. Both use the same headless stack.
Can I capture a specific element?
Yes. Pass a CSS selector to crop the capture to one node, useful for product cards, hero banners, or widget regression tests without storing full-page images.
Pick your next move
Wire up an integration, review plans, or read the API reference before your first job.
Integrations
Trigger BrowserSolver from n8n, Zapier, Make, or any stack that speaks HTTP.
Scrape your first blocked URL
Fetch, render, screenshot, or unlock from one dashboard. Proxies, browsers, and anti-bot lanes stay on our side.
- 500 signup credits
- No card to start
- All scraping modes