Chrome Portable
Stable · Recommended daily driver
Follows the Google Chrome Stable channel — a solid long-term default browser.
Windows x64 · No install · Open-source automated builds
Portable Chrome, Edge & Helium
Unzip and run. No installer, no registry writes — your profile stays next to the app. Rebuilt daily from official packages via GitHub Actions, with public logs and checksums.
4
Build targets
3 browsers · 4 release channels
Daily
Tracks upstream
Repackaged when official builds ship
SHA256
End-to-end checks
Upstream hashes verified while downloading
Smoke
Launch test
Real browser start before publish
Downloads
Pick a browser and channel. Every archive is built by GitHub Actions and published straight to that browser’s Releases page.
Chrome Portable Beta
Beta · Try features early
Follows Chrome Beta, about four weeks ahead of Stable. Don’t share one Data folder with Stable.
Edge Portable
Stable · Microsoft ecosystem
Built from Microsoft’s official offline installer, keeping vertical tabs, Collections, and other Edge features.
Helium Portable
Stable · Ad-blocked, de-Googled
Stable builds of imputnet/helium — a Chromium fork that blocks ads and strips Google telemetry by default.
Why this portable set is different
Most “green editions” online have unclear provenance. Here, every step is something you can re-check yourself.
Installers come straight from official channels
Chrome uses Google’s Omaha update API, Edge uses Microsoft’s CDP feed, Helium ships via upstream GitHub Releases — no third-party mirrors.
Build stops if hashes don’t match
The upstream SHA256 is recorded first, recomputed while downloading, and the build aborts on mismatch. A doubtful installer never enters the archive.
Injection is verified, not assumed
After packaging we parse the PE import table and assert Chrome++’s version.dll is injected as a relative import — not merely “looks successful”.
Portable mode is smoke-tested
We extract the final archive, launch the browser, and confirm the profile lands inside the unpacked folder. Portability is proven, not claimed.
No closed steps
Build scripts, workflows, and full logs live on GitHub. Archive SHA256 values appear in each Release body for independent comparison.
Nothing extra is bundled
Only unpack, integrate Chrome++, inject, compress. No homepage hijack, no preinstalled extensions, no promo payload. Source is line-reviewable.
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)
Project repositories
One repo per browser, all sharing the same portable builder core.
Chrome-Portable
Piracola
Portable Google Chrome. Stable and Beta channels ship in the same Release.
Edge_Portable
betacola
Portable Microsoft Edge on the official Stable channel, built from Microsoft’s offline installer.
Helium_Portable
Piracola
Portable Helium tracking upstream Windows x64 stable builds.
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.
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.