How to take an Awesome Screenshot of a page behind a login

To take an Awesome Screenshot of a page behind a login, sign in to the site in your browser, open the protected page, start the Awesome Screenshot extension, and choose its full-page capture option. In Chrome and other browsers that support Chrome extensions, use Capture → Full Page. Safari and Firefox use differently named controls. The page must be accessible in the active browser session, and the extension’s help does not guarantee that every authenticated site or embedded viewer will capture correctly.

Capture the logged-in page

Open the site in the browser and sign in normally. Complete any multi-factor prompt or other access check.
Navigate to the page you want to capture. Wait for its content to finish loading, including any sections that appear after scrolling.
Start the Awesome Screenshot extension from the browser toolbar.
Choose the full-page option for your browser, as described below.
Review the resulting capture and save or export it using the options available in the extension.

Signing in first is the practical way to make the protected page available in the browser tab. The extension captures the page shown in that authenticated session; it does not provide a way to bypass a site’s login or access controls.

Chrome and browsers that support Chrome extensions

Open the extension, select Capture, then select Full Page. The Awesome Screenshot Help Center documents this sequence for Chrome-extension-compatible browsers.

Safari

Start the extension and select Capture Full Page, following the Safari control names in the vendor’s instructions.

Firefox

Start the extension and select Capture Entire Page, following the Firefox instructions.

Choose the right capture scope

What you need	Control to try	When it helps
The complete scrolling page	Full Page or the browser-specific equivalent	Capturing a long page as one image
Only the portion currently on screen	Visible Part	Full-page capture is unavailable or only the current viewport matters
The browser window or app view	Entire Screen & App Window	Extension scripts cannot run on the page, or the content is outside the normal page capture path

If you capture the visible part or the window, crop the result afterward if you need a smaller area. These fallbacks may not produce the same single, continuous page image as a full-page capture.

When full-page capture is unavailable

Awesome Screenshot says Full Page and Selected Area can be unavailable when browser restrictions prevent extension scripts from running on a page. Its examples include browser settings pages, extension-store pages, and chrome:// URLs.

Check whether the current page is a browser-internal page or another restricted page.
If the full-page control is missing, try Visible Part or Entire Screen & App Window.
Crop the resulting image if you need to remove surrounding browser or desktop content.
If the target is a normal website, return to the page and confirm you are still signed in and the page has loaded. Then reopen the extension and check the available capture controls.

The vendor’s instructions describe the available workflows and restrictions, but do not specifically guarantee capture support for every single-page application, embedded frame, private document viewer, or login-protected site. If a particular page fails, use the fallback capture mode or the site’s own export option where available.

Permission and privacy context

Awesome Screenshot says its “On all sites” permission lets the extension capture screenshots and recordings across websites you choose to use it on. The vendor also says the extension does not run in the background or secretly record. These are the vendor’s descriptions of its permission and behavior; review the extension’s current permission prompt and privacy information if you need to assess whether it fits your organization’s policies.

Or skip the browser setup

If you need a repeatable capture in code, [ScreenshotNeo](https://screenshotneo.com) is a website screenshot API and MCP server for developers. One GET request takes a URL and returns an image or PDF. For authenticated pages, the request needs valid access to that page; an API call does not bypass a login. See the [ScreenshotNeo API documentation](https://screenshotneo.com/docs/) for authentication and 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,
)
r.raise_for_status()
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 Bun.write('shot.webp', res);

Replace the example URL with a page your request can access, and keep your API key private. ScreenshotNeo can accept cookie and header options for sites where you are authorized to capture content; consult the docs for the supported parameter names and formats. Cookie banners, popups, 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 per month with no card, and paid plans start at $5 for 3,000.

Troubleshooting

Problem	Likely cause	What to try
The page shows a sign-in screen in the capture	The browser session expired, or the target page redirected to login	Sign in again, reopen the target page, and confirm it displays protected content before capturing.
Full Page or Selected Area is missing	Browser restrictions prevent extension scripts from running on that page	Use Visible Part or Entire Screen & App Window, then crop if needed.
Some page content is missing	Content may load only after scrolling, or the page may use embedded or dynamic content	Scroll through the page first to trigger lazy-loaded sections, wait for them to appear, and capture again. If an embedded area still does not appear, use a window capture or the site’s export feature.
The result is only the visible viewport	A visible-area or screen capture mode was selected instead of full-page capture	Use the browser-specific full-page control when it is available.
Capture does not work on a browser settings or store page	The browser restricts extensions on internal or protected pages	Use a visible-part or screen/window capture. Extension-based full-page capture may not be available there.

Reliability, performance, and cost considerations

Reliability: Confirm the page is signed in and fully rendered before capture. Authentication may expire, and pages with dynamic or embedded content may behave differently from ordinary documents.
Performance: Long pages take more time to render and capture. Let lazy-loaded sections appear before starting, and use a visible-part capture if you only need the current view.
Privacy: A screenshot can contain account details or other private information. Store and share it according to the site’s and your organization’s rules. Do not expose session cookies or API keys.
Cost: The research sources do not state Awesome Screenshot pricing for this workflow. ScreenshotNeo offers 1,000 shots per month free with no card; paid plans start at $5 for 3,000, with all features on every plan.

FAQ

Can I capture a page that requires a password?

Yes, when you are signed in and the page is accessible in the active browser session. The extension workflow captures the page available to that session; it does not bypass authentication.

Does the extension capture every logged-in site?

The vendor documents the capture steps but does not promise that every protected site, app, frame, or private viewer will work.

Why does the button name differ in my browser?

The help instructions use Capture → Full Page for Chrome-extension-compatible browsers, Capture Full Page for Safari, and Capture Entire Page for Firefox.

What if the site blocks screenshots?

Follow the site’s access rules. Browser-level restrictions can prevent extension scripts from running; try the documented visible-part or screen/window fallback when appropriate.

Sources

Awesome Screenshot Help Center: full-page capture instructions, published December 24, 2025.
Awesome Screenshot Help Center: why full-page and selected-area capture may be unavailable, published August 27, 2024.
Awesome Screenshot Help Center: “On all sites” permission explanation, published November 20, 2025.