Cookie Panda

Copy your sign-in (cookies and site storage) to another Chrome browser through an encrypted file or a private link.

Move your signed-in state from one Chrome to another. Cookie Panda copies the cookies and site storage (localStorage, sessionStorage, IndexedDB) of the sites you choose into one encrypted file. Import that file into another Chrome profile or another computer, open the sites, and you are signed in just like on the first browser. HOW IT WORKS 1. On the first browser, click the Cookie Panda icon to open the side panel. 2. Choose the data to copy, and either the current site or all open sites, then press Export. 3. Untick any site you want to leave out, set a password, and save the .cpanda file (or copy it to the clipboard). 4. Move the file yourself: USB stick, your own cloud drive, or a message to yourself. 5. On the other browser, open the side panel, import the file, enter the password, check the preview, and press "Write to this browser". 6. Reload the sites. A report shows what was written, and what needs your attention. MORE • Per-site detail: see how many cookies and how much storage each site carries, and which cookies expire soon. • Compare before writing: the preview shows, per site, which cookies are new, will be replaced, or are already identical on this browser. • Paste cookies from other tools: Import also reads cookies as JSON (Cookie-Editor, EditThisCookie and similar), a cookies.txt file, or a name=value line from DevTools (written to the site of the tab you are on). • Undo: changed your mind after an import? One click puts back this browser's previous cookies and localStorage for those sites (while the panel stays open). • Site templates: save a set of sites under a name and pick it again in one click. • Quick export: press Alt+Shift+E on any site, or right-click and pick "Export this site" or "Export all sites", to open the panel and export straight away; "Import a .cpanda file" in the same menu opens the Import step (change the key at chrome://extensions/shortcuts). • Profiles: keep several sign-in states in one Chrome profile, in a vault locked with your password, and switch between them. Switching saves the current state, closes the web tabs, clears browsing data (your Google sign-in cookies are kept unless you choose to include it in profiles), then restores the other profile and reopens its tabs. • Organise profiles: give each one a colour, put it in a group and filter by group, sort by name or by last saved, duplicate one, and see which sites and how many cookies it holds before you switch. • Switch fast: Alt+Shift+P opens the Profiles tab, and the right-click menu has a "Switch to profile" list of your profiles (it asks you to unlock the vault first if it is locked). • Profile files: save a profile to an encrypted .cpanda file, or import a .cpanda file as a new profile. • Sync by link (optional): sign in with Google, press "Upload & get link", and paste the link into Import on the other browser, signed in with the same Google account — or tick "Anyone with the link can open it" to share it with someone who never signs in (switch it back any time under "My files"; the link stays the same). The file is encrypted with a new key that exists only in the link (and, for accounts you share with, locked so that only their browser can open it); the server never sees it. • Share with other accounts: list up to 10 Gmail or Google Workspace addresses under "Share with". The file then shows under "Shared with me" for them. Once their browser has opened "Shared with me" and yours has opened "My files" again, "Open" takes it straight to the Import preview — no link to send. • Its own page: "My files" and "Shared with me" are a table on the extension's "Sync by link" page (the "My files ↗" button in the panel, Alt+Shift+L, or the right-click menu): change who can open each file, put files in groups (tick many and move them at once, rename a group) and browse them group by group, copy its link, delete it, or "Delete cloud account" to remove everything. • Proxies with your profiles: save HTTP or HTTPS proxies (with their login, if any) and SOCKS4 or SOCKS5 proxies in the same locked vault, turn one on or off for this Chrome profile, and attach one to a profile so that it travels with that profile's file or link — many sites tie a sign-in to the IP address. Paste many proxies at once, filter the list, and press "Check" to see a proxy's exit IP, country, city, network (ASN) and time zone before you use it. • Feedback: send a bug report, an idea or a feature request with up to 3 screenshots from the "Sync by link" page (signed in with Google). PRIVATE BY DESIGN • No analytics, no tracking. Your data only travels in the file you move yourself, or — if you choose Sync by link — as a file encrypted end to end, which the server cannot read (it sees only the file name, the addresses you share with, the group names you choose and whether the file carries a proxy). Feedback you choose to send is the one exception: it is meant to be read, so it is sent over HTTPS but not end-to-end encrypted. • Files are encrypted by default with AES-256-GCM, using a key derived from your password (PBKDF2-SHA256, 600,000 iterations). Your password is never stored. • Nothing happens until you press Export, Import or a profile button (or their shortcut or menu item), and you decide which sites go into the file and which sites from a file are written. • A proxy's password stays encrypted in the vault. It goes into a file, the clipboard or a link only when you attach the proxy — encrypted like the rest, except in a file or clipboard text you save without a password. "Check" sends one empty request through the proxy to Cookie Panda's own server, which answers with what it sees about the proxy's address and keeps nothing. • The code is not obfuscated: what the extension does can be read from its package. GOOD TO KNOW • Cookies and site storage are sign-in information: anyone with an unencrypted file can use your accounts. Keep the file private and delete it when you are done. • While importing, Cookie Panda opens the imported sites in background tabs (site storage can only be written from the site's own page) and closes them afterwards. A tab is kept open when the site uses sessionStorage. • For tabs Chrome has frozen, or pages that block extension scripts, it falls back to Chrome's debugger API, so Chrome may show a "being debugged" bar for a few seconds. • Some sites tie a session to the device or IP address and may still ask you to sign in again. Interface: English, Vietnamese, Simplified Chinese, Spanish, Brazilian Portuguese, Russian, Japanese, German, French, Korean, Indonesian, Turkish and Arabic.