How to Take a Full-Page Screenshot of a Password-Protected Website

To take a full-page screenshot of a password-protected website, first sign in through the site’s normal login flow in your browser, open the page you are authorized to view, and use the browser’s full-page capture tool. Firefox offers Save full page. In Chrome, use DevTools device mode and choose Capture a full size screenshot. These tools capture the page rendered in your signed-in browser; they do not require a separate screenshot login or a password bypass.

Capture and share only information you are authorized to access and disclose. If your organization or the site blocks screenshots, use its approved export process or ask an administrator for an authorized way to obtain the information.

1. Sign in and prepare the page

1. Open the website in the browser profile where you normally sign in.
2. Complete the site’s regular authentication flow, including any required multi-factor prompt.
3. Navigate to the page you need. Confirm that the page shows the expected account or record.
4. Wait for the specific content to load. Expand sections or reveal data you need included in the image.
5. Consider whether the page contains names, account details, messages, or other private information. Plan to inspect and redact sensitive details before sharing.

The capture is of the page currently rendered in that browser session. It does not grant access to the site or make the screenshot safe to distribute.

2. Capture the whole page in Firefox

1. Open the signed-in page.
2. Right-click an empty area of the page and choose Take Screenshot. Mozilla also documents the shortcut Ctrl+Shift+S on Windows/Linux and Command+Shift+S on macOS.
3. Choose Save full page in the screenshot controls.
4. Save the image, or use the available copy option if you need it on the clipboard.
5. Open the saved image and check its top, bottom, and any important sections before sharing it.

Firefox’s screenshot tool supports full-page capture and saving or copying the image. See Mozilla’s Firefox screenshot instructions.

If the Firefox screenshot button is missing

Open Developer Tools, go to its settings, and enable Take a screenshot of the entire page under Available Toolbox Buttons. Mozilla also documents a Web Console :screenshot helper with options including --fullpage, --delay, --filename, and --selector. The selector option captures one element and its descendants rather than the entire page. See Firefox Source Docs: Taking screenshots.

3. Capture the whole page in Chrome

1. Open the signed-in page in Chrome and open DevTools.
2. Turn on the device toolbar in DevTools.
3. Open the device toolbar’s More options menu.
4. Select Capture a full size screenshot.
5. Open the downloaded image and verify that the content you need appears correctly.

Chrome documents this command as capturing the whole page, including content outside the viewport. Menu labels can change between versions, so refer to Chrome’s device mode documentation if the menu differs.

4. Check that the screenshot is complete

A full-page command captures the page beyond the visible viewport, but complex pages do not always behave like one simple scrolling document. Before you use the result:

• Check the first and last sections for clipping or missing content.
• Look for gaps, repeated sections, or content that loaded only after scrolling.
• Check components with their own scrollbars. A page-level screenshot may not include every item inside an independently scrolling panel.
• For lazy-loaded content, scroll through the page first so the required images or sections have a chance to load, then capture again.
• Make sure the correct signed-in account, record, and page are visible.
• Inspect for private information and redact anything unnecessary before sharing or storing the image in a shared location.

Browser documentation describes the full-page capture feature; it does not guarantee that every site’s dynamic content or nested scroll layout will render perfectly. Checking the output is a practical safeguard.

5. If the browser method does not work

Symptom	Likely cause	What to do
The screenshot shows a login page	The browser was not signed in to the relevant account, the session expired, or the page redirected.	Sign in through the site’s normal flow, reopen the target page, confirm the content is visible, and capture again.
Some content is missing	The page was still loading, content loads as you scroll, or a section has its own scroll area.	Wait for the needed content, scroll to trigger lazy loading, inspect nested panels, and capture again. If the page has an approved export, use it when that better preserves the data.
Firefox has no screenshot control	The screenshot toolbox button may not be enabled or the interface differs in your version.	Enable Take a screenshot of the entire page in Developer Tools settings, or use Firefox’s page screenshot interface. See the Mozilla documentation linked above.
Chrome’s menu item is hard to find	The device toolbar is not enabled, or DevTools labels differ in your Chrome version.	Enable the device toolbar, open its More options menu, and consult Chrome’s current device mode documentation.
The capture is blocked or protected content appears black	A site, managed browser, or organization policy may restrict screenshots.	Do not try to defeat the restriction. Ask the site or administrator about an approved export or authorized capture method. Google documents managed Chrome screenshot prevention, and a W3C TPAC presentation describes protected content appearing black in Edge when capture prevention is active. See Chrome screenshot prevention policy and the W3C TPAC 2024 materials.
The image contains information you should not share	A signed-in page may show account or personal details.	Keep the original access-controlled, redact unnecessary information in a suitable editor, and share only with authorized recipients.

6. Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server. For a page the API can access, one GET request returns an image or PDF. Use the documented authentication options when a protected page requires credentials; an API request does not inherit the cookies from your local signed-in browser. Check the ScreenshotNeo documentation for supported headers, cookies, and authorization configuration before sending credentials. Keep API keys and session cookies private.

The following calls show the basic request shape for an accessible target. Save the response as an image and inspect it. For a protected page, configure the required authentication as documented for the API.

cURL

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/account/page -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/account/page"},
    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/account/page'
});
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 (await import('node:fs/promises')).writeFile('shot.webp', bytes);

ScreenshotNeo removes cookie and consent banners, newsletter popups, and chat widgets before capture; each of those steps can be turned off. Bot checks, blank pages, failed loads, timeouts, and cache hits cost nothing, and response headers identify the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf for AI agents and MCP clients.

The Free plan includes 1,000 shots a month with no card. Paid plans start at $5 for 3,000 shots; all listed features are on every plan, and yearly billing gives two months free. Create a free account for 1,000 screenshots a month, with no card.

7. Performance, reliability, and cost

Browser capture: Firefox and Chrome’s documented workflows are built into the browsers and require no screenshot service for a one-off capture. Capture time depends on the page and the content that must render. Very long pages and high-resolution images can take longer and produce larger files. Wait for the content you need, and inspect the image instead of assuming that a completed command means every dynamic section is present.

API capture: an API is useful when you need to repeat captures or integrate them into a workflow, but a protected URL needs authentication configured for that API. A local browser session is not automatically available to a remote request. Treat credentials as secrets, use only accounts and pages you are authorized to capture, and consult the API documentation for the supported authentication and output options. ScreenshotNeo’s published plan prices and no-charge verdict cases are listed above; verify the plan that fits your expected volume on its site.

FAQ

Does the screenshot tool need my website password?

The browser workflow uses the session you signed into normally. It does not ask the screenshot tool for your password. An API workflow may need supported authentication credentials configured for the request; see that API’s documentation.

Will a full-page screenshot include every item in a scrollable panel?

Not necessarily. Full-page capture covers the document, while an independently scrolling panel may have its own content boundary. Inspect the result and use an approved export or authorized element-level method if needed.

Can I use a screenshot of a work or customer account?

Only if your access and the intended capture and sharing are authorized. Follow your organization’s data-handling rules, and redact information that recipients do not need.

Can I automate a capture from my signed-in browser session?

The browser steps above are manual. For API automation, the request needs its own supported authentication configuration; it does not reuse the cookies in your open browser automatically.