Ultimate Web ScraperCookies & Sessions: Scrape Behind Logins in the Cloud
Clone your current browser session's cookies and localStorage into a cloud browser so logged-in extractions keep working when they run without you.
Some pages only show their data to logged-in users. Locally that's a non-issue — the extension runs in your own browser, with your session, so it sees exactly what you see. A cloud browser starts logged out. Cookies & Storage cloning fixes that.
How it works
When creating a task in the Run in Cloud wizard, expand the Cookies & Storage group. Enabling it clones your current browser session's cookies and localStorage into the cloud browser, so the cloud run visits the target site as your logged-in session.
That makes logged-in extractions work in the cloud: member directories, dashboards, gated listings — anything your account can see, the cloud browser can now extract, including on a schedule while you're away.
🔒 Only when you use it
Session cloning only reads the current site's cookies and storage, and only when you enable it for a task — nothing is accessed at install time or in the background. If you never clone a session, nothing is ever read.
Local vs. cloud with logins
| Extension (local) | Cloud with session cloning | |
|---|---|---|
| How it authenticates | Uses your live browser session natively | Copies your session's cookies and localStorage at task creation |
| Setup | None — just be logged in | Enable Cookies & Storage in the wizard |
| Stays valid | As long as you're logged in | Until the cloned session expires on the site's side |
If a site logs sessions out quickly, a long-running schedule may eventually hit expired cookies — recreate the task while logged in to refresh the cloned session.
⚠️ Use your own accounts, respect site terms
Session cloning is meant for extracting data that your own account legitimately has access to. Check the target site's terms of service before scraping logged-in areas, never clone sessions for accounts that aren't yours, and be conservative with scheduling frequency on authenticated sites.
When you don't need this
Leave Cookies & Storage off (the default) for public pages — most extractions don't need a session, and the proxy and unblocking settings cover ordinary anti-bot friction.