Import and export cookies
Work with cookies and Local Storage for sites you manage. Import from a file, text, or URL, and export to a file or clipboard. You can protect exported data with a password.
Back up cookies and Local Storage, keep session profiles for the sites you manage, and set a refresh schedule for subscriptions.
Work with cookies and Local Storage for sites you manage. Import from a file, text, or URL, and export to a file or clipboard. You can protect exported data with a password.
Save separate session profiles for a site you use in more than one role, such as a test environment with different authorized accounts.
Use a subscription URL you manage and choose how often SetCookies checks it for updates.
Set up a proxy for the domains where you need it and keep the rest of your browsing separate from that rule.
When you test a staging site in more than one role, save a profile for each test account you manage. Name the profiles so you can tell the environment and role apart. After switching, confirm the active account in the page before running a test.
If a bug depends on a saved preference or a particular session state, keep a copy of the relevant test data. Work out whether the behavior comes from cookies, Local Storage, or both. Save just the data needed for the test alongside your reproduction notes.
If your team maintains a subscription source, use it to refresh a shared set of test values on authorized browsers. Check the refresh result before running your test. For a one-off fixture, importing a file makes it easier to see which snapshot you used.
Use domain rules when a particular test environment needs a proxy. Check which domain the rule covers before browsing. If the test site fails to load, confirm that the proxy is reachable and that the current domain matches your configuration.
SetCookies stores its settings and managed data locally. When you configure a subscription, proxy, or webhook, the feature can send requests or selected data to that service. Keep exports containing live account sessions or personal information in a secure place. If you need to share material to reproduce a bug, use a test account and sample data.
SetCookies runs as a Chrome extension. Install it from the Chrome Web Store on desktop Chrome, then open it from the Extensions menu while you’re on the site you want to manage.
A browser can send matching cookies with requests to a site. Local Storage holds data that a site’s scripts can read for that origin, such as a preference. If a test depends on saved state, first check which type the site uses.
You can import from a file, text, or URL, and export to a file, the clipboard, or a webhook you configure. Review the current site and the selection before exporting. A webhook receives the data you explicitly send to it.
Confirm that the extension has selected the same site as the tab, then reload the page. Check that the data belongs to the intended environment and is still current. A site can reject an expired session even if its cookie appears in the browser.
The site controls how long its sessions remain valid and may ask you to verify your identity again. If that happens, sign in with your own account through the site’s normal process.
Use a single import when you need one snapshot. A subscription checks the source on a schedule, which helps when your team maintains test values that change periodically.
The extension supports English and Simplified Chinese. This website also has both languages, and you can switch using the link in the header.
Use the Contact link in the footer or the support page on the Chrome Web Store. Include your Chrome version, the action you took, and what you expected. Use sample data when sharing an example.