Render JavaScript before the page comes back
JavaScript rendering loads the page in a real browser, so content that scripts add after the first HTML is part of the result. In a Standard request you set render_js=true, and ScrapeDrive picks the browser engine.
500 credits after you confirm your email. No card.

What this request asks for
- render_js=true
- Starts the request in a browser instead of a fast HTTP client.
- X-Sdrive-Credits
- Reports the settled charge. 10 credits for a datacenter browser request.
What it does for a request
- Starts in a browser
- With render_js=true the request starts in a real browser. The default, false, starts with a fast HTTP client.
- Makes browser settings available
- Browser waits need it in Standard mode. A screenshot switches a browser on by itself. See browser waits.
- Blocks heavy resources by default
- In a browser run, images, CSS, fonts, ads and tracker scripts are blocked by default so the page loads faster. Set block_resources or block_ads to false to load them.
- Adds 5 credits
- A datacenter browser request costs 10 credits. A residential browser request costs 15.
When to use it
Use it when
- The first HTML has an empty container and the records arrive after scripts run.
- You need to wait for an element that scripts add.
- You need the mobile layout a browser renders. Add device_type=mobile.
Leave it out when
- The data is already in the HTML a plain request returns. That request costs 5 credits.
- You use Auto mode. Leave render_js out, because Auto decides between HTTP and browser itself.
How to set it
render_js
true or false
Standard mode only. The default is false.
block_resources
true or false
Browser runs only. The default is true. A screenshot turns it off.
block_ads
true or false
Browser runs only. The default is true. Independent of block_resources.
device_type
desktop or mobile
The emulated viewport and user agent. The default is desktop.
Limits to plan for
- A browser job on a hard site can take longer than the 120 second sync limit and fail. Send those jobs as async requests.
- Rendering does not sign in to a site, and the API has no parameters to click, scroll or type.
- A page the site delivered is charged even when it is an error page or not the content you expected.
Other features
Start with a plain request. Add browser, routing or waiting settings only when the page needs them.
Automatic routing
ScrapeDrive picks HTTP or browser, proxy pool and location, under the max_credits ceiling you set.
See the feature, Automatic routingProxy routing
Send a Standard request through datacenter or residential proxies, or through your own proxy.
See the feature, Proxy routingGeo targeting
Route a residential Standard request through the country you name with proxy_country.
See the feature, Geo targetingWebpage screenshots
Add an image of the viewport, the full page or one element to a request.
See the feature, Webpage screenshotsOutput formats
Choose HTML, visible text or Markdown with result_type, at the same price.
See the feature, Output formatsAsync requests
Get a job id at once, then poll for the result or receive it at an HTTPS webhook.
See the feature, Async requestsBrowser waits
Hold a browser request for a load event, a CSS selector or a fixed delay.
See the feature, Browser waitsHeaders and sessions
Pass your own headers to the site and keep one proxy session across related requests.
See the feature, Headers and sessionsCost controls
Work out the price from the parameters, cap Auto with max_credits and read the settled charge.
See the feature, Cost controls
Try JavaScript rendering on your page
Paste a page URL into the Playground and see exactly what ScrapeDrive returns.
500 credits after you confirm your email. No card.
