Open danielgatis/rembg releases and pick a tag that starts with v. The assets that matter for Windows are rembg-cli-cpu-installer.exe and rembg-cli-gpu-installer.exe. macOS and Linux readers use pip instead of a native installer on those tags.
Prefer the CPU installer unless you already maintain a working CUDA stack. The GPU installer is larger and only helps when onnxruntime-gpu requirements are already met, as the rembg README explains.
Which asset to take
| Need | Asset | Notes |
|---|---|---|
| Windows everyday | rembg-cli-cpu-installer.exe | Primary background remover path |
| Windows with CUDA | rembg-cli-gpu-installer.exe | Same tag, optional |
| macOS / Linux | pip install "rembg[cpu,cli]" | No native installer on release |
If SmartScreen or Gatekeeper-style prompts appear on Windows, re-check that the file name still matches the Releases list. Do not “fix” a blocked background remover install by grabbing a second binary from a review portal. Guide: Windows install, macOS, Linux.
Release habit
Keep one update door forever. Return to the same Releases page for the next Windows installer, or upgrade rembg with pip on macOS and Linux. Document which asset this PC used so the next person does not mix CPU and GPU installs by accident.
Safety notes: download safe. Repo overview: GitHub. Machine chooser: for this computer.
After you download
Run the installer, confirm rembg --help, and cut one small file before you batch a folder. First hour: installed. First run: first run.
A background remover release page should stay boring: exact names, same publisher, no surprise “setup assistant” from a search ad. If a page offers a renamed exe, leave.
Official releases
All releases on GitHub- GitHub stars
- 24,744
- Downloads, last 3 releases
- 619
- Latest version
- 2.0.84
- rembg-cli-cpu-installer.exe 114 MB 167 downloads
- rembg-cli-gpu-installer.exe 230 MB 173 downloads
2.0.83
v2.0.83
- rembg-cli-cpu-installer.exe 113 MB 140 downloads
- rembg-cli-gpu-installer.exe 230 MB 131 downloads
2.0.82
v2.0.82
- rembg-cli-cpu-installer.exe 113 MB 3 downloads
- rembg-cli-gpu-installer.exe 230 MB 5 downloads
Counts come from the GitHub API at build time and only cover the v* tags shown here. Package managers (winget, Homebrew, Snap, Flathub) and app stores are not included.
Reading a release page without rushing
A careful background remover download starts by reading the release title, the publish date, and the asset list in that order. Ignore comment spam and third-party “mirror” links pasted under the assets. The only files that matter for Windows are the two exe names documented in research: the CPU installer and the GPU installer.
If a friend forwards a Dropbox zip that claims to be rembg, decline it. Ask them for the GitHub Releases URL instead. Shared folders hide publisher identity, which is exactly what a safe background remover path is trying to preserve.
CPU versus GPU without mythology
The CPU installer is the default for most people who typed background remover into a search box. It avoids a CUDA scavenger hunt on day one. The GPU installer exists for shops that already run onnxruntime-gpu successfully. Starting on GPU without that stack turns a simple install into a driver puzzle.
When in doubt, install CPU, prove rembg i, then evaluate GPU later on a second machine if you need speed. Keeping the first proof boring protects the catalog deadline.
Pip users still watch Releases
Even if this computer uses pip, skim the Releases notes when a new tag lands. CLI flags and model notes often appear there first. That habit keeps macOS and Linux background remover installs aligned with what Windows teammates see.