Private background remover with no image upload
Use bgcut when you want an interactive background remover without sending the source image to a background-removal server.
Your image stays on the device
bgcut.dev downloads application code, ONNX Runtime files, and the model it needs to run. The source image itself is decoded and processed in the browser.
Source image bytes, decoded pixels, the predicted mask, and the generated result are not sent to a bgcut inference backend.
WebGPU first, WebAssembly fallback
Automatic browser mode tries WebGPU when the browser and device can use it. When that path cannot run and fallback is allowed, bgcut can use WebAssembly instead.
Both paths keep inference local. Engine selection changes how the browser computes the result, not where the image is processed.
No account or per-image service request
The hosted remover does not require a bgcut account. There is also no per-image request to a bgcut inference service because that service is not part of the browser flow.
The device running the browser supplies the compute. Local processing is not the same thing as free infrastructure.