Edge Portable
Stable · Microsoft ecosystem
Built from Microsoft’s official offline installer, keeping vertical tabs, Collections, and other Edge features.
Microsoft Edge · Windows x64 · Portable
Edge Portable
Microsoft Edge without an installer, built from Microsoft’s offline package. For people who want Edge compatibility and built-in features without letting it take over the system.
Installer comes from Microsoft’s official CDP feed. Version matches Edge Stable.
Downloads
Archives come straight from the Edge_Portable Releases, each with a SHA256 checksum.
Why a portable Edge?
Windows ships Edge as a system component: hard to remove, system-managed updates, profile scattered under the user directory. This build turns it into an ordinary folder:
- Fully isolated from system Edge — run both at once with separate profiles
- Profile and cache live in Data and Cache in the extraction root
- No registry writes, no update service; delete the folder to uninstall
- Fits on a USB stick, or a work PC where you want an unmanaged browser profile
- Vertical tabs, Collections, Copilot, and other Edge features remain available
How to use
- Download the Edge_Portable_Win64 7z archive from Releases.
- Extract anywhere.
- Double-click 开始.bat to create the shortcut, or run msedge.exe inside the version folder under Microsoft\Edge\Application.
- Data and Cache appear in the extraction root on first launch.
How to update
Portable Edge won’t auto-upgrade. This repo repacks Microsoft releases daily; overwrite manually:
- Quit the browser completely.
- Back up the Data folder in the extraction root.
- Delete the old Microsoft folder.
- Extract the new Microsoft folder next to it.
- Restore the Data folder in the extraction root.
Verify your download
Every Release lists the SHA256 of each archive. Run one PowerShell command after download and compare — a match means the file is byte-identical to the build output.
certutil -hashfile .\Edge_Portable_Win64_version_date.7z SHA256Build logs are public on GitHub Actions, so you can confirm the archive came from that exact run.
Chrome++ extras out of the box
Powered by Bush2021/chrome_plus. These are enabled by default and can be tuned or turned off in chrome++.ini.
- Profile and cache live in Data and Cache folders next to the app
- Double-click a tab to close it, keeping the last tab open
- Scroll the tab bar while hovering to switch tabs
- Address-bar text and bookmarks open in a new foreground tab
- View saved passwords without typing your Windows login password
- Right-click close, boss key, translate hotkeys, key mapping, launch/exit hooks (off by default)
FAQ
How is this different from the official installer?
Same engine and features — both come from official packages. Portable builds skip installation: no registry writes, no background updater. Profile and cache live in Data and Cache next to the app. Move the folder freely, or delete it to uninstall cleanly.
Does it auto-update?
No. Portable builds don’t register a system updater. This project checks official channels daily with GitHub Actions and publishes new archives to Releases. Download and overwrite manually; keep the Data folder to preserve everything.
How do I verify a download wasn’t tampered with?
Each Release body lists filename, size, and SHA256. After download, run certutil -hashfile yourfile.7z SHA256 in PowerShell and compare. Full build logs are public in Actions so you can match the archive to the run that produced it.
Where is my data, and how do I migrate PCs?
In the Data folder next to the browser (cache in Cache). Copy the whole folder to the new machine — bookmarks, passwords, extensions, and logins come along.
Can I move the data folder somewhere else?
Yes. The location is set by chrome++.ini inside the browser folder — edit the data_dir and cache_dir lines. Both an absolute path and %app% with relative levels work, where %app% is the folder holding the browser executable. Save and restart the browser; the folders are created at the new location. Two caveats: the file is UTF-16 encoded, so if you re-save it from Notepad pick Unicode or the config is silently ignored; and the default path already follows the program around, so you only need to change this to put data outside the program folder (on a larger partition, for example).
Antivirus flags the file. What now?
Chrome++ implements portability by injecting version.dll into the browser process (DLL side-loading). Some security tools heuristically flag that. Build scripts, workflows, and logs are public on GitHub; archives come from GitHub Actions with SHA256. You can also build locally from the repo if you prefer.
Is 32-bit or Windows 7 supported?
Only Windows x64 builds are published. System requirements follow upstream browsers, which have dropped Windows 7 / 8.1. Use Windows 10 or 11.
Can I run it next to an installed browser?
Yes. Portable builds use an isolated profile directory and can run side by side with an installed copy.
Is this paid or ad-supported?
Neither. The pipeline only unpacks, integrates Chrome++, injects, and compresses — no homepage changes, no preinstalled extensions, no bundled promo. Source is MIT-licensed and fully public.
Windows SmartScreen or Defender flags the download. Is it safe?
SmartScreen reputation is built per-file over time; brand-new GitHub Release assets often look unknown. Defender may also heuristically flag Chrome++ because it injects version.dll (a side-loading technique). The build scripts, workflows, and full logs are public on GitHub, archives ship from GitHub Actions with SHA256, and you can build locally from source if you prefer. If you still prefer not to run it, skip the download — nothing here is forced.
Can I sign in to Google or Microsoft and use sync?
Yes. Profile data lives in the portable Data folder, so bookmarks, passwords, and extensions sync the same way as an installed browser. Remember that a portable profile on a shared or public PC still contains those credentials — treat the folder like any other sensitive data.
Does it run from a USB drive or another PC?
Yes. Extract the archive anywhere with write access (USB stick, external disk, another computer). User data stays next to the app. Some security software may still block execution from removable media; if that happens, copy the folder to a local disk first.