PNG, WebP, and PDF captures from the same headless stack as Rendering
Website Screenshot
Capture any public URL as PNG, JPEG, WebP, or PDF through BrowserSolver. Emulate devices, scroll lazy content, wait for selectors, strip cookie banners, and keep visual QA in sync with your HTML scrapes.
- Full page, viewport, or CSS selector crops
- Device profiles for iPhone, Pixel, Galaxy, and iPad
- Lazy-load scroll before the shutter fires
- Same Chromium stack and API key as Website Rendering
PNG
JPEG · WebP · PDF
Full
page capture
Crop
CSS selector
Device
emulation
Visual proof beside your scrape job
- Step 1
Render or navigate
Reach the DOM state your QA or archive needs.
- Step 2
Capture
Export PNG, WebP, or PDF with device and viewport controls.
- Step 3
Store
Keep bytes in your bucket or attach them to tickets and diffs.
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
- Same API key and credit balance across BrowserSolver scrape modes
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
- Same API key and credit balance across BrowserSolver scrape modes
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.
Formats
PNG, JPEG, WebP, and PDF outputs
Devices
Mobile and desktop profiles built in
In sync
Same sessions as Rendering scrapes
QA-ready
Element crops for visual regression
Frequently asked questions
Credits, scrape types, and billing before your first production job.
How is Screenshot different from Rendering?
Rendering returns HTML after JavaScript. Screenshot returns an image or PDF, ideal for diffs, thumbnails, compliance packs, and monitoring dashboards.
Can I capture a specific element?
Yes. Pass a CSS selector to crop the capture to one node such as a product card or price widget.
Does PDF use a separate product?
Yes. PDF uses the same print pipeline as Screenshot. Choose PDF Generation when you need a document archive, or Screenshot when you need an image.
Can I remove cookie banners first?
Yes. Banner and ad cleanup options are documented on the Screenshot endpoint so captures stay usable for QA.
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