dump
Extract and decrypt browser data — the default command.
dump extracts and decrypts data from detected browsers and writes it to disk. It is the default command, so hack-browser-data … is the same as hack-browser-data dump ….
Flags
| Flag | Default | Description |
|---|---|---|
-b, --browser | all | Target browser, or all |
-c, --category | all | Data categories (comma-separated), or all |
-f, --format | json | Output format: json, csv, or cookie-editor |
-d, --dir | results | Output directory |
-p, --profile-path | (auto-discover) | Custom profile directory — find it via chrome://version |
--keychain-pw | (none) | macOS login password for non-interactive Keychain access |
--zip | false | Compress the output into a zip |
Categories: password, cookie, bookmark, history, download, creditcard, extension, localstorage, sessionstorage.
Output is one file per non-empty category in --dir — see Output & Data Formats
for the file model and per-category schema. Run list
to discover profiles, then use the canonical browser key from Supported Browsers
.
Examples
# Everything, from every detected browser (the default)
hack-browser-data dump --browser all
# Just Chrome history, as CSV
hack-browser-data dump --browser chrome --category history --format csv
# Several categories at once, into a custom directory
hack-browser-data dump --browser edge --category password,cookie --dir ./edge-export
# Point at a specific profile directory
hack-browser-data dump --browser chrome --profile-path "/path/to/User Data/Profile 1"Warning
With the default
--category all,dumpexports passwords, cookies, and credit cards along with everything else. Scope it down with--categoryif you don’t need sensitive data.
On macOS, selected Chromium browsers and Safari can require the current login password for Keychain access. Interactive input is hidden; use --keychain-pw only when non-interactive execution is necessary. See the macOS FAQ
.