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
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.
Archives come straight from the Edge_Portable Releases, each with a SHA256 checksum.
Stable · Microsoft ecosystem
Built from Microsoft’s official offline installer, keeping vertical tabs, Collections, and other Edge features.
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:
Portable Edge won’t auto-upgrade. This repo repacks Microsoft releases daily; overwrite manually:
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 SHA256
Build logs are public on GitHub Actions, so you can confirm the archive came from that exact run.
Powered by Bush2021/chrome_plus. These are enabled by default and can be tuned or turned off in chrome++.ini.
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.
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.
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.
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.
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.
Only Windows x64 builds are published. System requirements follow upstream browsers, which have dropped Windows 7 / 8.1. Use Windows 10 or 11.
Yes. Portable builds use an isolated profile directory and can run side by side with an installed copy.
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.
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.
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.
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.