To screenshot a page behind a login with ScreenshotAPI.net, give its capture browser an authentication method the site accepts. For a site that uses browser sessions, the documented route is to sign in normally, provide the active session cookies in the capture request, or save them as a Cookie Template and reference its template_id. If the site authenticates requests with a token, custom headers may work instead. Neither method is universal: the site’s login design determines what will work.
How to take a screenshot of an authenticated page
ScreenshotAPI.net’s help page asks, “How to take a Screenshot in an Authenticated Page?” Its guidance is practical: first identify how the target site authenticates you. The service’s guide focuses on reusing an already-authenticated browser session through cookies; it does not establish that sending a username and password to the screenshot API will log you in.
As an Amazon Associate I earn from qualifying purchases.
- Sign in to the target website in a browser account you are authorized to use.
- Determine whether the site relies on session cookies or accepts an authentication header.
- Provide the appropriate current cookie or header to ScreenshotAPI.net using its documented request parameters.
- Check the returned image. If it shows a login screen, verify the authentication state before changing render timing.
Authentication flows vary by site, so a valid-looking cookie or token is not proof that the capture browser will be accepted. ScreenshotAPI.net describes these mechanisms in its help page.
Choose cookies or custom headers based on the site’s login design
| Method | Use it when | Setup and maintenance |
|---|---|---|
| Session cookies | The site maintains a signed-in browser session with cookies. | Export the active cookies and pass them with the request, or save them in a Cookie Template and use template_id. Sessions can expire, so refresh them when the site no longer accepts them. |
| Custom headers | The target accepts an authentication token or other credential in an HTTP request header. | Set the documented custom header, such as Authorization: Bearer TOKEN, replacing the example token with a valid credential. This works only for a site whose authentication flow accepts that header. |
The vendor documents cookies and reusable templates on its Screenshot API Features page and headers in its Browser Environment Emulation documentation. Those pages describe available mechanisms, not a universal ranking for security or reliability.
#1 Best Overall
Pass a browser session with cookies
Export and send current cookies
Sign in to the site in your own browser, then export the active cookies for the target domain. ScreenshotAPI.net’s guide notes that cookie structure matters: an export from a browser extension may already be suitable, while data copied manually may need conversion. Use the service’s current parameter documentation for the exact request syntax and accepted cookie format rather than assuming every browser export can be pasted unchanged.
Include all cookies the site requires for the session, and ensure they belong to the correct domain and have not expired. Treat exported session cookies like passwords: anyone who can use them may be able to access the associated account. Do not capture accounts or data without authorization, and avoid exposing cookie values in shared code, logs, or source control.
Save a Cookie Template for repeat captures
If the same authenticated session is used regularly, ScreenshotAPI.net’s features page says you can save a named Cookie Template in the dashboard and reference it with template_id. This avoids rebuilding the cookie payload for each request. A template still depends on valid session cookies; update it when the session expires or the site changes its session state.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteUse custom headers when the site accepts token authentication
Some sites or internal applications accept credentials in request headers rather than relying on a browser login session. ScreenshotAPI.net’s emulation documentation shows custom request headers, including an Authorization: Bearer TOKEN example. Add the header only when the target application’s documented integration supports that authentication scheme. It is not a way to bypass an ordinary login form, multi-factor authentication, or an interactive challenge.
Keep tokens private and use the narrowest access the target application offers. If the site expects a cookie-backed browser session, a header alone may leave the capture unauthenticated.
Wait for the authenticated page to finish rendering
A successful login state and a finished screenshot are separate issues. ScreenshotAPI.net describes its renderer as real Chromium and lists timing controls for pages that render content after the initial response:
Rank #4
delayto allow a known amount of additional time.wait_for_selectorto wait until a relevant page element appears.wait_for_event=networkidleto wait for network activity to settle.
Prefer a selector that indicates the content you need is present when one is available. A longer delay is simple, but can waste time and still fail when rendering duration varies. Timing controls do not authenticate a request: if the result is the login page or a blank shell, first confirm the cookies or header were accepted. The vendor describes these options on its homepage.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Troubleshoot login-protected captures
| What you see | Likely check | What to do |
|---|---|---|
| The screenshot shows the login page. | The session cookies may be expired, for the wrong domain, or incomplete; the site may not use cookie-based sessions. | Sign in again, export the current cookies for the target domain, include the required session cookies, and confirm the site’s authentication method. If it requires an accepted token header, use that documented integration instead. |
| The page is blank or only partly rendered. | Authentication may have succeeded, but client-side or asynchronous content may not be ready. | Check for a visible authenticated-page marker, then try an appropriate delay, selector wait, or network-idle condition. |
| The site requires a challenge, changing token, or another interactive step. | The available vendor documentation does not establish universal support for these site-specific flows. | Consult ScreenshotAPI.net and the target site’s permitted integration options. Do not assume that a cookie or header can satisfy a challenge. |
| The page differs by region. | Regional routing is separate from having valid credentials. | Review the vendor’s emulation documentation for proxy and request-emulation options; possessing a valid session alone does not determine the page’s region. |
Or skip the browser setup
ScreenshotNeo is an alternative if you would rather make a screenshot request than configure a browser capture workflow. Its one-call API can capture a URL as an image or PDF; for a login-protected target, supply authentication details only through a method that target site accepts.
See the ScreenshotNeo API documentation for supported parameters. Example cURL request:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo removes cookie/consent banners, newsletter popups, and chat widgets before capture; bot checks, blank pages, and failed loads are not billed. Its 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. Sign up for ScreenshotNeo and start with 1,000 free screenshots a month, no card required.
Frequently Asked Questions
Does ScreenshotAPI.net log in if I provide a username and password?
The cited guide describes reusing session cookies, not a general username-and-password login feature. Whether a capture can authenticate depends on the target site’s login design.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsCan I use the same cookies for every protected website?
No. Cookies are associated with a site and session, and the required authentication mechanism varies by target.
Will waiting longer fix a screenshot that shows the login page?
Not by itself. Verify that the site accepted the authentication state first; timing controls help when authenticated content is still rendering.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
