Apify Website Screenshot Actor Not Capturing the Full Page: Fixes
Fix Apify screenshots that stop at the fold. Check full-page mode, rendering delays, lazy loading, height limits, and Actor-specific settings.
If an Apify website screenshot contains only the top of a page, first confirm that the selected Actor is set to capture the full page rather than just the browser viewport. If it is already in full-page mode, check whether the page finished rendering, whether lazy-loaded content needs scrolling to appear, and whether the Actor limits screenshot height. Apify screenshot Actors use different input schemas, so check the exact Actor’s current Store page or API schema before changing field names.
1. Identify the exact Apify Actor
“Apify Website Screenshot Actor” does not identify one universal Actor or input schema. The Website Screenshot Generator example labels its setting “Screenshot type: fullPage”; another Actor’s schema uses a boolean named fullPage. These names and available controls are specific to the Actor. Check the Store page and the input for the Actor version used in the run. [Apify Store]
Before editing inputs, note the Actor name and version, the exact target URL, the run input, and the output record. This helps distinguish a wrong capture mode from a rendering delay or an output limit.
2. Select full-page capture
A viewport screenshot covers only the browser window. Full-page capture is the mode intended to include the page beyond the visible fold. Explicitly select the Actor’s whole-page option and confirm the saved input for the run has that setting enabled. [Apify Store]
Use the field or selection shown by that Actor’s current schema. Do not copy fullPage or another field name from a different Actor without checking that it is supported.
3. Allow the page to finish rendering
A page can continue rendering after its initial document load. Review the Actor’s supported page readiness option, such as a waitUntil selection if present, and any extra-delay input. The Website Screenshot Generator example documents a wait-until selection and an additional delay setting. No single wait value guarantees that every site is ready. [Website Screenshot Generator on Apify]
- Start with the Actor’s documented readiness setting.
- If visible sections still appear late, add a modest post-load delay using that Actor’s supported input.
- Repeat the capture and inspect whether the missing content appears. Increase the delay only as needed.
Longer waits can increase run time. They also cannot fix a page that requires scrolling to trigger content or an image-height cap that truncates the result.
4. Trigger lazy-loaded content
Some pages load images or sections as the visitor scrolls. A full-page capture may not include elements the page has not loaded yet. Check whether the selected Actor supports scrolling through the page before capture; some Actor schemas document such an option, but it is not universal. [Apify screenshot Actor schema example]
If the option exists, enable it and run again. If it does not, consult that Actor’s documentation for a supported way to trigger scrolling. Do not assume a delay alone will load content that only appears after scrolling.
5. Check maximum height and truncation
Some screenshot Actors expose a maximum page or image height. A long page can exceed that cap even when full-page capture is enabled. If the Actor reports the page height or a truncated status, compare those values with the configured maximum and adjust the cap within the Actor’s documented limits. These fields are Actor-specific. [Apify screenshot Actor schema example]
When the output ends at a consistent height across runs, inspect for a height cap first. If the cutoff varies with the target page or load conditions, check readiness and lazy loading as well.
6. Inspect the run’s output
Use the metadata provided by the exact Actor alongside the screenshot. Depending on the Actor, output records may include a screenshot key, dimensions, format, capture time, page height, or truncation status. Not every Actor exposes all of these fields. [Apify screenshot Actor output example]
- Only the initial viewport is present: verify full-page mode.
- The page is full height but some sections are empty: investigate rendering readiness and lazy loading.
- The image ends at a repeatable height: inspect the maximum-height setting and truncation metadata.
- The result differs between runs: compare timing, page state, and the exact run input.
7. Troubleshooting checklist
| Symptom | Likely cause | What to check |
|---|---|---|
| Screenshot stops at the fold | Viewport capture is selected | Set the Actor’s documented full-page mode and verify the run input. |
| Lower sections are missing or blank | Content had not rendered before capture | Check the supported readiness setting and post-load delay. |
| Images or cards appear only after scrolling | Lazy loading was not triggered | Enable the Actor’s scroll-to-bottom or equivalent option if available. |
| Very long pages end at a consistent point | Maximum screenshot height | Check the configured height cap and any page-height or truncation fields. |
| Copied input field has no effect or is rejected | Field belongs to another Actor’s schema | Use the current schema for the exact Actor and version. |
| One run works and another does not | Different page readiness or run inputs | Compare the exact URL, saved input, timing settings, and output metadata. |
8. Performance, reliability, and cost considerations
Waiting longer and scrolling through a page can add work to a capture. For repeatable results, tune the readiness delay to the target page, use scrolling only when lazy-loaded content requires it, and record the Actor version and input with each run. The reviewed Actor examples do not establish universal defaults, height ceilings, benchmarks, or costs; check the selected Actor’s current documentation and pricing for those details.
For a batch of URLs, inspect output metadata per URL rather than assuming one setting behaves identically on every page. Sites can render content differently, and the Actor’s available controls determine how those cases can be handled.
Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server. One GET request returns an image or PDF, with controls for full-page capture, lazy-image loading, viewport, wait conditions, and other capture options. See the API documentation.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpimport requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);ScreenshotNeo removes cookie banners, popups, and chat widgets before the shot. Bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000.
Sign up for 1,000 free screenshots a month, no card required.
FAQ
Is fullPage the right setting for every Apify screenshot Actor?
No. Actor schemas vary. Use the exact field or selection documented by the Actor you are running.
Will adding a delay always reveal missing content?
No. A delay can help with content that renders late, but lazy-loaded sections may need scrolling, and a height cap can still truncate the image.
Can I know the exact height limit without the Actor ID?
No. The limit and whether truncation is reported depend on the selected Actor. Check its current schema and output documentation.
What information should I include when asking for help?
Share the Actor name and version, sanitized run input, target page behavior, and relevant output metadata. Remove API keys, cookies, and other secrets first.
