The image stays on your device
When you drop an image in, your browser downloads a segmentation model and runs it locally. Nothing about the picture is transmitted: no upload, no temporary copy on a server, no queue. This is not a promise about how we behave — it is how the free path is built. You can confirm it yourself in your browser devtools: open the Network tab and watch that no request carries your image.
The browser must download the model before the first cutout; a refined model may also download on supported devices. Later runs can reuse cached files while browser storage remains available. Connection speed, device memory and processing mode affect the wait.
Two quality tiers, chosen automatically
The page checks what your browser can do and picks a path. You do not choose anything.
- Graphics acceleration (WebGPU) — a fast result appears first, then a refined model loads in the background and replaces it. Outlines come out noticeably tighter, without the pale halo of the fast tier.
- Compatibility mode (WebAssembly) — only the fast model runs. Results are still usable, but edges are rougher and processing takes longer.
The tier in use is shown next to the page heading, so you know what to expect before you start rather than after the result disappoints you.
Getting a good cutout
- A subject that stands out from its background works best — contrast in brightness or colour matters more than resolution.
- Even, diffuse light beats hard shadows. A shadow that touches the subject is often read as part of it.
- Very fine detail — loose hair, mesh, fur against a busy background — is the hardest case for both tiers: strands tend to merge into a solid edge. A plain, contrasting background helps more than anything else.
- If nothing separable is found, you get an explicit message rather than a blank image. That is deliberate: a silent empty result is worse than a refusal.
Limits
- Input: JPEG, PNG or WebP, up to 12 MB per file (or paste directly from the clipboard with Ctrl+V / ⌘V). To protect browser Canvas memory, PNG inputs are capped at 10 megapixels, whereas JPEG and WebP inputs support up to 50 megapixels — convert a >10 MP PNG to JPG or WebP first in the on-device image converter.
- Output: PNG or WebP with transparency, or JPG with a chosen background color, up to 1280 px on the longer side. Export formats are probed with a 1×1 blank canvas so unsupported encoders are never mislabeled.
- No npm image-cutout library or third-party REST API is offered — cutoutpic runs interactively in your browser, and a paid server-side full-resolution export is planned but not open yet.
What your browser needs
Any current version of Chrome, Edge, Firefox or Safari will work. WebAssembly with SIMD is the minimum; WebGPU unlocks the refined tier. The page must be served over HTTPS — browsers only expose graphics acceleration in a secure context.