Local background removal guides
Practical notes for browser privacy, WebGPU and WebAssembly, Node.js, CLI batches, image formats, and the bgcut processing pipeline.
How to remove a background without uploading your imageLearn how local background removal works in a browser, what still downloads from the site, and how to verify that your source image is not sent for inference.WebGPU vs WebAssembly for local background removalUnderstand the WebGPU and WebAssembly paths used for browser background removal, why a local tool needs both, and what fallback behavior means.How to remove image backgrounds in Node.jsUse bgcut from Node.js with one reusable local runtime, single-image removal, batch iteration, output formats, engine selection, and typed errors.How to batch remove backgrounds from the command lineUse the bgcut CLI for multiple images and recursive directories, choose output locations and formats, and keep one warm local runtime for the batch.How local AI background removal worksFollow a local background-removal job through image decode, resize and normalization, ONNX inference, matte restoration, compositing, and export.PNG vs WebP vs JPEG after background removalChoose an output format after background removal based on transparency, compatibility, file size needs, and what bgcut actually writes.What 'no upload' means for background-removal privacySeparate local inference from ordinary website traffic, understand which bgcut data stays on your machine, and verify the boundary with browser tools.Browser, CLI, or Node.js for background removal?Choose the bgcut interface that matches interactive editing, shell automation, directory batches, or application code without changing the local-inference model.