How to Capture Screenshots of Competitor Product Pages on Indian Ecommerce Sites

A screenshot records what a product page looked like in one browser session. For a useful competitor research record, open the specific listing, select the variant and delivery location you want to document, capture the relevant visible area or the full page, and save the original with its URL and capture time. Use a PDF when a printable page-shaped record is more useful, keeping in mind that print output can reflow or omit interactive elements.

This guide covers manual capture in a desktop browser, full-page capture in Chrome, print-to-PDF, evidence context, troubleshooting, and an API option for permitted workflows. A screenshot does not prove that a listing was generally available, accurate, or unchanged at another time.

1. Prepare the product page before capturing

Open the specific product URL in a desktop browser. Avoid relying on a search result or category page if the listing itself is what you need to document.
Select the relevant size, color, seller, offer, or other variant. Make the selection visible in the capture when possible.
If price or delivery availability matters, set the delivery location or pincode and preserve that context. Note the location separately if it does not appear in the captured page.
Wait until the page has finished loading and the details you care about are visible. If content loads as you scroll, inspect the full listing before using a full-page capture.
Choose an output: a visible screenshot for a detail that fits on screen, a full-page image for a long listing, or a PDF when printable or searchable page output is useful.

Product pages can differ by selected variant, seller, location, time, stock, and promotion. Record the conditions that matter alongside the capture so a reviewer knows what the image represents.

2. Capture the visible page with your operating system

For a specific price, offer, stock label, or product detail that fits on screen, an operating-system screenshot is usually the simplest option. The exact keyboard shortcut depends on your operating system and device. Use its built-in screenshot tool to capture the screen or a selected region, then save the image in a format such as PNG or JPEG.

Before capturing, make sure the browser shows the intended page and variant. If browser chrome or other on-screen content is not relevant, select only the page area. Keep the original image unchanged; add arrows, highlights, or notes to a separate working copy.

3. Capture a full-page screenshot in Chrome

For a long product listing, a Chrome Community answer describes using Developer Tools’ command menu to find the full-size screenshot command. These are community instructions rather than formal Chrome documentation, and Chrome menus may change.

Open the product page in Chrome and set its variant and delivery location.
Open Developer Tools with Ctrl + Shift + I on Windows or Linux, or Cmd + Option + I on Mac.
Open the command menu with Ctrl + Shift + P on Windows or Linux, or Cmd + Shift + P on Mac.
Search for Capture full size screenshot and select the matching command.
Save the resulting image, then open it to check that the page sections you need are present and readable.

If the command is missing, check that Developer Tools is open and try searching for “screenshot.” If the page is very long or content appears only after scrolling, inspect the saved image carefully; a full-size capture may not represent content that never loaded in the session.

4. Save a product page as a PDF

Chrome’s official help describes printing from the browser: open the page and choose File > Print, or press Ctrl + P on Windows or Linux and ⌘ + P on Mac. Select an available destination or print setting in the dialog. Where Save as PDF is available, save a separate PDF record. See Google Chrome Help: Print from Chrome.

A PDF and a screenshot serve different purposes. A screenshot preserves the page’s visible appearance in the browser session. Print output may reflow the layout or omit interactive elements, so open the PDF and confirm the relevant product details survived the conversion.

5. Preserve useful context with the capture

Keep the original capture and a small record of the conditions under which it was made. A practical record can include:

The product page URL and the date and time of capture in UTC.
The browser and device used.
The selected size, color, seller, offer, or other relevant variant.
The delivery location or pincode, when relevant.
Any visible price, stock, delivery, or promotion text you rely on.
Whether the file is a visible screenshot, full-page screenshot, or print-to-PDF output.

These are practical evidence-preservation recommendations, not a claim that a platform requires a particular format. Keep an unaltered original. If you annotate or crop a copy for a report, label that copy so it is distinguishable from the original.

6. Choose the capture method

Method	Best for	What to check
Operating-system screenshot	A visible detail or selected region	Whether the full price, variant, or offer you need fits in the captured area
Chrome full-page screenshot	A long product listing	Whether the saved image includes all relevant sections and remains readable
Chrome print-to-PDF	A printable or searchable page-shaped record	Whether printing changed the layout or omitted interactive content
Screenshot API	Repeated capture in a workflow where automated access is permitted	Site terms, access controls, loaded content, output, and the response status

