When to use render_js
Set "render_js": true when the content you need is injected by JavaScript after the initial HTML loads. Common cases:
- Single-page applications (React, Vue, Angular)
- Infinite-scroll feeds where items appear after JS executes
- Pages behind login redirects that trigger on load
- Dynamic price or inventory widgets
render_js — it saves credits and latency.
How it works
Whenrender_js is true, the API navigates to the URL in a headless Chromium browser, waits for the network to settle, and captures the fully-rendered DOM. Each request gets a fresh, isolated browser context (cookies, storage, and cache are not shared with other requests) — the underlying browser process itself is kept warm and reused across requests for performance, not relaunched from scratch each time.
Rendering typically adds 2–5 seconds of latency.
Setting a timeout
Usetimeout_ms to cap how long the browser waits. The default is 10,000 ms (10 s) for inline requests. Async requests allow up to 300,000 ms (5 min).
timeout error code.
Device emulation
Emulate mobile or tablet viewports to reach responsive content:"desktop" (default), "mobile", "tablet".