Common Problems
Fixes for the most common Urlbox rendering problems — blocked or blank screenshots, missing content, broken full-page captures — and the options most people set.
Practical answers to the questions we hear most often, drawn from real usage and support tickets. Each entry is a problem → why it happens → the options that fix it, with copy-paste examples.
Find your problem
| What you see | Likely cause | Start with |
|---|---|---|
| A blank page, a CAPTCHA, "Access denied" or a 403 | Bot detection or Cloudflare | Avoiding blocks |
| Charts, images or text missing from the screenshot | Captured before late-loading content arrived | Getting complete renders |
| A full-page screenshot that's cut off, stretched, or repeats the header | Fixed headers, 100vh sections or lazy-loaded content during stitching | Full-page gotchas |
| Cookie banners, popups or ads over the content | Page clutter you haven't hidden | Most-used options |
| Renders you need to keep, or results you're polling for | Render URLs expire, and polling is slow | Saving to your storage |
All common problems
Most-used options
The options most people set on almost every render — page cleanup, engine version, retries, extraction.
Avoiding blocks
Blank or blocked screenshots from bot detection, Cloudflare, or 403s.
Getting complete renders
The screenshot is captured too early and misses late-loading content.
Full-page gotchas
Full-page screenshots cut off, stretched, or with duplicated headers.
Saving to your storage
Send renders to your own bucket, or get notified with a webhook.
Still stuck?
Try the request in the sandbox to see exactly what Urlbox renders, and check each option's details in Render Options. For deeper walkthroughs, see the Guides. If it still isn't right, contact support with the render ID and the options you used.