7. Check site terms and access restrictions

Terms differ by platform and intended use. Flipkart’s cited Terms of Use restrict page scraping, robots, and similar or equivalent manual processes used to access, acquire, copy, or monitor platform content through means not purposely made available. The cited Myntra terms contain substantially similar restrictions. Amazon India’s Terms of Use describe a limited license for personal use and restrict certain commercial or derivative uses and systematic extraction or data-gathering tools without applicable permission.

Those clauses do not establish that every one-time screenshot is unlawful or that all screenshots are prohibited. They also do not settle questions about publication, copyright, fair dealing, contract formation, or legal process. Before repeated, automated, commercial, or public reuse, check the live terms for that specific platform. Respect access controls; do not bypass logins, bot checks, or technical restrictions. For consequential use, seek permission or legal advice.

8. Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server for developers. For a workflow where automated capture is permitted, a GET request can return an image or PDF. This example requests a screenshot of the target product URL; use the exact URL you are allowed to capture.

See the ScreenshotNeo API documentation for the API details.

cURL

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

Python

import requests

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

Node.js

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

ScreenshotNeo accepts cookie or consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and response headers report the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots. Every feature is on every plan. These capabilities do not remove the need to follow a target site’s terms and access restrictions.

9. Troubleshooting

Problem	Likely cause	What to do
The variant, seller, or offer is wrong	The page was captured before selecting the intended option	Return to the listing, select the right option, confirm it on the page, and capture again. Keep the earlier original if it is part of your record.
The delivery or price context is missing	The location was not set, or it is not visible in the captured area	Set the relevant location before capture and record it alongside the image if the page does not display it.
The full-page image is incomplete	Some content may not have loaded or may appear only after interaction or scrolling	Inspect the listing in the browser first, wait for relevant content, and verify the saved image section by section.
The screenshot is hard to read	The relevant text is too small in the full-page image	Capture the key section separately at readable size and retain the full-page capture as context.
The PDF looks different from the browser	Print output can reflow the page or omit interactive elements	Use a screenshot when browser appearance is the important record; inspect the PDF before sharing it.
A browser screenshot command is unavailable	Chrome’s command menu or interface may differ	Confirm Developer Tools is open, search the command menu for “screenshot,” or use an operating-system screenshot for the visible area.
An API capture is blank or fails	The page may not have loaded, a request may have timed out, or access may be restricted	Check the response and page verdict, confirm the URL is correct, and follow the site’s access rules. Do not try to evade bot checks or other controls.

10. Performance, reliability, and cost

For a one-off record, the built-in screenshot or print workflow avoids setting up an API and makes it easy to confirm the selected page state yourself. Full-page images can be less readable than a focused capture, so save both when the full listing and a specific detail matter.

For repeated permitted captures, an API can reduce manual steps, but a successful request alone does not establish that the page showed the intended variant or that its terms allow the workflow. Verify the output and preserve URL, timestamp, variant, and location context. Plan for timeouts or failed loads by checking the response and retrying only when appropriate. ScreenshotNeo says failed loads and timeouts are not billed; its response includes page-verdict and billing headers. Its listed monthly plans range from 1,000 free screenshots to paid tiers of 3,000 for $5, 15,000 for $15, 60,000 for $39, 250,000 for $99, and 1,000,000 for $249; yearly billing gives two months free. Every feature is available on every plan.

11. FAQ

Does one screenshot prove what every shopper saw?

No. It records one browser session at a particular time and under particular page conditions.

Should I use a screenshot or a PDF?

Use a screenshot when the page’s visible appearance matters. Use a PDF when printable or searchable page output is useful, and check for layout changes or missing interactive content.

Can I publish a competitor’s product screenshot?

That depends on the platform’s current terms and the intended use, as well as other legal considerations. Review the relevant terms and seek permission or legal advice when publication is consequential.

Can a screenshot API bypass marketplace restrictions?

No. An API is a capture method, not permission to bypass access controls or disregard a site’s terms.