How to capture a cookie banner screenshot on an Indian website in Gujarati

To capture a cookie banner on an Indian website in Gujarati, open the page in Chrome, translate it to Gujarati, leave the banner untouched, then use Chrome DevTools to capture the visible viewport. Check the saved image to make sure the banner remains visible and its Gujarati text is readable. If you need the whole page as well, use DevTools’ full-size screenshot option.

Translation changes the rendered page. If you need to document the wording exactly as the site originally served it, capture an original-language screenshot too and label the two images clearly. Browser translation and banner behavior can vary by site, so verify the result instead of assuming the banner will remain unchanged.

1. Open the page and preserve the banner

1. Open the exact page you need in desktop Chrome and let it finish loading.
2. If the goal is to document the first-visit consent prompt, do not click Accept, Reject, or settings before taking the screenshot.
3. Check whether a banner is actually present. Websites may show consent prompts differently depending on prior choices or site behavior.
4. If the banner is missing, consider whether you previously made a choice on the site. You can inspect the page in a fresh browser profile to check its first-visit state, but do not alter or misrepresent evidence from an existing session.

2. Translate the website into Gujarati in Chrome

Chrome Help documents two ways to translate a webpage: use the Translate control near the right side of the address bar, or right-click the page and select Translate. Choose Gujarati from the language selector. If the translation does not take effect, refresh the page and check again. The exact controls and labels can differ by platform or Chrome version. See Google Chrome Help: Translate pages and change Chrome languages.

1. Open the page with the cookie banner visible.
2. Select the Translate control in the address bar, or right-click the page and choose Translate.
3. Choose Gujarati as the target language.
4. Wait for the page to update, then inspect both the website and the banner.

Browser translation may not translate every interface element. Confirm that the banner is still visible and its text is legible. If the original wording or consent controls matter, take a separate screenshot before translation as well. A translated rendering is not proof of the exact language or legal wording originally served by the website.

3. Capture the banner with Chrome DevTools

Chrome DevTools offers a viewport screenshot and a full-size screenshot. Use the viewport capture when the banner and its surrounding context are what you need to show. Choose full size when the whole document is relevant. The saved image should contain enough page context to make the banner understandable.

1. Open DevTools with F12 or Ctrl+Shift+I on Windows/Linux, or Command+Option+I on macOS.
2. Open the device toolbar in DevTools. Its toggle is also available with Ctrl+Shift+M on Windows/Linux or Command+Shift+M on macOS.
3. Open the device toolbar’s More options menu.
4. Select Capture screenshot for the current visible viewport. Select Capture full size screenshot if you need the entire page, including content outside the viewport.
5. Open the saved image and check that the banner, surrounding page, and Gujarati text appear as intended.

See the official Chrome DevTools documentation for device mode and Chrome’s DevTools screenshot guidance. Menu labels and availability can change with Chrome versions.

4. Choose viewport or full-page capture

Capture	Use it when	Check
Visible viewport	You need to show the banner as it appears in the current browser view.	The banner is not below the fold or obscured, and enough surrounding content is visible.
Full page	You need the entire document for context or a record of content beyond the first screen.	The banner is included in the resulting image and remains readable at its displayed size.

For a record comparing the source wording with Gujarati, keep two clearly identified images: one captured before translation and one after translation. This is a documentation practice, not a guarantee that translation preserves the website’s original meaning.

5. Optional automation with Chrome DevTools Protocol

For repeatable browser automation, Chrome’s DevTools Protocol exposes Page.captureScreenshot. It supports image formats, viewport clipping, and capture beyond the viewport. Automation still needs to load the intended page state, avoid interacting with the consent controls, and verify the returned image. Consult the Chrome DevTools Protocol screenshot method for current parameters. The protocol is lower-level than the manual workflow, and the exact browser automation setup depends on your tooling.

6. Inspect and preserve the result

• Confirm the image opens and is not blank.
• Check that the banner is visible, not clipped, and not covered by another element.
• Read the Gujarati text at the image’s actual viewing size.
• Keep the original-language capture too when you need to distinguish translated content from the site’s source wording.
• Record which page and language state each screenshot represents. Do not describe a translated image as the original wording.

7. Troubleshooting

Problem	Likely cause	What to do
No cookie banner appears	The site does not show one in this session, or a prior consent choice affects the page.	Check the page state. If appropriate, inspect in a fresh browser profile. Do not claim a banner was present if it was not.
Gujarati translation does not start	The Translate control is unavailable, the language choice was not applied, or Chrome needs to reload the page.	Use the page context menu’s Translate option, choose Gujarati, and refresh if needed. Controls vary by platform and version.
The banner text stays in another language	Translation may not apply to every interface element.	Inspect the saved image and report which text remained untranslated. Keep the original-language capture when wording matters.
The screenshot omits part of the page	A viewport capture includes only what is currently visible.	Use Capture full size screenshot if you need content beyond the viewport; verify that the banner is included.
The banner is clipped or difficult to read	The viewport or image scale may not fit the banner and its context well.	Adjust the browser view before capture, then inspect the saved image. Choose the capture scope that best preserves readable context.

8. Performance, reliability, and evidence limits

For a single manual capture, DevTools avoids setting up a separate screenshot tool. A full-size image can be harder to inspect if the page is long, while a viewport capture is focused on the current view. Translation, site loading, and consent behavior are controlled by the browser and the website, so there is no universal guarantee that a particular Indian website will translate its banner or preserve the same layout.

For documentation, retain the original-language image when exact source wording matters and identify the translated image as a browser-translated rendering. The research for this guide covers desktop Chrome; the exact site, operating system, browser version, and evidence standard were not specified.

Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server. Its API can return a screenshot with one GET request; see the ScreenshotNeo documentation for the request options.

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

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

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

ScreenshotNeo accepts cookie or consent banners as a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. That cleanup is useful when you want a clean page image, but it may not suit this article’s goal of preserving a banner in the screenshot. Bot checks, blank pages, and failed loads are never billed. An MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000.

Sign up for 1,000 free screenshots a month, with no card required.

FAQ

How do I translate a website into Gujarati in Chrome?

Use Chrome’s address-bar Translate control or right-click the page and select Translate, then choose Gujarati. Refresh if the translation does not take effect.

Should I click Accept or Reject before taking the screenshot?

No, if your goal is to document the prompt before a choice is made. Leave the controls untouched and confirm the banner is visible in the saved image.

Does a Gujarati screenshot prove the site originally displayed Gujarati?

No. Browser translation changes the rendered page. Keep an original-language capture when you need to show the wording as served.

Can I guarantee a specific Indian website’s banner will translate?

No. Banner and translation behavior depend on the particular site and browser. Check the rendered page and screenshot directly.