Decrypt & Export Microsoft Edge Data
Decrypt and export Microsoft Edge passwords, cookies, history, and bookmarks on Windows, macOS, and Linux — including Chromium 127+ App-Bound Encryption (v20).
Microsoft Edge is built on Chromium, so HackBrowserData treats it like Chrome — decrypting and exporting passwords, cookies, history, bookmarks, downloads, credit cards, extensions, and storage on Windows, macOS, and Linux, including Edge’s App-Bound Encryption (v20) cookies.
Warning
For authorized security research and DFIR only. Run it on systems and accounts you own or are explicitly permitted to assess — see About.
What you can extract
As a Chromium browser, Edge supports all nine categories. See the category matrix.
Commands
# Everything Edge has (default scope)
hack-browser-data dump --browser edge
# Edge passwords and cookies, into a custom directory
hack-browser-data dump --browser edge --category password,cookie --dir ./edge-exportedge is the --browser key. Output is one file per non-empty category — see Output & Data Formats.
Where Edge stores data
| OS | User-data directory |
|---|---|
| Windows | %LOCALAPPDATA%\Microsoft\Edge\User Data |
| macOS | ~/Library/Application Support/Microsoft Edge |
| Linux | ~/.config/microsoft-edge |
Each profile (Default, Profile 1, …) is exported and aggregated automatically.
Decrypting on each OS
On macOS, HackBrowserData asks for the current login password to retrieve Microsoft Edge Safe Storage. On Linux, v10 needs no keyring, while v11 needs an accessible D-Bus Secret Service. On Windows, recent Edge protects new cookies with App-Bound Encryption (v20), which needs the amd64 Windows ABE build. See FAQ & Troubleshooting for failure modes that can leave encrypted fields blank.
See also
- Google Chrome — the same engine and ABE scheme.
- Supported Browsers & Data ·
dump· How It Works - Cross-Host Decryption — collect on one machine, decrypt on another.