How to Screenshot a Private Web Page When Login Uses an Authenticator App

Short answer: Sign in to the website through its normal password and authenticator-app flow. Once the private page is open, use a screenshot feature supported by your browser or device to capture only the information you need. Check the saved image before sharing it. If capture is blocked by a site or organization policy, ask the site owner or administrator for an approved way to document the page.

An authenticator app helps you prove that you are authorized to sign in; it is not part of the webpage screenshot. Do not include its current one-time code, recovery details, or unrelated account information in the image.

Open the website and go to its sign-in page.
Enter your password and complete the requested second step. Depending on the site, that may mean entering a code from an authenticator app or approving a sign-in notification.
Wait until the private page itself has loaded and is visible in the browser.

Google describes app-generated codes as one available method for completing its account verification step. The exact methods and recovery options vary by website and account setup, so follow that site’s own instructions. [Google Account Help: Get verification codes with Google Authenticator]

Keep the authenticator screen separate from the webpage capture. Microsoft says authenticator OTP codes do not require internet or mobile data, while sign-in notifications do require an internet connection. The app’s job is to complete the sign-in step; a screenshot of the page usually needs only the browser. [Microsoft Authenticator FAQ]

2. Capture the smallest useful part of the page

Choose a capture method that works in your installed browser and operating system and is allowed by the site and any work or school policy. Prefer a selection or region capture when the whole page is not needed.

Firefox’s built-in screenshot feature

Firefox’s screenshot guide describes selecting a visible area or a page, then saving the image or copying it to the clipboard. A download goes to Firefox’s default download folder. The exact controls can vary with browser version and platform; check the screenshot controls available in your current Firefox installation. [Mozilla Support: Take screenshots in Firefox]

Open the signed-in page in Firefox.
Use Firefox’s screenshot command or the browser interface available in your version.
Select the relevant area or page if prompted.
Choose Save or Copy, then locate the saved file or paste the copied image into an approved destination.

Mozilla’s documentation says Firefox Screenshots collects interaction data such as whether you use Copy or Save full page, but not the URL or details of the captured image. This statement applies to the documented Firefox feature; it does not describe other extensions, operating-system tools, cloud backups, or workplace monitoring. [Mozilla Support: Take screenshots in Firefox]

Other browser or device capture controls

If the browser’s own screenshot tool is unavailable or unsuitable, use a screenshot control supported by your device and browser, if policy permits. There is no single shortcut that applies to every device, operating system, browser version, or managed environment. Look up the current instructions for the device you are using rather than assuming a familiar key combination will work.

Firefox’s older project FAQ described Firefox Screenshots as unavailable in Private Browsing, with a reason related to downloads appearing in the normal downloads list. Because that FAQ is undated and may describe an older product state, check the interface in your installed version rather than treating it as a rule for all current releases. [MozillaWiki: Firefox Screenshots FAQ]

Open the saved or pasted image at full size and check what it contains. This is practical minimization advice: a screenshot can expose details beyond the passage you meant to document.

Crop away unrelated private content and browser areas that are not needed.
Check for account names, email addresses, customer details, recovery information, and one-time codes.
Confirm that the image is going to an approved location and recipient.
If you copied the capture to a clipboard, remember that pasting it elsewhere may place the same image in another app or document.

Do not assume that a capture method has no storage or sharing side effects. Firefox’s documented save action writes to its default download folder, while Copy puts the image on the clipboard. Handle the resulting file or clipboard content according to your organization’s rules.

4. If the screenshot is blocked

On a work, school, or otherwise managed device, a blocked screenshot may be an intentional policy control. Google documents Chrome Enterprise Premium controls that can permit or prevent screenshots on selected websites. The control can cover keyboard shortcuts and apps or extensions that use Chrome’s capture API; Google says the setting is unavailable on Linux. [Google Chrome Enterprise: Prevent users from taking screenshots]

Do not try to work around a control that the site or administrator has put in place.
Ask the administrator or site owner whether an approved exception or documentation process is available.
If you need a record for support or compliance, ask what information may be captured and where it should be stored.

Where capture is permitted, use the browser or device method the administrator approves. A screenshot service cannot legitimately turn an access restriction into permission to capture protected material.

5. If you cannot access the authenticator

Use the account’s official recovery route. Available options depend on the website and how you configured the account. Google Accounts, for example, may offer backup codes, app codes, security keys, or recovery email, but those options should not be assumed for another site. [Google Account Help: Get verification codes]

