Background Remover — Free, Automatic, In-Browser (No Upload)

The model comes to your image, not the other way round

"Runs in your browser" is a claim worth interrogating, because it is used loosely. Here it means something precise: the segmentation model is downloaded to your device and executed there, and the photograph is never uploaded. The only network request is for the model weights — roughly 5 MB, fetched once and then cached.

That distinction is the whole point. A server-side background remover takes the picture itself, which matters when the picture is an ID document, an unreleased product shot, or someone else's face. The honest cost is that first run: about 5 MB has to arrive before anything happens. After that it is local and quick.

What the model is actually doing

It is a segmentation model, which means it makes one decision per pixel: subject, or background. It is not following an outline you drew, and it has no idea what the object is — a chair and a person are the same problem to it.

Holding that in mind explains everything below. The failures are not the model being unreliable; they are the cases where "is this pixel part of the subject" genuinely has no clean answer.

Where it struggles

• Fine strands. Hair and fur are finer than the boundary the model works at, so wisps get trimmed or a halo is left behind.
• Semi-transparent things. Glass, a veil, a plastic bottle — pixels that are genuinely part subject and part background, when the answer has to be one or the other.
• Colour matching the background. A dark jacket against a dark wall gives the model nothing to separate on.
• Motion blur at the edge. The boundary is spread across many pixels rather than sitting between two.
• Busy backgrounds. Where the subject does not stand out to you, it will not stand out to the model either.

The practical conclusion is worth stating plainly: a plain, contrasting background and sharp focus produce a noticeably better cut-out, and shooting for it beats fixing it afterwards. Two minutes rearranging a product against a blank wall saves more than any amount of editing.

Why the output is PNG

Transparency needs an alpha channel, and JPEG does not have one. This produces the most common mistake with cut-outs: save the result as JPEG and every transparent pixel comes back as solid white or black. There is no setting that fixes it — the format simply cannot store the information.

WebP and AVIF both support transparency and are the modern options when file size matters.

Using the result

Drop it onto a coloured background, a product listing, a slide, or a composite. One thing to expect: the cut-out is often larger than the photo it came from, because PNG is lossless and stores every pixel exactly. That is fine while you are still editing and wasteful once you ship it.

So do the transparency work first, then re-encode to WebP or AVIF at the end using the image optimizer, which keeps the transparency and drops the size considerably. Note that re-encoding to those formats at a quality setting is lossy — that is the point, and at sensible settings you will not see it.