Rendering error
How to fix the Scrnpix API 500 Rendering Error when the browser fails to capture a screenshot of the target page.
When Does This Happen?
This error occurs when the headless browser fails to load or screenshot the target page. Common causes include page load timeouts (15 second limit), JavaScript errors that crash the page, SSL certificate errors, or the target server refusing connections.
Reproduce This Error
curl -H "X-KEY: your-api-key" \ "https://api.scrnpix.com/screenshot?url=https%3A%2F%2Fhttpstat.us%2F504"
{"error": "Rendering error"}How to Fix
- 1Verify the target URL is accessible and returns a valid HTML page
- 2Check that the target page loads within 15 seconds
- 3Ensure the target server does not block headless browser User-Agent strings
- 4Try a simpler page to confirm your API setup is correct
- 5If the issue persists, the target page may have JavaScript errors preventing rendering
Correct Request
curl -H "X-KEY: your-api-key" \ "https://api.scrnpix.com/screenshot?url=https%3A%2F%2Fexample.com" \ --output screenshot.png
200 OK — returns the screenshot as a PNG image
Related Errors
Frequently Asked Questions
What is the page load timeout?
Scrnpix waits up to 15 seconds for the page to reach the networkidle0 state (no network requests for 500ms). Pages that take longer to load will trigger a rendering error. Optimize your target page's load time or simplify the content.
Does Scrnpix reveal the underlying error details?
No. For security reasons, the API returns a generic "Rendering error" message. Detailed error information is logged server-side only and is not exposed in the response to prevent information leakage.
Still Having Issues?
Check your API key and subscription status in the dashboard, or explore our language guides for integration examples.
Go to Dashboard