How to Capture Lazy-Loaded Images in a Wix Website Screenshot

To capture lazy-loaded images on a Wix page, open the published page in Chrome, scroll through it in sections and wait for each image to become sharp, return to the top, then use Chrome DevTools’ full-size screenshot command. Wix loads media as it enters the visitor’s viewport and may show low-resolution placeholders while sharper images load. A full-page capture includes content outside the viewport, but the capture command does not guarantee that every image or interactive element has finished loading. Check the saved image.

Why images may be missing or blurry

Wix enables lazy loading for images and videos. This delays media loading until it appears in the viewport. Wix also describes using low-resolution placeholders while high-resolution images load in the background; the sharper versions replace placeholders when ready. That means capturing a long page before visiting its lower sections can leave some media unloaded or blurry. Wix says its built-in lazy loading cannot be turned off, so prepare the page by scrolling and waiting rather than looking for a dashboard switch. See Wix’s guidance on lazy loading and performance-focused design and how Wix improves site loading time.

Capture the published Wix page in Chrome

1. Open the live page. Use the published URL in Chrome, not the Wix editor. Make sure the page is accessible and that any sign-in or consent step needed to view it is complete.
2. Scroll through the page in viewport-sized sections. Move down until each major image section enters view. Pause while images load. For images that look soft, wait until the sharper version appears.
3. Expose interactive content. If the page contains a gallery, carousel, load-more control, or other section that requires an action, use its controls to reveal the specific images you need. Wait for those images too. A normal scroll may not reveal content that depends on interaction.
4. Return to the top. This gives you a consistent starting point before making the full-page capture.
5. Open DevTools Device Mode. Open Chrome DevTools, then turn on Device Mode if it is not already active. In Device Mode, open the More options menu and choose Capture a full size screenshot. Chrome documents this command as capturing the whole page, including content outside the visible viewport. See Chrome’s Device Mode guide.
6. Inspect the saved screenshot. Check image sharpness and completeness, especially in lower sections and galleries. If an image is missing or still a placeholder, revisit that section, trigger any relevant control, wait for the image to resolve, then capture again. For a single region, Chrome’s Command Menu includes Capture area screenshot; use Ctrl+Shift+P on Windows or Linux, or Command+Shift+P on Mac, type “screenshot,” and select the area capture command. Area capture does not work when DevTools is undocked. See Chrome’s Command Menu guide.

What the full-size command does: it captures the page beyond the visible viewport. It is not a promise that every Wix image, animation, gallery item, or third-party widget has loaded. Scrolling first triggers the page’s loading behavior; checking the resulting image confirms whether the content was ready.

Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server. Its full-page capture loads lazy images. One GET request returns an image or PDF; the example below saves a screenshot of a Wix page as WebP. See the ScreenshotNeo API documentation for request options.

cURL

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

Python

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={
        "access_key": "YOUR_API_KEY",
        "url": "https://example.wixsite.com/site/page",
    },
    timeout=90,
)
r.raise_for_status()
with open("wix-page.webp", "wb") as screenshot:
    screenshot.write(r.content)

Node.js

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

Replace the example URL with the published Wix page and provide your API key. ScreenshotNeo removes cookie and consent banners, newsletter popups, and chat widgets before capture; each cleanup step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers report the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients. The Free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots.

Create a free ScreenshotNeo account and get 1,000 screenshots a month with no card.

Troubleshooting

Symptom	Likely cause	What to do
An image is blurry in the screenshot.	The low-resolution placeholder was captured before its high-resolution replacement finished loading.	Scroll until the image is visible and wait longer. Confirm it looks sharp in the browser before taking another capture. Wix describes the sharper media replacing placeholders in the background.
Images near the bottom are blank or absent.	Those sections may not have entered the viewport before capture, or their requests may not have completed.	Scroll down in stages, pause at each section, then return to the top and capture again. Check the saved image afterward.
Some gallery images are missing.	The gallery may reveal items only after scrolling within it or using its controls.	Visit the gallery, expose the items you need with its controls, wait for them to load, and capture again. Gallery behavior varies by page and widget.
The screenshot is incomplete even though you used full-size capture.	Full-size capture extends the capture area; it does not itself guarantee that every page-specific image or interaction has completed.	Trigger loading by visiting affected sections, wait for media to resolve, and inspect a fresh capture.
You cannot find the full-size capture command.	You may not be in Device Mode, or the command may be in its More options menu.	Open DevTools, enable Device Mode, then open More options and select Capture a full size screenshot.
Area capture does not work.	Chrome’s Command Menu area capture requires DevTools to be docked.	Dock DevTools, open the Command Menu with Ctrl+Shift+P or Command+Shift+P, search “screenshot,” and choose Capture area screenshot.
A section remains blank or takes an unusually long time.	The page, network, or an embedded element may not have finished loading or may be unavailable.	Wait and reload the published page if needed. Check whether the content appears in the live page before treating the screenshot as complete.

Performance and reliability tips

• Use staged scrolling on long pages. It takes longer than an immediate capture, but gives lazy-loaded sections an opportunity to request their images. There is no documented universal wait time; use whether the image has visibly sharpened as your cue.
• Keep the browser and page state consistent. Use the same viewport and page state when recapturing so you can compare results. If content changes with a gallery selection or other interaction, reproduce that state before capture.
• Verify the output instead of assuming success. Review the beginning, middle, and bottom of long screenshots, plus interactive areas. Revisit any blurry or missing section and capture again.
• Use area capture for a focused region. It can be simpler when you need one visible section rather than a very long page. It does not replace the scrolling preparation for content that has not loaded.
• Use the Network panel when diagnosing timing. Chrome DevTools can capture screenshots during page loading and correlate them with network activity. That view is useful for diagnosing load timing; it is separate from saving the final full-page image.

FAQ

Can I disable Wix lazy loading?

Wix says its built-in lazy loading cannot be turned off. Scroll through the page and wait for the images to load before capturing.

Do I need to open the Wix editor?

No. This workflow uses the published page in Chrome.

Does a full-size screenshot include content below the fold?

Yes. Chrome describes the Device Mode full-size screenshot command as capturing the entire page, including off-screen content. You should still verify that lazy-loaded and interactive media had finished loading.

What if I only need one section?

Use Chrome DevTools’ area screenshot command for a selected region. If that section contains lazy-loaded media, visit it and wait for the media first.