Awesome Screenshot Cannot Capture a Page with Lazy-Loaded Images: What to Try

If Awesome Screenshot’s full-page capture is missing images, first check whether those images have actually appeared in the page. Scroll through the areas with missing images, wait for them to render, return to the top, and try the full-page capture again. This is a practical troubleshooting step, not a fix Awesome Screenshot documents or guarantees for lazy-loaded images.

Awesome Screenshot’s reviewed help instructions explain how to start a full-page capture and what to do when browser restrictions disable it. They do not describe a lazy-loading-specific setting or promise that pre-scrolling will fix a capture. If the page still comes out incorrectly, the documented next step is to send the affected URL through extension feedback or the Awesome Screenshot website.

1. Check that the images load in the page

A screenshot records what the browser has rendered. If an image has not appeared in the page, there may be nothing for the capture to include yet. Lazy-loaded images commonly wait until their part of the page is near the viewport, but individual sites can also require time, interaction, or other conditions before content appears.

Open the page normally and find an image that is missing from the screenshot.
Scroll to that part of the page. Wait and check whether the image appears.
Repeat for other areas with missing images, then return to the top.
Retry the full-page capture using the control for your browser.

Keep the result in perspective: this is a reasonable diagnostic step, not an Awesome Screenshot-confirmed remedy. If an image still does not appear in the page after scrolling and waiting, investigate the page’s loading behavior before treating the screenshot extension as the cause.

2. Retry with the documented full-page workflow

The control name depends on the browser. Awesome Screenshot’s help instructions say to initiate the extension, choose Capture, and then choose Full Page in Chrome, Edge, and compatible browsers. In Safari, choose Capture Full Page. In Firefox, choose Capture Entire Page. See Awesome Screenshot’s help center for its capture guidance.

Make sure the target page is open and the images you need are visible after scrolling.
Return to the top if you want a full-page result from the beginning of the page.
Start Awesome Screenshot and select the full-page option named for your browser.
Review the resulting capture, especially the sections that previously lacked images.

The reviewed instructions describe the normal capture workflow; they do not document a setting that forces every site’s lazy-loaded images to load. A page can still behave differently depending on its scripts, interactions, and loading logic.

3. If Full Page is unavailable

Browser restrictions can prevent an extension from accessing some pages. Awesome Screenshot gives browser-internal pages, such as chrome:// pages, as examples. That is a browser-access restriction and is separate from a normal webpage whose lazy-loaded images are absent.

If Full Page is disabled because of a browser restriction, use Visible Part or Entire Screen & App Window, then crop the result as needed.
If a partial result is enough, use Visible Part after scrolling until the target images have appeared.
If Full Page is available but the capture is still incorrect, send the affected page URL to Awesome Screenshot through extension feedback or its website.

The help guidance does not promise a response time or a particular support outcome.

4. Diagnose what kind of failure you have

What you see	What to check	Next step
The image is missing in both the page and the screenshot	Whether scrolling to the image or waiting makes it appear	Check the page’s loading behavior. A screenshot cannot include an image that has not rendered.
The image appears after scrolling, but not in the full-page capture	Whether you returned to the top and retried the browser’s full-page workflow	Retry once after scrolling through the missing-image areas. Treat this as troubleshooting, not a guaranteed fix.
Full Page is unavailable	Whether the browser restricts extension access to this page	Use Visible Part or Entire Screen & App Window and crop, as the help instructions suggest.
Full Page is available, but the result remains wrong	Whether the problem is repeatable on the same page	Send the page URL through extension feedback or the Awesome Screenshot website.
Only a particular section matters	Whether the images in that section appear after scrolling	Capture the visible part once the section has rendered.

5. Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server. Its full-page capture loads lazy images. Here is a one-call request for a full-page WebP screenshot:

curl -G "https://api.screenshotneo.com/v1/shot" \
  -d access_key=YOUR_API_KEY \
  --data-urlencode url=https://example.com \
  -d full_page=true \
  -d format=webp \
  -o page.webp

See the ScreenshotNeo API documentation for the request options. You can also make the request in Python:

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={
        "access_key": "YOUR_API_KEY",
        "url": "https://example.com",
        "full_page": "true",
        "format": "webp",
    },
    timeout=90,
)
r.raise_for_status()
open("page.webp", "wb").write(r.content)

Or use Node.js:

const q = new URLSearchParams({
  access_key: 'YOUR_API_KEY',
  url: 'https://example.com',
  full_page: 'true',
  format: 'webp',
});
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await import('node:fs/promises').then(fs => fs.writeFile('page.webp', Buffer.from(await res.arrayBuffer())));

ScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before the shot. Bot checks, blank pages, and failed loads are never billed; an MCP server lets AI agents take screenshots; and 1,000 screenshots a month are free with no card, with paid plans starting at $5 for 3,000. Sign up for 1,000 free screenshots a month, with no card required.

6. Reliability, performance, and cost considerations

For a manual capture, scrolling and waiting can help reveal whether images appear only when their section is reached. It does not guarantee that a full-page extension capture will include them, and the reviewed Awesome Screenshot help pages make no lazy-loading success claim. For repeatable captures, check the actual output for missing sections rather than assuming a successful capture control means every image loaded.

For API captures, ScreenshotNeo’s stated behavior includes full-page capture with lazy images loaded. Its billing distinguishes clean captures from bot checks, blank pages, failed loads, timeouts, and cache hits, which cost nothing; responses indicate the page verdict and billing status in headers. Choose image format and other capture options according to the output you need. Avoid repeatedly requesting the same page without a reason; caching with a chosen TTL is available when a cached result is appropriate. Current plan prices are Free: 1,000 shots/month; Starter: $5 for 3,000; Growth: $15 for 15,000; Pro: $39 for 60,000; Scale: $99 for 250,000; Business: $249 for 1,000,000. Yearly billing gives two months free, and every feature is available on every plan. See the documentation for configuration details.

7. Troubleshooting checklist

Image never appears in the browser: wait, scroll to its location, and check the page itself before capturing.
Image appears only after scrolling: scroll through the affected areas, wait, return to the top, then retry Full Page or Entire Page.
Full-page option is unavailable: check for a browser access restriction; use Visible Part or Entire Screen & App Window and crop.
Capture remains incorrect: record the affected page URL and report it using extension feedback or the vendor website.
Only part of the page is needed: use a visible-part capture after the relevant images have rendered.
Automated capture needs to be repeatable: use a screenshot API and verify the returned image and response status for the page you capture.

8. FAQ

Does Awesome Screenshot have a documented lazy-load switch?

The reviewed official help instructions do not describe a lazy-loading-specific option or guaranteed remedy.

Should I scroll the whole page before capturing?

It is a practical troubleshooting attempt when images appear as their sections enter view. It is not a vendor-documented guarantee, and site-specific scripts or interactions can still affect the result.

What is the Firefox option called?

The official instruction calls it Capture Entire Page; Chrome and Edge-compatible browsers use Full Page, while Safari uses Capture Full Page.

What should I send support?

Send the affected page URL through extension feedback or the Awesome Screenshot website when Full Page is available but produces an incorrect result.