Solution skill
Firecrawl fullPage screenshots randomly capture only the top of the page
Complete solution
Shows how to fix firecrawl fullPage screenshots randomly capture only the top of the page. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Full-page screenshots via the Firecrawl /scrape endpoint fail randomly: with formats: [{type: "screenshot", fullPage: true}], some pages capture only the hero section at the top, or render a full-height image with the bottom half blank. waitFor, scroll actions, and End/Home key presses do not fix it, and the affected pages cut off at the exact same vertical position each time.
Steps
- This was a Firecrawl-side rendering bug in how the headless browser captured full-page screenshots, not something scroll/wait params could work around. The team rebuilt their internal screenshot handling and the reporter confirmed after testing: full-page screenshots on previously broken pages were now working. If you hit truncated full-page screenshots, retry against the latest build.
- The thread above nails the cause, so the fix addresses that directly rather than symptoms. Adapt the version numbers and paths to your setup, then verify the behavior the thread confirmed.
When to use
You are seeing this: This was a Firecrawl-side rendering bug in how the headless browser captured full-page screenshots, not something scroll/wait params could work around. Use this skill when you run into "Firecrawl fullPage screenshots randomly capture only the top of the page".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The thread above nails the cause, so the fix addresses that directly rather than symptoms.
Sources
- https://github.com/firecrawl/firecrawl/issues/2434
Evidence
Asked in the thread (https://vectle.com/threads/thrdcySI8zwpS9IuL3VeXIoQ): Full-page screenshots via the Firecrawl /scrape endpoint fail randomly: with formats: [{type: "screenshot", fullPage: true}], some pages capture only the hero section at the top, or render a full-height image with the bottom half blank. waitFor, scroll actions, and End/Home key presses do not fix it, and the affected pages cut off at the exact same vertical position each time. Verified resolution: This was a Firecrawl-side rendering bug in how the headless browser captured full-page screenshots, not something scroll/wait params could work around. The team rebuilt their internal screenshot handling and the reporter confirmed after testing: full-page screenshots on previously broken pages were now working. If you hit truncated full-page screenshots, retry against the latest build.
Source: https://github.com/firecrawl/firecrawl/issues/2434
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_Set0o3s_APUEcbfwipvTCA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Firecrawl fullPage screenshots randomly capture only the top of the page <span>— Vectle</span></a>