Noureddine RAMDI / Get cookies.txt LOCALLY: a privacy-first browser extension for local cookie export

Created Sat, 23 May 2026 20:41:14 +0000 Modified Sat, 23 May 2026 20:41:27 +0000
1020 Words
github-stars javascript browser-extension privacy cookies manifest-v3 cli-integration

kairi003/Get-cookies.txt-LOCALLY

Every time you try to bridge browser sessions with CLI tools like wget or curl, exporting cookies safely without risking your privacy is a hassle. Get cookies.txt LOCALLY is a browser extension that solves this exact problem by providing a fully local, transparent way to export your cookies in standard formats without ever sending data outside your machine.

What Get cookies.txt LOCALLY does and how it works

Get cookies.txt LOCALLY is a privacy-focused browser extension written in JavaScript that exports your browser cookies in either the Netscape cookies.txt format or JSON. It operates strictly locally — no data is transmitted externally at any point. This makes it a practical and trustworthy tool for developers and privacy-conscious users who want to integrate browser cookies into CLI workflows or scripts such as wget, curl, or Python’s MozillaCookieJar.

Under the hood, the extension uses the latest Manifest V3 standard for browser extensions, which enhances security and performance by requiring explicit permissions and service worker architecture. The extension requests only the minimal necessary permissions: activeTab, cookies, downloads, notifications, and host permissions explicitly declared and justified in the unobfuscated source code. This transparency allows users to audit exactly what the extension does.

The main workflow relies on the browser’s cookies API to read cookies for the active tab’s domain and then formats them into a compatible file. Instead of hacky methods like creating invisible links for downloads, it uses the downloads API to save the cookies file directly to disk, improving reliability and user experience.

Available on both the Chrome Web Store and Firefox Addons, the extension can also be loaded unpacked from source, which is useful for developers or privacy enthusiasts who want to inspect or modify the code themselves.

Technical strengths and design tradeoffs

The standout feature of this extension is its radical privacy-first architecture. Unlike many cookie exporters that rely on external servers or obfuscated code, Get cookies.txt LOCALLY guarantees your cookie data never leaves your machine. The source code is fully open, unobfuscated, and auditable, which is a rare quality in browser extension ecosystems.

The choice to use Manifest V3 is significant because it reflects a commitment to modern, secure extension practices. Manifest V3 enforces stricter permission models and service worker-based background scripts, reducing attack surface and improving performance.

The extension’s minimal permission set is a clear design tradeoff. While it limits functionality to only what is necessary for cookie export, it also reduces risk and builds user trust. Each permission is explicitly declared and justified, which is important for privacy-sensitive users.

The use of the downloads API rather than traditional link-click hacks for file saving is a subtle but important technical detail. It avoids issues with popup blockers or inconsistent browser behavior, providing a smoother and more predictable user experience.

One limitation to note is that the Firefox version may have some feature differences or limitations compared to Chrome, and review delays on WebStores can mean the latest version isn’t always immediately available. Also, users need to manually enable site access permissions in some cases, which adds a small layer of user configuration.

Overall, the codebase is surprisingly clean and straightforward for a browser extension handling sensitive data, which aligns well with the project’s core value proposition: trust through radical transparency.

Quick start

Installation

From WebStore

Chrome Web Store

Firefox Addons

  • Note: Depending on the status of the review, it may not be the latest version or may not be published yet.
  • Some features may be limited in the Firefox version.
  • You may need to allow access to site resources from the extension manager.

From source code (Google Chrome)

  1. Download and unzip this repository.
  2. Open Extensions (chrome://extensions/).
  3. Enable “Developer mode”.
  4. Click on “Load Unpacked” and open the directory Get-cookies.txt-LOCALLY/src.

From source code (Firefox)

  • For Firefox, you need to patch the manifest file by merging src/manifest.json and src/manifest-firefox.json.
  • Use the firefox branch where the manifest is merged on master.
  • Alternatively, merge manually or with npm run build:firefox or jq.

Example extension installation directory (Google Chrome)

  • Windows:
%LOCALAPPDATA%\Google\Chrome\User Data\Default\Extensions\cclelndahbckbenkjhflpdbgdldlbecc
  • Mac:
~/Library/Application Support/Google/Chrome/Default/Extensions/cclelndahbckbenkjhflpdbgdldlbecc
  • Linux:
~/.config/google-chrome/Default/Extensions/cclelndahbckbenkjhflpdbgdldlbecc

verdict

Get cookies.txt LOCALLY is a solid choice for developers who want a trustworthy, privacy-first way to export browser cookies for automation, scraping, or scripting workflows. Its local-only architecture and minimal, transparent permissions make it stand apart from other cookie exporters that may obfuscate code or rely on external servers.

While it may not have all the bells and whistles of bigger extensions, its straightforward, auditable design is a strong advantage if privacy and trust are top priorities. The tradeoff is a bit more manual setup for Firefox users and occasional delays in WebStore updates.

If you need to bridge your browser sessions securely with CLI tools like wget, curl, or Python scripts without risking cookie leakage, this extension deserves a look. Its clean codebase also makes it a good starting point if you want to fork or customize your own cookie export tool.

In sum, Get cookies.txt LOCALLY solves a real problem with a clear focus on privacy, security, and developer trust — worth understanding even if you don’t adopt it as-is.

→ GitHub Repo: kairi003/Get-cookies.txt-LOCALLY ⭐ 993 · JavaScript