How to take a full-page screenshot of an Indian e-commerce product page in Chrome

To capture an entire Indian e-commerce product page in Chrome, open the page, let the content you need load, then open DevTools and choose More options → Capture a full size screenshot in the Device Toolbar. Chrome saves the full page, including content below the visible viewport. If you need a mobile-style layout, enable the Device Toolbar and choose a device preset or set the viewport before capturing. Then inspect the saved image to confirm the sections you wanted are present.

Choose the right kind of screenshot

Chrome offers different capture commands for different coverage:

Command	What it captures	Use it for
Capture screenshot	The currently visible viewport	A product image or section that fits on screen
Capture full size screenshot	The entire page, including content below the viewport	A full product listing or detail page
Capture area screenshot	A region you select	A specific part of the page

For a full product page, use the full-size command. Chrome documents the viewport and full-size options separately. See [Chrome’s DevTools Command Menu documentation](https://developer.chrome.com/docs/devtools/command-menu?authuser=2&hl=en).

Capture the full page in Chrome

1. Open the product page in Chrome and wait for the page to render.
2. If the page loads images or product details as you scroll, scroll through the sections you need first so they have a chance to load.
3. Open DevTools with Ctrl+Shift+I on Windows or Linux, or Command+Option+I on macOS. You can also right-click the page and choose Inspect.
4. Enable the Device Toolbar by clicking its device icon, or press Ctrl+Shift+M on Windows or Linux and Command+Shift+M on macOS.
5. In the Device Toolbar, open More options and select Capture a full size screenshot.
6. Open the saved image and check that the page sections, product images, and details you need are included.

Chrome’s [Device Mode guide](https://developer.chrome.com/docs/devtools/device-mode?authuser=1004904077) explains how to use the toolbar and configure a viewport.

Capture a mobile-style page

To capture how the product page lays out at a narrow width, turn on the Device Toolbar before taking the screenshot. Choose a device preset or enter viewport dimensions in the toolbar, then capture the full-size screenshot as above.

Device Mode is a simulation. Chrome describes it as a first-order approximation; it does not run the site on a real mobile device. Use it to inspect a responsive layout, but do not describe the resulting image as a real-phone screenshot. For device-specific behavior, verify on an actual device. The [Chrome Device Mode documentation](https://developer.chrome.com/docs/devtools/device-mode?authuser=1004904077) covers these limits.

Prepare dynamic product pages

E-commerce pages may reveal content only after scrolling or interaction. The Chrome documentation explains the general full-page capture command; it does not guarantee how a particular store handles lazy-loaded product photos, consent prompts, sticky controls, or other dynamic content.

• Scroll through the page before capture if the images or sections you need load on demand.
• Dismiss or interact with consent prompts if they cover content you need to document.
• Expand product details, size charts, or other sections when those are part of the intended capture.
• Check whether sticky bars obscure content in the saved image, and inspect the full result rather than relying on the preview.

These are practical checks, not guarantees that every site behaves the same way. Always review the output.

Common problems and fixes

Problem	Likely cause	What to try
The image shows only what was on screen	The viewport screenshot command was used	Choose Capture a full size screenshot from the Device Toolbar’s More options.
Some product images or details are missing	The page may load content on scroll or after interaction	Scroll through the needed sections, expand relevant controls, and capture again.
The layout does not look like a real phone	Device Mode simulates a viewport rather than running on phone hardware	Treat the image as a simulated responsive view, or inspect the page on a real device.
A banner covers part of the page	A consent prompt or sticky element is still visible	Handle the prompt or inspect the site’s available controls before taking another capture.
You captured a region instead of the whole page	The area screenshot command was selected	Use Capture a full size screenshot for complete page coverage.

Performance, reliability, and file handling

A full-page image can be much taller and larger than a viewport screenshot, so allow time for Chrome to render and save it. Very long pages may take longer to capture and produce large files. If the result is missing content, first check whether that content had loaded before the capture. The source documentation does not specify a maximum page length, capture time, or output file size, so these depend on the page and local environment.

For repeatable records, keep the viewport choice consistent, note whether it was a desktop or simulated mobile capture, and inspect the image after each capture. Chrome’s built-in command has no per-capture API charge; it runs in your browser.

Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server for developers. A single request returns a screenshot or PDF. Its capture flow accepts cookie and consent banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets before the shot; each cleanup step can be turned off. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and response headers identify the page verdict and billing status. Its MCP server lets Claude, Cursor, and other MCP clients use screenshot tools. See the ScreenshotNeo website and API documentation.

Example using cURL:

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.in/product -o shot.webp

Example using Python:

import requests

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

Example using Node.js:

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

ScreenshotNeo supports full-page capture, lazy-image loading, CSS selectors for capturing one element, dark mode, device presets and custom viewports, retina scale, custom CSS and JavaScript, waits, request blocking, headers and cookies, and image formats including PNG, JPEG, and WebP. It also offers PDF output, caching with a chosen TTL, signed image links, asynchronous jobs, bulk capture, a usage API, and an OpenAPI spec. The parameter names used by other screenshot APIs also work. Check the docs for available parameters and configuration.

The free plan includes 1,000 screenshots per month with no card. Paid plans start at $5 for 3,000 screenshots; yearly billing gives two months free, and every feature is available on every plan. Sign up for 1,000 free screenshots a month, with no card.

FAQ

Does Chrome capture content below the fold?

Yes. Choose Capture a full size screenshot; the regular screenshot command captures the visible viewport.

Is a Device Toolbar capture the same as a screenshot from an iPhone or Android phone?

No. It simulates a viewport in Chrome and is not a real-device run.

Can I capture only part of a product page?

Yes. Use Chrome’s area screenshot command from the Command Menu when you need a selected region rather than the whole page. See [Chrome’s Command Menu guide](https://developer.chrome.com/docs/devtools/command-menu?authuser=2&hl=en).

Should I trust the image without checking it?

No. Inspect it, especially when the page has content that loads on scroll or appears after interaction.