Screenshot API error ยท HTTP 500

Render failed

render_failed

With HTML input (html), the HTML could not be rendered for a reason not covered by another error. A URL that fails this way is answered with a plain 500 without this code; write to support with its X-Request-Id.

How to recognize it

The API answers with status 500 and a JSON body with the message, for example:

HTTP/1.1 500
Content-Type: application/json

{
  "message": "The page could not be rendered."
}

How to fix it

  1. Send the request again; if it keeps failing, write to support@screenshotbase.com with the X-Request-Id of the response.
  2. Check the HTML for scripts that crash the page or loop forever.

Billing

Not billed: a request answered with this error does not count against your quota.

Every response carries an X-Request-Id header. If this page does not explain the error, write to support@screenshotbase.com with that id. All statuses: status codes.

Other API errors

Screenshot API

Take screenshots from your code

screenshotbase renders any website in a real browser and returns the image: full page or viewport, any device size, retina, from 100+ countries, with cookie banners and ads hidden.

/v1/take documentation Screenshot API All documentation

300 free screenshots every month. No credit card required.

GET https://api.screenshotbase.com/v1/take?url=https://example.com&full_page=true

# Response: the image (PNG, JPG, WebP or GIF)
curl -G "https://api.screenshotbase.com/v1/take" \
  --data-urlencode "url=https://example.com" \
  -d viewport_width=1280 -d viewport_height=800 \
  -d format=png \
  -H "apikey: YOUR-API-KEY" \
  -o screenshot.png

More free tools

Start using our Screenshot API for free today!

Get 300 requests / month for free