Ultimate Web ScraperHow to Scrape Pages Behind a Login
Extract members-only pages using your own browser session locally, or clone cookies into a cloud browser for scheduled logged-in extractions.
Dashboards, member directories, order histories, gated catalogues — if a page needs a login, you can still extract it. The rule of thumb: if you can see it in your browser, you can extract it.
Log in as usual
Sign in to the site in Chrome, exactly as you normally would. The extension runs inside your browser and uses your existing session — there's no separate login to configure, no credentials to hand over.
Extract like any other page
Use whichever tool fits the job — List Extractor for gated lists and tables, Page Extractor for batches of member-only detail pages. Because extraction happens locally in your logged-in browser, gated pages render just as you see them. Results stay in your local Data Table.
Logged-in extractions in the cloud
Cloud runs happen in a cloud browser that starts with no session — so a login wall would stop it. The fix is session cloning:
Build and test the extraction locally
Run it once in your logged-in browser to confirm it works.
Enable Cookies and Storage cloning
In the Run in Cloud wizard, open the Cookies & Storage section and enable cloning. Your current session's cookies and localStorage for the target site are replicated into the cloud browser, so it arrives already logged in as you.
Run or schedule
Submit the task. The cloud browser loads the pages with your session, on a schedule if you set one. See Cookies and sessions for details, including what happens when sessions expire.
⚠️ Use it responsibly
Session-based extraction is for your own accounts and data you're entitled to access. Respect each site's terms of service and rate limits, and don't extract other people's private data. You are responsible for how you use your sessions.
What's not possible
LinkedIn is blocked regardless of login state — every tool refuses LinkedIn URLs, locally and in the cloud, and being signed in doesn't change that.
Beyond that, the usual limits apply: content inside cross-origin iframes or shadow DOM isn't reachable, and pages that require interaction to reveal content (beyond scrolling/pagination the tools handle) won't render it for extraction.