How to Capture a Full-Page Screenshot of an Aadhaar Website Page Without Showing Personal Details

Use your browser or device’s full-page capture option to capture the entire Aadhaar webpage, then inspect the exported image and irreversibly remove or obscure every personal detail before sharing it. Do not assume a masked Aadhaar number, a cropped view, or a visual overlay makes the rest of the screenshot safe.

UIDAI defines masked Aadhaar as replacing the first eight digits with “xxxx-xxxx” while leaving the last four visible. That feature concerns the Aadhaar number; it does not automatically hide names, addresses, photographs, QR codes, contact details, account identifiers, or other information elsewhere on a webpage. UIDAI advises against putting Aadhaar details on public platforms. UIDAI’s FAQ and e-Aadhaar service information describe masked Aadhaar and its download routes.

1. Decide what the screenshot needs to show

Before capturing, identify the minimum information the recipient needs. A full-page screenshot can include more than the visible section: headers, footers, side panels, embedded content, pop-ups, and QR codes may all contain identifying details. If the purpose can be met with a smaller excerpt, share only that minimum necessary cropped information.

For high-risk sharing, avoid publishing the screenshot. UIDAI cautions against placing Aadhaar details on public platforms. Aadhaar may be used as identity proof and for transactions with due diligence, but that does not make a complete webpage screenshot appropriate to post publicly. UIDAI’s guidance provides its advice on Aadhaar use and sharing.

2. Capture the full page

Open the Aadhaar website page you need and wait for it to finish loading.
Use the full-page screenshot function available in your browser or device. Choose the option that captures the whole page, rather than only the current viewport, if your device offers both.
Save or export the resulting image locally. Do not share it yet.
Open the image at full size and review the entire capture, from the first header area through the footer.

Browser menus and full-page capture support vary by browser, device, and page. This workflow is browser-neutral; exact menu labels and reliable redaction behavior are not established here. If your current browser or device does not provide a full-page capture, use another capture method you can verify, or capture the necessary sections individually and review the assembled result.

3. Find every detail that could identify someone

Inspect the full exported image, not just the page in the browser. Check for:

The full Aadhaar number, including the last four digits that remain visible in a masked Aadhaar.
A person’s name, address, date of birth, photograph, signature, or other visible profile information.
QR codes and barcodes, which may encode information that is not readable as ordinary text.
Phone numbers, email addresses, account or application identifiers, and transaction details.
Details that appear in page headers or footers, side panels, dialogs, notifications, or pop-ups.

Masked Aadhaar is a way to download an e-Aadhaar in which the first eight Aadhaar digits are replaced and the last four remain visible. UIDAI identifies MyAadhaar and the mAadhaar app as routes for downloading e-Aadhaar. It is not a general webpage-redaction feature, and it does not establish that unrelated fields or codes in a screenshot are hidden.

4. Redact the image and verify the exported file

Make a working copy of the captured image so you retain an unedited original privately if needed.
Use an image editor that removes the selected pixels or applies irreversible redaction. Cover each sensitive item completely, including the last four Aadhaar digits if they are not needed.
Export the edited image as a new file.
Close and reopen the exported file. Zoom in and inspect every redacted area and the whole page for missed details.
Share only the verified exported file. Avoid sharing an editable project file or the unredacted original.

A decorative shape or translucent overlay should not be assumed to remove the underlying image data. For safer sharing, use a redaction operation that irreversibly removes or obscures the image pixels, then verify the exported file itself. This is practical image-handling guidance, not a UIDAI-specific rule.

5. ScreenshotNeo option for the capture step

If you need an API to capture the webpage, ScreenshotNeo accepts a URL in one GET request and returns an image or PDF. Its clean-shot processing accepts cookie or consent banners like a visitor and removes more than 60 known consent platforms, newsletter pop-ups, and chat widgets before capture. That can reduce incidental page clutter, but it does not identify or redact Aadhaar numbers or other personal details. You must still inspect and redact the result before sharing.

