If a full page screenshot is missing images or has blank sections, the page almost always had not finished showing that content when the capture happened. The three usual causes are lazy loading (images only load when you scroll near them), scroll-triggered animations (sections start invisible and fade in as you scroll) and a load delay that is too short for slow images, fonts and scripts. The fix is to give the page time and, where needed, scroll through it first. This guide explains each cause, how to recognize it and how to fix it in browsers and batch capture tools.
Recognize which problem you have
| What you see | Likely cause | Quick fix |
|---|---|---|
| Top of page fine, images lower down are blank, gray or blurry placeholders | Lazy loading | Scroll the whole page before capturing |
| Whole sections are empty or faded, but the space is there | Scroll-triggered animations | Scroll through so animations complete, or wait longer |
| Everything is missing or partly drawn, including near the top | Capture taken too early | Increase the load delay |
| Fonts look plain, then change in a later capture | Web fonts still loading | Increase the load delay |
| Embedded maps, videos or social posts are empty boxes | Third-party embeds loading slowly or blocked | Longer delay; some embeds may never render in captures |
Cause 1: Lazy loading
Lazy loading is a standard technique that makes pages load faster. Instead of downloading every image when the page opens, the browser waits until an image is about to scroll into view. Modern browsers support it natively with a simple loading="lazy" attribute, and many site builders and themes turn it on by default.
For visitors, it is invisible: images appear just before they scroll into view. For full-page screenshots it is a problem, because a tool that captures the whole page without scrolling never triggers the lower images. The result is a sharp header and blank or placeholder images further down.
How to fix it in a browser
- Open the page and let it load.
- Scroll slowly all the way to the bottom. Pressing the End key jumps too fast on some sites; scrolling with the mouse wheel or pressing Page Down repeatedly is more reliable.
- Wait a few seconds at the bottom, then press Home to return to the top.
- Now take the full-page capture, for example with Ctrl+Shift+S in Edge or the Capture full size screenshot command in Chrome DevTools.
Once the images have loaded, they stay loaded, so the capture includes them.
Cause 2: Scroll-triggered animations
Many sites animate sections as you scroll: text slides in, images fade up, counters tick over. Technically, the content starts hidden (often fully transparent) and an animation reveals it when it enters the viewport. If the page is captured without being scrolled, those sections are captured in their hidden starting state: the space is there, but it looks empty or washed out.
The fix is the same as for lazy loading: scroll through the page so every animation runs, then capture. Some animations replay each time a section re-enters the screen, which can leave a few sections mid-animation; wait a moment after scrolling back to the top before capturing.
Cause 3: The capture happened too soon
A browser reports a page as "loaded" when its main document and initial resources are ready. Plenty happens after that: web fonts swap in, sliders initialize, cookie banners appear, images from slower servers arrive and scripts build parts of the page. A screenshot taken at the "loaded" moment can catch all of that half-finished.
In a browser, the fix is patience: wait several seconds before capturing. In a batch tool, increase the load delay, the pause between the page loading and the screenshot being taken.
Bulk Captures waits for each page in a URL batch to finish loading before capturing it, and lets you add a load delay on top for pages that keep working after that. A delay of 2 to 5 seconds suits most sites; script-heavy pages, sites with large hero videos and slow servers may need longer.
Start with a test batch of a few of the slowest-looking pages. Find the delay that works for them, then use it for the whole list. A slightly longer delay costs a little time; a rerun costs much more.
Fixing missing images in a batch of URLs
When you capture a long list of pages, you cannot scroll each one by hand. Work through it in this order:
- Increase the load delay and rerun the affected pages. This fixes slow images, fonts and scripts.
- Check whether the affected pages share a template. If only blog posts or only product pages have the problem, it is probably a lazy-loading or animation feature of that template.
- Try a visible-area capture for those pages if the top section is what matters. Content near the top is rarely lazy loaded.
- Capture stubborn pages from your browser. Open them, scroll through as described above, then use a scrolling capture or the browser's full-page tool.
- If it is your own site, ask your developer whether there is a way to disable lazy loading for capture runs, or to load images eagerly on key pages.
Our guide on how to screenshot multiple websites at once covers setting up and checking a batch, including how to spot failed captures quickly by sorting the folder by file size.
Other things that look like missing images
Cookie and consent banners
A batch tool visits each page as a first-time visitor, so consent banners appear, and on some sites they cover part of the page or dim the rest of it. That is not missing content, but it can hide it. Note it in reports, or capture key pages from your browser after accepting the banner.
Blocked or geo-restricted content
Some embeds, such as videos or maps, only load for certain regions, need cookies or block automated visits. They may show as empty frames whatever delay you use.
Very tall pages being cut off
If the bottom of a long page is missing entirely, rather than blank, the image may have hit a format's size limit. WebP is limited to 16,383 pixels in height and JPG to 65,535. Save very long pages as PNG. Our guide to long screenshots that get cut off explains these limits.
Repeated headers
If a sticky header or chat widget appears over and over down the page, that is a stitching issue rather than missing content. See our guide to repeated headers in scrolling screenshots.
A checklist for complete full-page captures
- Wait for the page to finish loading, then wait a few seconds more.
- Scroll to the bottom slowly and back to the top for pages with lazy loading or animations.
- Close or accept banners if you need the content beneath them.
- Save very tall captures as PNG.
- In batches, set a sensible load delay, run a small test first, and rerun any pages whose files are suspiciously small.
Most missing-image problems disappear with those habits. Bulk Captures makes the batch part routine: set the delay once, and every page in the list gets the same chance to finish loading.
Frequently asked questions
Why are images missing at the bottom of my full page screenshot?
Most sites lazy load images, so they only download when you scroll near them. If the capture happens before that, those areas come out blank.
Does a longer load delay fix missing images?
Often, yes. A longer delay gives slow images, fonts and scripts time to finish. It will not help images that only load when the page is scrolled.
Why do some sections look faded or invisible?
Scroll-triggered animations start content hidden and fade it in as you scroll. If the page was never scrolled, those sections can be captured in their hidden state.
