Frequently asked questions
If something here does not answer your question, write to us at service@cutoutpic.com.
Privacy
Is my image uploaded to a server?
No. Your browser downloads a segmentation model and runs it on your device, so the image never leaves it — the free preview has no upload path at all. A paid full-resolution export is planned; if you ever choose it, that will be the only case in which an image is sent to a server.
Is there a background remover that does not upload my photos?
Yes — this one. cutoutpic runs the model inside your browser with WebGPU or WebAssembly. You can confirm it yourself: open your browser devtools, watch the Network tab, and process an image. The only downloads are the page, the inference runtime and the model; no request carries your picture.
Do you store or train on my images?
The free preview cannot: the image never reaches us. The planned paid export will keep images only until a short retention period ends, and will never use them to train models, show them publicly or give them to anyone else.
Can I use the results commercially?
Yes. Your images remain yours, and so do the results. We do not train models on them, display them, or pass them to anyone else.
Using the tool
Do I need an account?
No. The free preview opens and works, with no sign-up and no usage limit.
Is it really free? Is there a watermark?
Background removal and PNG, JPG or WebP downloads are free, without an account or watermark. The free cutout has a resolution cap. A paid full-resolution export is planned but not open yet.
Does it work offline?
After the model has been cached, the processing itself needs no network. The page and the model still have to be loaded once.
Can I remove the background from several images at once?
Background removal processes one image at a time. The separate image converter accepts batches, but changes formats only: it does not remove backgrounds or bypass the cutout resolution cap.
Can I paste an image instead of choosing a file?
Yes. Copy a bitmap image or take a screenshot and press Ctrl+V (or ⌘V on a Mac) anywhere on the page to paste the image from the clipboard and remove its background in the browser without saving a file first. Pasting accepts bitmap clipboard data (image/*), and the finished cutout is downloaded as a file.
Formats and limits
Which formats are supported?
Input: JPEG, PNG and WebP, up to 12 MB (PNG inputs up to 10 megapixels; JPEG and WebP inputs up to 50 megapixels). Output: PNG or WebP with transparency, or JPG with a chosen background color, up to 1280 px on the longer side. Available formats depend on your browser.
Can I use a HEIC photo from an iPhone?
Not directly — HEIC is not accepted. Export or share the photo as JPEG or PNG first, then drop the converted file in. On an iPhone, Settings → Camera → Formats → Most Compatible makes new photos JPEG.
What resolution is the free download?
The free preview is capped at 1280 px on the longer side. That is enough for profile pictures, listings and web use. Print and full-size work need more; a paid full-resolution export is planned but not open yet.
Why does a PNG over 10MP fail or lag vs 1280px cutout export limit?
The cutout is resized to at most 1280 px on its longer side while preserving its aspect ratio. If you wonder why a PNG over 10MP fails upload vs 1280px cutout export limit: an uncompressed 10+ megapixel PNG (such as 4000 × 3000 px) decompresses in client RAM to over 48 MB of raw RGBA pixel canvas buffers, which can crash low-memory tabs during in-browser WASM/WebGPU inference. While JPEG and WebP inputs are accepted up to 50 megapixels, large PNGs are capped on intake at 10 MP to avoid tab crashes. Use our free in-browser converter to turn an oversized PNG into WebP or JPG first before removing the background.
Can I get a JPG or a white background instead of transparent?
Yes. After background removal, choose JPG in the export settings and select white or another background color. Choose PNG or WebP to keep transparency. Changing the format does not increase the cutout resolution.
Quality
Why is my result rougher than I expected?
Your browser is running compatibility mode (WebAssembly SIMD) rather than graphics acceleration (WebGPU). Without WebGPU (such as non-HTTPS pages, disabled hardware acceleration, or unsupported GPU drivers), inference falls back to slower WASM processing and the refined pass is unavailable. The active tier is shown next to the page heading.
How well does it handle hair, fur and fine edges?
Fine detail is the hardest case for any segmentation model, and both tiers here tend to merge loose strands into a solid edge. The refined tier (WebGPU) gives a tighter outline without the pale halo of the fast tier. Plain, contrasting backgrounds give the cleanest edges.
Why are there white or coloured edges around the subject?
That fringe is leftover background along the edge pixels — most visible when the original background was bright. A darker or evenly lit background helps; if the fringe matters, a quick pass with an eraser or feather tool in an editor removes it.
It says no subject was found. What now?
That no-subject check triggers when less than 0.5% of pixels qualify as foreground (such as a blank frame or flat wall), so an empty image is never returned in place of a cutout. True close-ups exceeding 99.5% foreground remain valid full-frame outputs, while unstable transitional masks (>90% edge band) are caught and rejected instead of returning grey smudges. Try an image with clearer subject contrast and space around the edges.
Why does the first image take longer?
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.
Does it work on a phone, Chromebook or Linux?
It should, wherever the browser supports WebAssembly SIMD — current Chrome, Edge, Firefox and Safari do, on any operating system. We test on desktop Chrome; phones and Chromebooks are not tested yet and are usually slower. Browsers that expose WebGPU get the refined tier automatically.