bgcut vs BG0
Both projects can remove image backgrounds locally in the browser without sending the source image to an inference backend. The main difference is scope. BG0 focuses on the browser app and browser library. bgcut also ships a CLI and Node.js API.
Facts checked
| Area | bgcut | BG0 |
|---|---|---|
| Hosted browser app | Yes. Local WebGPU with WebAssembly fallback. | Yes. Local WebGPU with WebAssembly fallback. |
| Browser library | The public package is centered on CLI and Node.js use; the hosted app owns its browser runtime. | Yes. @bg0/browser is a documented integration package. |
| Node.js API | Yes. | BG0 documents a browser-only package. |
| CLI | Yes, including multiple files and recursive directories. | Not part of BG0's documented product scope. |
| Source license | MIT. | Apache-2.0. |
Choose bgcut when
- You want a local CLI or Node.js API in addition to the browser tool.
- You want one package contract for file and directory automation.
- MIT licensing fits your project.
Choose BG0 when
- You specifically want a reusable browser background-removal package.
- Your project is browser-only and BG0's package contract fits it.
- Apache-2.0 licensing fits your project.
The browser privacy model is similar
BG0 documents local browser inference with no source-image upload, WebGPU when available, and WebAssembly fallback. bgcut follows the same high-level privacy boundary in its hosted browser app.
That means the decision is less about whether either project can run locally and more about which interfaces your application needs.
Compare the package contract before choosing
BG0 exposes @bg0/browser for adding background removal to a web application. bgcut's public Node.js contract is built around bgcut(), removeBackground(), removeMany(), and close().
If your integration is inside a browser application, inspect BG0's library first. If you need Node.js, shell automation, or directories, inspect bgcut's interfaces.
Sources
External product facts above were checked on 2026-09-29.