Back up any site's cookies to your own private GitHub Gist and restore them in one click. Per-domain, encrypted.
Users
6
+2 in 30 days
Rating
0.0 / 5
unchanged in 30 days
Ratings
0
0 in 30 days
Store rank
#242K
#202K among extensions
Version
1.12
updated 25 Sep 2026
Users
monthly, 9 months
Latest, 16 Oct 2026:6 usersMove the mouse over the chart for any month
Ratings count
monthly, 9 months
Latest, 16 Oct 2026:0 ratingsMove the mouse over the chart for any month
The Chrome Web Store rounds user counts down to the leading digit, so the user line moves in steps. The ratings count is exact and is the better signal of real adoption.
About CookieBridge - Private Cookie Sync
CookieBridge - Private Cookie Sync backs up the cookies of any website to a private GitHub Gist and restores them whenever you need them.
Built for people who work across several browsers, profiles or machines, or who need to keep a site session alive after clearing cookies.
WHAT IT DOES
* Push - saves the cookies of the current domain to a Gist file you choose, optionally encrypted with AES.
* Pull - restores those cookies into the browser, with an option to clear stale cookies first.
* Per-domain settings - every domain keeps its own file name, cookie selection and automation options.
* Cookie picker - the popup lists every cookie for the current domain in a sortable Name / Path table, so you can sync only the cookies you care about.
* Reload after pull - refresh the current page, or jump to a specific path on the same site.
* DOM trigger - push automatically once a chosen element appears on the page. CSS selectors and XPath are both supported, including elements that only render after a redirect or a client-side navigation.
HOW TO USE
1. Create a GitHub personal access token with the "gist" scope.
2. Create a Gist and copy its ID.
3. Open the extension, paste the token and the Gist ID, set a file name and the target domain, then click Save.
4. Click Push to upload the current cookies, or Pull to restore them.
PRIVACY
Everything stays under your control. Cookies are written to your own GitHub Gist, never to a server operated by the developer. The extension contains no analytics and sends no data anywhere else. If you set an encryption password, cookie data is encrypted before it leaves the browser.
Cookies are equivalent to login credentials. Keep your Gist secret and set an encryption password.