How to Screenshot a Page You Are Logged Into

Quick answer

The reason most capture tools fail on a signed-in page is simple: they load the URL in their own browser, and that browser is not you. It has no session cookie, so the server returns a login screen. What you capture is the login screen.

There are only two reliable ways around it. Either capture from the browser that already holds the session, or use an app whose built-in browser is the thing you signed into. Anything that takes a URL and fetches it elsewhere will hit the same wall.

This matters more than it sounds, because the pages worth capturing are so often the private ones: an order history, a dashboard, a statement, a booking confirmation.

Step-by-step

Understand what is actually breaking

When you sign in, the site stores a session cookie in that specific browser. The cookie is what identifies you on the next request. A different browser, an extension running in its own context, or a server-side screenshot service has no copy of it.

So a URL alone is not enough to reach a private page. This is a security property, not a bug, and it is why "paste a link and get a screenshot" services can only ever capture public pages.

Capture in the browser that has the session

The most direct approach is to capture where you already are.

On iPhone, Safari's built-in full-page screenshot captures the page as Safari sees it, session included. Take a screenshot, tap the preview, choose Full Page, and save the PDF. See how to take a full-page screenshot on iPhone for the full walkthrough and its limits.

On Android, the equivalent depends on the manufacturer. Many devices offer a scroll or long-screenshot option in the screenshot preview, which captures whatever the browser is currently showing, signed in or not.

Or sign in inside the capture app

The other approach is to use an app that browses as well as captures. You sign in once inside that app's browser, the session persists there, and every subsequent capture of that site sees the signed-in page.

This is the more practical option if you capture private pages regularly, because you sign in once rather than working around the problem each time.

Check what you actually captured

Whichever route you take, look at the result before you rely on it. The failure mode is quiet: you get a perfectly clean screenshot of a login form, or of the page in its signed-out state, which can look surprisingly close to the real thing on sites that show a public preview.

Common problems and fixes

I captured the login page instead of my account

The capture ran in a context without your session. Either capture from the browser you are signed into, or sign in inside the capture tool first.

It worked once and then stopped

Sessions expire. Banks and other sensitive sites often time out after minutes of inactivity, and many sites end the session when the browser is closed. Sign in again and capture promptly.

Parts of the page are blank or still loading

Dashboards frequently load their data after the initial page render. If the capture happens too early you get empty cards and spinners. Let the page finish, scroll through it once so everything has loaded, then capture.

The page shows a "not secure" or blocked warning

Some sites actively refuse to render inside embedded browsers, particularly banking sites using framing protections. If a page refuses to load properly in a capture app's browser, fall back to capturing in the system browser instead.

My capture is cut off at the fold

That is a different problem: the tool captured the visible screen rather than the whole page. Full-page capture is the fix.

Doing this with Foldless

Foldless takes the second approach. It has its own built-in browser, so you sign in there exactly as you would anywhere else, and the session stays live. Dashboards, order histories and account pages capture exactly as you see them, because it is genuinely your session doing the rendering.

Nothing about that login leaves the phone. Foldless has no account system and no backend, so there is no server to send a session to and nothing stored anywhere but the device. Your captures land in a local library you can organize into projects.

Because the page is captured at full height in a single pass, a long statement or a tall dashboard comes out as one image or one PDF rather than a stack of screenshots you have to piece together afterwards.

Foldless is $3.99, once, on the App Store and Google Play.

Frequently Asked Questions

Why does my screenshot tool show a login page instead of my account?

Because it loaded the URL in a browser that does not hold your session cookie. The server has no way to tell it is you, so it returns the signed-out version. Only a browser you have actually signed into can render the private page.

Is it safe to sign in inside a capture app?

It depends on the app. The question worth asking is where the session and the captures go. Foldless keeps both on the device: there is no account, no backend, and nothing uploaded, so the session never leaves the phone. An app that syncs to a server is making a different trade, and is worth checking before you sign in to anything sensitive.

Can I capture a page behind two-factor authentication?

Yes. Two-factor affects signing in, not the session afterwards. Once you are through the login inside the browser you are capturing from, the page renders normally.

Why do some banking sites refuse to load in a capture app?

Some sites use framing and embedding protections that block rendering outside their expected context. When that happens, capture in the system browser instead, using its own full-page screenshot feature.

Do captures of private pages get uploaded anywhere?

With Foldless, no. There is no server behind it, so captures stay in the local library on your device. Other tools vary, and cloud-based screenshot services necessarily send the page somewhere. It is worth checking before capturing anything sensitive.

Conclusion

Signed-in pages break capture tools for one reason: the session lives in a specific browser, and most tools are not that browser. Once you see that, the fix is obvious. Capture where you are already signed in, or sign in where you capture. The second is less friction if private pages are a regular part of what you save, and it is the reason a capture app with its own browser handles dashboards and statements that a URL-based tool simply cannot reach.