How on-device removal works
The page downloads the BiRefNet model (115 MB, or 94 MB for the CPU engine) and ONNX Runtime Web once, from the same site, and caches them. Your image is opened in the tab's memory, processed on your GPU through WebGPU or on your CPU through WebAssembly, and the result is saved straight from the tab to your downloads.
How to check it yourself
- Open your browser's developer tools and the Network panel, then remove a background: no request carries your image.
- Load the page once, turn off Wi-Fi, and remove another background: it still works.
- The site's security policy only allows connections to itself and to a cookieless page-view counter.
Who this matters for
Unreleased product shots, client work under NDA, photos of children, ID documents, medical and legal images: anything you would rather not hand to a third-party server. Clipout gives the same result without that trade-off.
Questions
Does Clipout keep a copy of my images?
No. There is no upload endpoint, so there is nothing to keep. Your images stay in your browser tab.
Does it really work offline?
Yes. After the first visit the page and the model are cached; you can also install Clipout as an app from your browser's menu.
What does the site measure?
Cookieless page views and coarse tool events (such as which engine ran and a size band), never file names or image content. You can switch analytics off in the cookie preferences.
More background removal tips in the complete guide, or go back to the background remover.