Headless Chromium for SPAs, hydrated catalogs, and dynamic scrapes
Website Rendering
Render JavaScript-heavy pages on BrowserSolver managed Chromium. Wait for selectors, block noise, export DOM HTML, then hand the same URL to Screenshot or WebUnlocker when pixels or vendor unlock are required.
- Selector waits and post-load delays for SPA scrapes
- Ad and tracker blocking for leaner HTML extracts
- Same stealth-aware browser stack as Screenshot
- Escalate to WebUnlocker on allowlisted hardened domains
2×
render lane
JS
DOM after load
Wait
CSS / XPath
SPA
ready
When static HTML comes back empty
- Step 1
Probe the page
Try Crawler first. If the DOM is empty, move to Rendering.
- Step 2
Wait for state
Hold on selectors or a load delay until your fields exist.
- Step 3
Extract or capture
Pull HTML, or call Screenshot / WebUnlocker on the same session stack.
Browser extraction without a local fleet
Catalog scrapers, travel fares, and authenticated flows often need a real DOM. BrowserSolver runs headless sessions with routing and challenge handling so you do not maintain Chrome pools.
- Consistent TLS and header profiles across sequential scraper calls
- Configurable timeouts so slow targets fail predictably
- Escalate to WebUnlocker when AntiBot flags a vendor block on an allowlisted domain
- Same API key and credit balance across BrowserSolver scrape modes
Capture markup after JavaScript executes
Wait for the DOM state your parser expects, then pull HTML suitable for downstream extraction, diffing, or QA, not a static GET that misses hydrated content.
- Wait strategies: CSS/XPath selectors, seconds after load, or timeout bounds
- Block ad networks when you want leaner HTML for NLP or storage
- Need pixels instead of markup? Use the Website Screenshot endpoint (PNG, WebP, PDF)
- Same API key and credit balance across BrowserSolver scrape modes
When static scrapes return empty HTML
Escalate from Crawler to Rendering on the same credential when the markup only exists after JavaScript.
Selector waits
Hold until `#price`, `.listing`, or your XPath appears.
Load delays
Pause after navigation for late AJAX fills.
Ad blocking
Strip ad requests for cleaner extracts.
Timeouts
Cap wait time per target page.
Rendered HTML
Export DOM after client JS runs.
Headless stack
Built for dynamic scrapes and SPAs.
JS-ready
Hydrated markup after client scripts run
Waits
CSS, XPath, or timed post-load delays
Cleaner DOM
Optional ad and tracker blocking
Shared stack
Matches Screenshot and unlock sessions
Frequently asked questions
Credits, scrape types, and billing before your first production job.
Does Rendering return screenshots?
Rendering returns HTML after JavaScript runs. For PNG, WebP, or PDF captures, call Website Screenshot on the same browser stack.
Which vendors can Rendering handle alone?
Rendering is built for JavaScript execution and realistic sessions. Hard vendor blocks on protected retailers usually need Website WebUnlocker on an allowlisted domain.
Can I run interaction scenarios?
Use wait strategies and load delays for most scrapes. For full driver-style automation, see Puppeteer, Playwright, or Browser Automation.
How do I know Rendering is enough?
Run Website AntiBot when pass rates drop. If it names a WAF challenge on an allowlisted host, escalate to WebUnlocker.
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