Microsoft Authenticator for Android has a separate Screen Capture setting that allows OTP codes to appear in screenshots; Microsoft says to turn it on in Settings and restart the app. This setting concerns screenshots of the authenticator’s OTP display. It is not normally needed to capture a signed-in webpage, and enabling it can expose the code itself. [Microsoft Authenticator FAQ]

Or skip the browser setup

If you are authorized to capture the page and can provide the required access through a supported request, ScreenshotNeo can return a screenshot through one API request. The API takes a URL and can return PNG, JPEG, WebP, or PDF. For pages that require a signed-in browser session, use the documented authentication and cookie options; an API request does not bypass the site’s login or your organization’s capture policy. See the ScreenshotNeo API documentation.

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}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', Buffer.from(await res.arrayBuffer())));

Replace the example URL with a page you are authorized to capture. The Python example uses the requests package. The Node.js example requires a Node version with global fetch and writes the response body to a file.

Cookie banners, newsletter popups, and chat widgets are removed before the shot; each cleanup step can be turned off.
Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed. Responses include page-verdict and billing headers.
An MCP server provides take_screenshot, get_page_info, and capture_pdf 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.

Create a free ScreenshotNeo account to get 1,000 screenshots a month with no card.

Troubleshooting

Problem	Likely cause	What to do
The private page does not load after entering a code	The code may have expired, the sign-in may need an approval notification, or the site may require another step.	Follow the site’s current sign-in prompt and request a fresh code if needed. Do not include the code in the screenshot.
The screenshot command is missing	The browser version, platform, or private-browsing mode may not expose that feature in the same way.	Check the current browser interface and use an approved device capture feature if available. Firefox’s older Private Browsing FAQ may not describe current releases.
Capture is blocked even with a keyboard shortcut	A managed browser or website policy may prevent capture through multiple methods.	Ask the administrator or site owner for an authorized capture or documentation process; do not attempt to bypass the restriction.
The screenshot is blank or misses content	The page may not have finished loading, or the chosen capture region may not cover the content.	Wait until the relevant content is visible, then capture again and inspect the image before sharing. If using an approved API, configure its wait behavior for the page.
You cannot find the downloaded image	The browser saved it to its default download folder or another configured location.	Check the browser’s downloads list and configured download location. Firefox documents saving to its default download folder.
The copied screenshot does not appear when pasted	The capture may have been saved rather than copied, or another clipboard action may have replaced it.	Repeat the capture and explicitly choose Copy, then paste promptly into an approved destination.
The authenticator code is not visible in an Android screenshot	Authenticator OTP screen capture may be disabled by its app setting.	Only if you have a specific, authorized need to capture the OTP display, consult Microsoft’s Authenticator instructions. For a webpage screenshot, keep the code out of the image.

Performance, reliability, and handling

Wait for the page: Capture after the private content is visibly loaded. A screenshot made during a redirect, loading state, or incomplete render may omit the information you need.
Limit the capture area: A smaller region is quicker to inspect and less likely to include unrelated sensitive information.
Check the output: Open the image before sending it. Confirm the required content is legible and the saved file is the expected one.
Protect the session: Do not put passwords, authenticator codes, or session cookies into an image or an unapproved service. Use only authentication methods allowed by the site and your organization.
For API capture: A service needs a supported way to access the page. Configure only the necessary authorization or cookies, protect API keys, and consider that page content may be sensitive. Consult the API documentation for supported capture and wait options.
Cost: Local browser and device capture does not require a screenshot API plan. ScreenshotNeo’s stated 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, and all features are on every plan. See the current ScreenshotNeo site for plan details.

FAQ

Does an authenticator app take the screenshot?

No. The authenticator completes the site’s sign-in step. Capture the page with an approved browser or device method after sign-in.

Can I screenshot a private page in Firefox Private Browsing?

Feature availability can vary by Firefox version. Check the screenshot controls in your installed browser; an older Mozilla project FAQ is not definitive for every current release.

Will the website know I took a screenshot?

This depends on the website and the capture method. The sources here do not establish a general rule, so consult the site owner or administrator if capture has policy or confidentiality implications.

What if the screenshot is for a support ticket?

Ask the support team what evidence they need and where to submit it. Capture only that information and remove unrelated account details before sending.

Can I send the screenshot to an AI tool for help?

Only if your site and organization allow it and the image contains no information you are not authorized to share with that tool. Review and minimize the image first.