Background remover before-and-after cutout of a car on a checker-style transparent panel.
Example cutout from rembg showing a local background remover result beside the source photo. rembg example outputs · danielgatis/rembg (MIT) · examples from the public repository.

For Windows, download rembg-cli-cpu-installer.exe from danielgatis/rembg releases. The GPU alternate on the same tag is rembg-cli-gpu-installer.exe. No winget package was verified for this guide.

rembg-cli-cpu-installer.exe

For macOS and Linux, install from PyPI with the README extras:

pip install "rembg[cpu,cli]"

Checklist before you run a file

  1. Confirm the publisher path. The repository must be danielgatis/rembg, not a random fork with a similar name.
  2. Confirm the asset name. CPU and GPU installer names are exact. A “rembg-setup.exe” from a review portal is a red flag.
  3. Confirm the tag. Prefer a current v* release. Avoid ancient prereleases unless you know why.
  4. Confirm the door. Windows uses Releases. macOS and Linux use pip per README. Do not invent brew or winget ids.
  5. Prove one cut. Run rembg i on a tiny local file before you point the background remover at a full catalog folder.

SmartScreen and unknown publishers

Windows may warn on an unfamiliar publisher. That warning is not permission to switch mirrors. Re-open the GitHub asset list, confirm the hash of the name, and continue only if it still matches. Safety deep dive: is it safe.

What “safe” does not mean

A safe download path does not guarantee a perfect mask on every photo. Hair, glass, and busy backdrops still need review. Safe means the binary came from the project release door, not that every cutout is gallery-ready without a glance.

Continue with Windows install, for this computer, and first hour.

Mirrors to avoid

Search ads for “background remover download” often lead to bundlers. If the page asks you to run a second installer to “enable cutout,” stop. Return to GitHub Releases or PyPI and start over.

Hash the name, not the rumor

You do not need cryptography to catch most bad downloads. Matching rembg-cli-cpu-installer.exe character for character already filters the worst adware renames. If your org requires checksums, fetch them only from the same GitHub release that published the exe.

Never trust a checksum pasted into a blog comment. Blog comments are not a background remover release channel.

Pip authenticity

On macOS and Linux, install into a fresh virtualenv when you can. Pinning a known-good rembg version after verification is a team choice; this guide avoids hard-coding dotted pins in footers and stamps. Prefer the current package from PyPI after you read the matching GitHub tag notes.

If pip resolves a different project name with “rembg” in a typo-squat, abort. The package name is rembg, and the homepage should point back at danielgatis/rembg.

Operational rule

Write the download URL into the ticket or chat when you install. Future you will thank present you when someone asks which background remover binary landed on the studio PC.