Chrome Web Store
Edge Web Store
- Auto Query — Automatically collects cookies when the popup opens; manual re-query available via the Query button
- Grouped by origin — Cookies are grouped by frame origin, including nested iframes
- Cookie detail — Click a cookie name or the ⓘ icon to expand value, domain, path, sameSite, secure, httpOnly, session, and expires
- Expiry warning — ⌛ badge on cookies expiring within 24 hours
- Search / Filter — Real-time filter by cookie name or domain
- Selection — Global select-all, per-group select-all (with indeterminate state), and individual selection
- Copy — Copy checked cookies to clipboard in TXT, JSON, or CSV format
- Save to file — Download checked cookies as
1cookies_yyyy-mm-dd_hh_mm_ss.{ext}in TXT, JSON, or CSV format - i18n — Supports 8 languages: Korean, English, Simplified Chinese, Traditional Chinese, Japanese, Russian, Indonesian, German
- Open the extension popup on any site — cookies load automatically
- Click a group header to expand it and see individual cookies
- Click a cookie name or ⓘ to inspect its full details
- Check the cookies you want, then use Copy or Save File to export
| Format | Content |
|---|---|
| TXT | Block format — [name], [value], [domain], … separated by --- |
| JSON | Full cookie fields as a JSON array grouped by origin |
| CSV | Column-based, Excel-compatible |
| Permission | Purpose |
|---|---|
cookies |
Read cookies across all origins |
tabs |
Get the current tab's URL and ID |
scripting |
Collect origins from all frames including iframes |
host_permissions (<all_urls>) |
Access cookies across all domains |
- Opaque origins (
"null") from sandboxed iframes are filtered out and skipped - When the popup opens, some iframes may not yet be initialized — clicking Query again will pick them up
- No data is stored locally or sent anywhere; all operations are in-memory only
# Production build
npm run build
# Development (watch mode)
npm start
# Build + zip for store submission → extension/1cookie.zip
npm run build:extensionLoad the dist/ folder as an unpacked extension in chrome://extensions.
Cookies may contain sensitive data such as session tokens. No data leaves the browser — everything is read in-memory via the chrome.cookies API and discarded when the popup closes. HttpOnly cookies are accessible only through the extension API and cannot be read by page JavaScript.