How to Remove a Background From an Image

The fast version

Open the background remover, drop your image on it, wait, download the PNG. Three steps, no account, no watermark, no credit counter.

The first run is slower than you expect. Your browser has to download the model itself before it can do anything, and it is not a small file. After that it sits in your browser's cache and every later run starts immediately. That download is the whole cost of the tool, paid once, and it is why there is no limit afterwards: nothing runs on our servers, so your fortieth image costs us exactly what your first one did, which is nothing.

What makes a good input image

The model does better when the photo makes the subject obvious. That sounds circular, but it cashes out in specifics you can control:

Contrast between subject and background. A dark jacket against a dark wall is genuinely ambiguous. A dark jacket against a bright wall is not. If you are shooting the photo yourself and know you will cut it out later, this decision matters more than everything else on this list.

One clear subject. Matting models are trained to find the salient object. Give them five people at varying depths, or a subject reflected in a mirror behind them, and the model has to guess what you meant. It will pick something, but maybe not your thing.

Resolution above roughly 500 pixels on the short side. The mask is computed at a fixed working size internally and scaled back to your image's real size. Feed it a 200 pixel thumbnail and you are asking the model to upsample its own understanding, so edges go mushy. If your source really is that small, run it through the image upscaler first, then cut it out.

In focus. A soft subject has soft edges, and the model cannot invent an edge that was never in the pixels.

Not already cut out badly. A JPEG that someone else cut out and flattened onto white has a fringe of white pixels baked into the subject. The model keeps that fringe, because as far as it can tell those pixels are part of the object.

Matting, not segmentation, and why hair is the hard case

This is the part most guides skip, and it is the thing that actually explains your results.

Segmentation answers a binary question for every pixel: subject or background? You get a mask of ones and zeros. It is fast, it is fine for a solid-edged object like a shoe, and it falls apart the instant an edge is not solid.

Matting answers a harder question: how much of this pixel is subject? The answer is a number between 0 and 1. A pixel sitting in the middle of a strand of hair might be 30% hair and 70% the wall behind it, because the strand is thinner than the pixel is wide. That is not a rounding error. That is physically what the camera recorded.

This matters because binary masks have to round. Round that 30% pixel down and the hair disappears into a bald, shrink-wrapped silhouette. Round it up and you keep a halo of wall color glued to your subject, which will announce itself the second you place the cutout on a background of a different color.

This is exactly why we use a matting model rather than a hard segmenter. It outputs a soft alpha channel with real intermediate values on wispy edges instead of a hard yes/no, and it runs a second refiner pass over exactly the pixels it was least confident about, which is usually hair. It is also permissively licensed, which is why we can use it on an ad-supported site at all. The two other well-known options in this category, RMBG-1.4 and MODNet, both have licenses that forbid commercial use, so they are off the table for us no matter how they perform. The license is the sharpest constraint in this whole project, sharper than quality, and it rules out models we would otherwise be glad to ship.

Now the honest part: fine flyaway hair against a busy background is hard for every tool in this category, including the ones charging you per image. When a single strand crosses a bookshelf, the model must decide, per pixel, how much of the color came from the strand and how much from the books behind it. Sometimes there is no recoverable answer. If your cutout of a windswept portrait against foliage looks imperfect, the problem is not that you picked the wrong tool. It is that the information you need is genuinely not in the file.

How to judge a cutout

Do not judge it on the checkerboard. The transparency checkerboard is a light grey pattern, and light grey hides exactly the errors you care about.

Instead, put the cutout on a solid color that is far from the original background. If you shot on white, drop it on saturated red or black. Then look for these four things:

1. A halo. A pale outline tracing the subject means original background pixels came along for the ride. Most visible on hair and on the shoulder line.
2. Erosion. The opposite failure. The mask sits slightly inside the true edge, so the subject looks shaved. Check fingers, ear tips, and thin things like glasses arms.
3. Holes. Look through gaps that should be transparent: between an arm and a torso, through the handle of a mug, between chair legs. Models often fill enclosed gaps because enclosed regions look like part of the object.
4. Semi-transparent solids. A subject holding a glass or wearing sheer fabric confuses the alpha channel, because the correct answer there really is partial transparency and the model has to guess how much.

Zoom to 100%. Halos are invisible at thumbnail size and glaring at full size, which is the size your customer's screen will use.

When to fix it manually instead

Automatic removal is the right default. It is not always the right finish. Reach for a manual tool in a real editor when:

• The edge is a straight line or a simple curve. A pen tool on a box, a phone, or a book beats any model, every time, and takes a minute. Models add wobble to lines that should be perfectly straight.
• The subject is transparent or reflective. Glassware, bottles, jewelry, water. The correct alpha for a wine glass depends on what is behind it, and no general model gets this right.
• Precision beats speed. Retouching a hero image for print is different work from cutting out 300 catalog thumbnails.

The useful middle path: run the automatic cutout, then use it as the starting selection in your editor and repair the 5% that is wrong. That is much faster than starting from nothing.

What people actually use this for

Product photos. The dominant use, and the easiest one. Products are usually solid-edged, well lit, and shot against a plain sweep. Most marketplaces want white or transparent, and consistency across a catalog reads as more professional than any single hero shot.

Profile pictures. Cut yourself out, drop a flat brand color behind, done. If you want the subject to stay in the scene, blurring the background often looks better than removing it, since it keeps the depth and lighting of the original instead of pasting you onto a color you were never lit for.

Stickers. Chat stickers, slide decks, thumbnails. Transparency is the whole point, and small errors are forgiving because the image ends up small.

One thing gone, not everything. To delete a photobomber but keep the scene, this is the wrong tool. The object remover fills in what should have been behind the thing you deleted, rather than deleting everything around your subject.

Save it as PNG, not JPEG

The most common way to destroy a good cutout is to save it wrong.

JPEG has no alpha channel. None. It cannot store transparency at all. Export a transparent image to JPEG and the transparency gets flattened, in many tools onto black. This is the origin of the very common question "why is my transparent background black?" The file went through JPEG somewhere, and the transparency was destroyed at that moment rather than lost in transit.

Save as PNG, or WebP if your destination supports it and you care about file size. Our guide to transparent PNGs covers the alpha channel, which formats hold one, and how to get out of the black-background trap.

Nothing gets uploaded

Every tool here runs the model inside your browser tab. Your photo is read into memory by JavaScript, processed on your own hardware, and discarded when you close the tab. There is no upload endpoint on this site at all.

You do not have to take our word for it, and you should not. Open developer tools, watch the Network tab, run the tool. The model file comes down. Your image does not go up, because there is nowhere for it to go. That is a verifiable claim rather than a promise, which is the point. Details on how private this is.

Speed depends on your hardware. With WebGPU (Chrome and Edge on desktop, mostly) the model runs on your GPU and a cutout takes a few seconds. Without it, the fallback is WebAssembly on your CPU: same result, much longer wait, roughly 5x to 60x depending on the machine. We break that down in what WebGPU means for image tools.