Screenshot API error ยท HTTP 503

Renderer busy

renderer_busy

All renderers were busy at the moment of the request. It did not start and is not billed. An async job that found no free renderer for 15 minutes fails with this code and is refunded.

How to recognize it

The API answers with status 503 and a JSON body with the message and the error.code renderer_busy, for example:

HTTP/1.1 503
Content-Type: application/json

{
  "error": {
    "code": "renderer_busy",
    "message": "The screenshot renderer is busy. Please retry in a few seconds."
  },
  "message": "The screenshot renderer is busy. Please retry in a few seconds."
}

How to fix it

  1. Send the request again after the seconds in Retry-After.

Retry

After the seconds in Retry-After.

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, AVIF 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