How to Capture Website Screenshots for Indian Ecommerce Product Page Audits

Use Chrome DevTools to capture either the visible viewport or the entire product page, then repeat at the viewport sizes relevant to your audit. For each image, record the exact URL, capture date and time, viewport dimensions, and page state, such as the selected variant or an expanded offer panel. A screenshot documents one observed state; by itself, it does not show that the page always looked that way.

1. Decide what the screenshot needs to show

Choose the capture extent based on the question you are investigating:

• Viewport screenshot: records the portion of the page currently visible. Use it to examine what a visitor sees without scrolling, including the product image, price, primary offer, and purchase controls when they fit on screen.
• Full-size screenshot: records the whole page, including content outside the viewport. Use it when the audit concerns lower-page information such as specifications, shipping details, seller information, or reviews.

These outputs answer different questions. A full-page image can be useful for reviewing the whole layout, while a viewport image preserves the initial screen as seen at a specified size. Chrome DevTools provides commands for both capture types. Chrome DevTools: Capture screenshots

2. Capture a product page with Chrome DevTools

1. Open the product detail page in Chrome and note its exact URL.
2. Set the page state you want to document. For example, select the product variant under review, expand a details section, or expose the offer being evaluated. Record those interactions with the screenshot metadata.
3. Open DevTools: select More tools → Developer tools from Chrome’s menu, or use the browser’s DevTools keyboard shortcut.
4. Open the DevTools command menu. In the command menu, search for Capture screenshot to save the current viewport, or Capture full size screenshot to capture the full page. Menu labels and behavior may vary by Chrome version.
5. Save the image with a filename that helps identify the page and condition, such as product-url-mobile-390x844-2026-10-04.png. Keep the exact URL and capture details in the audit record as well; a filename alone is not enough context.

Chrome’s capture commands are browser UI actions, not a stable command-line interface. If your audit needs repeatable automated captures across many URLs, use browser automation or a screenshot API and keep the viewport and page-state settings consistent.

3. Capture mobile and responsive states

1. With DevTools open, enable the Device Toolbar.
2. Choose a device preset or enter the viewport dimensions your audit requires.
3. Reload the page if needed, set the relevant product-page state, and capture the viewport or full-size page.
4. Record the dimensions or preset for every image. Repeat at the other target widths and compare how content reflows.

The Device Toolbar changes the emulated viewport so you can inspect responsive layout. It does not make the screenshot evidence of how a particular physical phone rendered the page. Identify the capture as a browser emulation and include the actual viewport dimensions. Chrome DevTools: Device mode

4. Make captures useful for an audit

Record enough context to reproduce the observation

Store these details with each image:

• Exact page URL, including relevant query parameters.
• Capture date and time, including the time zone if the audit spans locations.
• Browser and viewport dimensions, or the Device Toolbar preset used.
• Capture extent: viewport or full size.
• Page state: selected variant, open panels, visible consent prompt, or other relevant interaction.
• Any capture limitations, such as content that failed to load or a page that required sign-in.

This context is a practical reproducibility record, not a claim that there is a universal legal evidence format.

Preserve the original

Keep an unaltered original when a screenshot supports an audit finding. If you annotate, crop, or redact a copy for a report, label the edited copy and retain the original. Describe what is directly visible separately from conclusions that need other evidence. A captured price or discount is evidence of what appeared in that observed state; it does not alone establish how long the offer was available or whether every shopper saw it.

Compare pages fairly

For a comparison set, align the viewport, capture extent, and page state where possible. If they differ, state the difference. Record the URL and time because product details and offers can change. When reporting advertising claims, distinguish the visible wording from your interpretation: the ASCI Code says claims and comparisons about objectively ascertainable facts should be capable of substantiation, and that advertisements should not mislead through implications or omissions. Those principles support careful reporting; they do not prescribe a screenshot format or determine compliance by themselves. ASCI Code, Chapter I

5. Indian ecommerce rules: keep dates and scope clear

The Department of Consumer Affairs lists the Consumer Protection (E-Commerce) Rules, 2020 and a 2026 amendment on its legislation page. The government announced that the 2026 amendment commences on 1 January 2027. For an audit conducted before that date, do not describe the announced amendment as already in force. Check the operative legal text, effective date, and applicability to the specific audit before drawing a regulatory conclusion. A screenshot workflow is not legal advice, and a screenshot alone does not establish compliance. Department of Consumer Affairs: Acts and Rules · Government announcement of 10 September 2026

6. Automate repeat captures with ScreenshotNeo

