Session Transfer – Copy Login to Another Chrome Profile

Move your login (cookies + storage) to another Chrome profile or computer, encrypted. Or export a plain Playwright storageState.

Session Transfer moves an authenticated website session from one Chrome browser, profile, or computer to another in a couple of clicks — no re-login, no MFA loop. HOW IT WORKS On the source browser, open the site, click the extension and press "Transfer Session". The extension captures cookies (including HttpOnly), localStorage, sessionStorage, IndexedDB and Cache Storage, into one package that you copy or download (optionally encrypted with a transfer code). On the destination browser, press "Receive Session", paste or load the package (and enter the transfer code if the package asks for one). State is restored, the page reloads, and a verification report confirms the result. SECURITY & PRIVACY BY DESIGN • 100% local — no servers, no accounts, no analytics, no tracking. • Not encrypted by default, so treat the copied text or file like a password. Turn on "Encrypt with a transfer code" to encrypt it with AES-256-GCM, using a key derived from a code you send on another channel (PBKDF2-SHA256, 600,000 iterations). • The extension refuses packages older than 5 minutes. • Strict origin isolation — a package can only ever be restored into its own website origin. • Existing destination sessions are never silently overwritten: choose Replace, Merge or Cancel. • Honest about limits: WebAuthn/passkeys, hardware credentials and TLS-bound state cannot be transferred by any extension, and we say so in-product instead of faking success. FOR DEVELOPERS AND QA • "Export for Playwright" saves the current site's cookies and localStorage as a Playwright storageState file, so automated tests can start already logged in. • Signing in through another site? Add its host name (up to 5) under More options and its cookies travel too. IDEAL FOR • Developers moving authenticated sessions between dev/staging/prod profiles. • Switching computers or browsers without logging in again. • QA teams reproducing authenticated states quickly. Full capability table and threat model are published in the GitHub repository.