Use a URL you are authorized to access and do not put personal Aadhaar data in a URL or API request. For a public page, a basic request looks like this:

curl -G "https://api.screenshotneo.com/v1/shot" \
  -d access_key=YOUR_API_KEY \
  --data-urlencode url=https://uidai.gov.in/ \
  -o aadhaar-page.webp

See the ScreenshotNeo API documentation for request options and setup. The example captures the supplied URL; it does not bypass access controls or make sensitive content safe to publish.

Python

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={
        "access_key": "YOUR_API_KEY",
        "url": "https://uidai.gov.in/",
    },
    timeout=90,
)
r.raise_for_status()
with open("aadhaar-page.webp", "wb") as image:
    image.write(r.content)

Node.js

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

ScreenshotNeo responses indicate the page verdict and billing status in headers. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing. A clean capture is not a privacy review: inspect the returned file and redact all identifying content before sending or posting it.

6. Troubleshooting

Problem	Likely cause	What to do
The image contains only the visible screen	The chosen capture option took a viewport screenshot, or the browser/device does not support full-page capture for that page.	Look for a full-page option in the capture flow. If none is available, use a method that captures the full document or capture sections and check the result for gaps and overlap.
Content is missing near the bottom	The page may load content as you scroll, or the capture completed before content appeared.	Wait for the page to load and check the exported image against the page. Capture the needed content in sections if the full-page method omits it.
A masked Aadhaar still reveals information	Masked Aadhaar only replaces the first eight Aadhaar digits; the last four remain visible, and other page details are outside that masking.	Redact the last four digits if unnecessary, then separately review names, addresses, photos, QR codes, contact details, and identifiers.
Details remain visible under a cover shape	The editor may have placed a decorative or translucent overlay over the original pixels.	Apply irreversible pixel removal or redaction, export a new image, reopen it, and inspect the result.
A capture service returns a blank, failed, or challenge page	The page may not have loaded, may require interaction or authorization, or may present a bot check.	Do not treat that result as a valid screenshot. Use a page and access method you are authorized to use, and verify the captured image before redacting or sharing.

7. Performance, reliability, and cost considerations

Full-page images can be much taller and larger than viewport captures, so they take longer to review and may be harder to share. Capture only what the recipient needs. Pages with lazy-loaded content or dynamic elements may not appear consistently in a single capture; inspect the complete exported file and use section captures when necessary.

For any capture method, verify that the output is complete and legible before treating it as evidence or sharing it. A successful capture does not prove that every page element loaded, and automated capture does not replace manual privacy review.

ScreenshotNeo offers 1,000 shots per month free without a card. Paid plans start at $5 for 3,000 shots; higher plans are listed on its site, and yearly billing gives two months free. Only clean shots are billed; failed loads, bot checks or CAPTCHAs, blank pages, timeouts, and cache hits are not billed. These service billing rules do not change the need to review and redact the resulting image.

8. Or skip the browser setup

ScreenshotNeo can capture a public page with one request. Cookie banners, pop-ups, and chat widgets are removed before the shot. 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, and paid plans start at $5 for 3,000.

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

See the API docs, then sign up for 1,000 free screenshots a month with no card. Always review and irreversibly redact personal details in the output before sharing it.

9. FAQ

Does a full-page screenshot become anonymous if I use masked Aadhaar?

No. Masked Aadhaar replaces the first eight digits of the Aadhaar number and leaves the last four visible. Other identifying details in the screenshot need separate review and redaction.

Removing the number alone may leave names, addresses, photos, QR codes, or other identifiers visible. UIDAI advises against putting Aadhaar details on public platforms; avoid public posting when possible and share only the minimum necessary information.

Does ScreenshotNeo redact Aadhaar details?

No. Its described cleanup removes known consent banners, newsletter pop-ups, and chat widgets. It does not automatically detect or redact personal Aadhaar details.

Does UIDAI’s physical-record redaction rule apply to screenshots?

The cited regulation concerns requesting entities redacting the first eight digits on certain physical forms or photocopies before storage. It should not be described as a screenshot-specific requirement.