For repeatable captures or larger audit sets, ScreenshotNeo is a website screenshot API and MCP server. A GET request can return an image or PDF. Its capture options include full-page screenshots, CSS element capture, device presets or custom viewports, dark mode, custom headers and cookies, selector or delay waits, and bulk capture for up to 100 URLs per call. See the ScreenshotNeo API documentation for request options and configuration.

cURL

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

Python

import requests

response = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={
        "access_key": "YOUR_API_KEY",
        "url": "https://example.in/product/example",
        "full_page": "true",
    },
    timeout=90,
)
response.raise_for_status()
with open("product-full-page.webp", "wb") as image:
    image.write(response.content)
print("Page verdict:", response.headers.get("X-Page-Verdict"))
print("Billed:", response.headers.get("X-Billed"))

Node.js

const q = new URLSearchParams({
  access_key: 'YOUR_API_KEY',
  url: 'https://example.in/product/example',
  full_page: 'true',
});
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(({ writeFile }) =>
  writeFile('product-full-page.webp', Buffer.from(await res.arrayBuffer()))
);
console.log('Page verdict:', res.headers.get('X-Page-Verdict'));
console.log('Billed:', res.headers.get('X-Billed'));

For an audit screenshot at a specific mobile size, add the viewport parameters documented by ScreenshotNeo and save those dimensions with the resulting image. Use the same settings across the comparison set. Keep API keys private; do not embed a secret key in a public webpage or client-side script.

Or skip the browser setup

Make a one-call capture and adapt the target URL to the product page:

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

ScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before the shot. Bot checks, blank pages, and failed loads are never billed, and response headers identify the page verdict and billing status. Its MCP server lets AI agents use screenshot tools. The Free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots. Every feature is on every plan. Read the API docs, then sign up for 1,000 free screenshots a month with no card.

7. Troubleshooting and edge cases

Problem	Likely cause	What to do
The full-page capture misses or misplaces content	Some pages load or reposition content as you scroll; browser capture behavior can vary.	Wait for the page to settle, inspect the saved image, and use a consistent capture method. If the issue persists, capture sections or use an automated tool with an explicit wait condition.
Images or product details are blank	Lazy-loaded content may not have loaded yet, or the page request failed.	Scroll through the relevant area before capturing, wait for the content to appear, and note any missing content rather than treating it as absent from the live page.
The mobile image does not match a phone	Device Toolbar is viewport emulation, not a physical-device capture.	Record the emulated dimensions and preset. Use a real device if the audit specifically concerns device-only behavior.
A price or offer differs on a later capture	The page state changed, the offer expired, or personalization varied.	Retain URL and timestamp, record account or location conditions where relevant, and avoid generalizing one observation to all visitors.
A consent banner or popup obscures the page	The page is presenting a visitor prompt or overlay.	Decide whether the prompt itself is part of the audit. Record the state; do not silently remove it from evidence when its presence is relevant.
ScreenshotNeo response is not an image	The request may have returned an error or a page-verdict response.	Check the HTTP status and the X-Page-Verdict and X-Billed headers before treating the body as an image. Review the API docs for parameters and error handling.
ScreenshotNeo waits too long or captures early	The page may need a different wait condition, or a fixed delay may be insufficient.	Configure an appropriate selector, delay, or network-idle wait for the page; avoid assuming every ecommerce page has the same loading behavior.

8. Performance, reliability, and cost

For a manual audit of a few pages, DevTools avoids setting up automation and makes it easy to inspect a page interactively. Repeated manual captures take time and make consistent viewport settings and page state harder to maintain. For a larger audit, automate capture and store the request settings alongside the outputs.

Page readiness is a reliability concern: product images, offers, and lazy-loaded details may appear after initial navigation. Wait for the content relevant to the audit, then verify the saved output. No screenshot method can guarantee that a changing or personalized page will show the same state on every run. Preserve timestamps and capture conditions.

ScreenshotNeo bills only clean shots; bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing. Its response includes verdict and billing headers. Plans 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. All features are available on every plan; consult the current ScreenshotNeo site for plan details.

9. Frequently asked questions

Should an audit always use a full-page screenshot?

No. Use a viewport image for the initial visible experience and a full-size image when below-the-fold content matters. Many audits need both.

Does a screenshot prove what every shopper saw?

No. It records one page state under particular conditions. Personalization, location, account state, and time can change what appears.

Can I treat the 2026 ecommerce amendment as effective now?

The cited government announcement schedules commencement for 1 January 2027. Confirm current legal status and applicability for the date and subject of your audit.

Can screenshots replace substantiation for an advertising claim?

No. A screenshot can preserve visible wording, but the claim may need other evidence. Apply the relevant rules and review standards to the specific case.