Background Remover
Remove the background from a photo with AI — runs locally in your browser
Drop an image — JPG, PNG, or WebP. Best results with a clear subject against a less-complex background.
Max file size: 50MB
How to Background Remover Online
Remove the background from a photo with one click — gives you a PNG with transparent background.
- Drop an image. JPG, PNG, or WebP all work. Best results with a clear subject against a less-complex background.
- Wait for processing. The first image triggers a ~70 MB model download (one-time per session). Subsequent images skip this step.
- Each image processes in 5–20 seconds depending on resolution. Watch the progress indicator.
- Download the result as a PNG with transparent background. Open it in any image editor or compositing app.
About Background Remover
Removing the background from a photo used to be a Photoshop skill — Pen tool tracing around the subject, refining the mask edge, painting in the gaps. A 30-minute job for a clean result. Modern neural networks do the same thing in seconds and at decent quality, which has democratized the operation: you can remove a background without learning Photoshop.
This tool runs **@imgly/background-removal** entirely in your browser. The library wraps a U²-Net-style neural network — a model architecture specifically designed for salient object detection — and runs it via ONNX Runtime Web on WebGL or WebGPU. Drop an image, get a transparent PNG back. The model is the same kind that commercial 'remove.bg' style services use; the difference is this one runs locally instead of on someone's server.
**The use cases**:
- **Product photos for online listings.** A clean subject against transparent background lets you composite over any backdrop or context image. - **Social media graphics.** Pull a subject out, drop them onto a brand-color background or in a designed layout. - **Personal photos.** Cut yourself out of a vacation photo for a profile picture or composite. - **E-commerce thumbnails.** Quick cutouts for marketplace listings where the background is distracting. - **Stickers / cutouts for messaging apps.** Subject-only PNG works as an iMessage sticker or a Discord emoji.
**The quality picture.** Modern background-removal models are very good at clean cases:
- **Clean subjects against distinct backgrounds**: a person against a wall, a product against a sweep, a pet against grass. Output: crisp edges, accurate hair boundaries, no visible artifacts. - **Slightly noisy cases**: subject partially obscured, similar-color background, complex lighting. Output: usable cutouts with occasional edge artifacts. - **Hard cases**: glass / transparent objects, fur with similar background color, hair flying in motion, semi-transparent edges. Output: imperfect, may need touchup in an image editor. - **Pathological cases**: subjects that fade into the background, multiple subjects with overlap, no clear subject. Output: poor — sometimes nothing is identified as the subject.
For most casual / social-media use, results are 'good enough'. For commercial product photography or print-quality work, professional tools (Photoshop's Select Subject + Refine Edge, commercial services with human review) produce cleaner edges.
**Performance.** The neural network model is ~70 MB compressed. On first run, it has to download from a CDN — expect 30 seconds to 2 minutes depending on connection speed. After that, the model is cached in your browser's IndexedDB storage and reused for the rest of the session. Subsequent images:
- **Small images (under 1 MP)**: 3–5 seconds. - **Medium images (1–5 MP)**: 5–15 seconds. - **Large images (5–20 MP)**: 15–60 seconds.
The work happens on your GPU via WebGL or WebGPU. A faster GPU produces faster results; integrated graphics work but are slower. Discrete GPUs (NVIDIA, AMD) run the model at near-real-time speeds.
**Output format.** PNG with transparency. The output has the same dimensions as the input; pixels that were background are now transparent (alpha = 0), pixels that were subject have their original color with alpha = 255. Semi-transparent edge pixels (the boundary between subject and background) have intermediate alpha values, which is what creates the smooth edge.
**File size.** PNGs with large transparent regions compress well — usually 30–60% of the source image size. For very large source images, the PNG output is large in absolute terms but smaller than the source.
**Privacy.** This is the headline feature. The image, the processing, the result — all stay in your browser tab. The only network requests are the one-time model-weight downloads from a CDN, which are public model files that don't reveal anything about your image. Subsequent images don't trigger any further requests. Verify in DevTools — the network panel goes silent after the model loads, and only the image-blob URLs change in the document.
Commercial cloud background-removal services upload your image to their servers, run the model there, and return the result. For most users that's fine. For sensitive photos — private portraits, confidential product designs, anything you'd rather not have a third party hold a copy of — local processing is the right answer. That's what this tool offers.
**Limitations:**
- **WebGL2 required.** Some old browsers and some VMs don't have WebGL2 support. The model fails to load on those; the error message indicates the cause. - **Memory.** Very large images (over 4000×4000 pixels) can exhaust browser memory during processing. Resize before uploading if you hit this. - **Multiple subjects.** The model picks one salient subject per image. For images with multiple subjects, you may get all of them or just one, depending on the model's interpretation. - **No fine-tuning controls.** This tool exposes the default model with default parameters. For tighter control over edge softness, threshold, or matting quality, professional tools are the right pick.
**Edge cases handled:**
- **Empty input / wrong file type**: clear error rather than crash. - **Network failure during model load**: error indicates the CDN fetch failed; user can retry. - **WebGL2 unavailable**: error explicitly mentions WebGL2 requirement. - **Object URL lifecycle**: source and result URLs are revoked on unmount and on new-file-load. No memory leaks. - **Progress reporting**: the model exposes progress callbacks for both download and inference; the UI surfaces these so the user sees that something is happening.
In short: it's the AI-powered convenience tool for the cases where you don't need pixel-perfect edges and want the result in 10 seconds instead of 30 minutes.
Related Tools
Frequently Asked Questions
How does the AI background removal work?
The tool uses **@imgly/background-removal**, an open-source library that runs a U²-Net-style neural network in your browser via ONNX Runtime Web (a JavaScript port of Microsoft's ONNX inference engine). The model is trained on ~100k images of subjects-against-backgrounds and learned to predict 'subject' vs 'background' for every pixel. It runs on WebGL2 (or WebGPU when available) — your GPU does the work, the result is a transparent PNG with just the subject cut out.
Why is the first run so slow?
The neural network model is ~70 MB. On first run it has to download from a CDN to your browser, which takes 30 seconds to 2 minutes depending on your connection. After that, the model is cached for the rest of the session — subsequent images process in 5–20 seconds each. The model lives in browser storage (IndexedDB), so it survives tab reloads in the same session but gets re-fetched on a fresh visit.
How good is the quality?
For **clean subjects against distinct backgrounds** (a person against a wall, a product against a white sweep, a pet against grass), the results are very good — clean edges, accurate hair/fur boundaries, no visible artifacts. For **complex scenes** (a person in a crowd, a subject against a similar-color background, multiple overlapping subjects), the model struggles and you get partial cutouts. For **transparent or reflective subjects** (glass, polished metal, hair against a similar background), expect imperfect edges. Roughly: 80% of casual photos give 'good enough for social media' cutouts; 60% give 'good enough for product listings'; 30% give 'good enough for print'.
Why is the output a PNG?
Because PNG supports transparency (an alpha channel), and the whole point of background removal is to produce an image with transparent background. JPG doesn't support transparency — pasting a JPG cutout over a different background shows a white box where the transparency should be. WebP supports transparency and would be a slightly smaller file, but PNG is the universal format for transparent images and works everywhere.
Does it work for non-person subjects?
Yes. The model is trained on diverse subjects: people, animals, objects, products, vehicles, food. It generally works well on anything that has a clear visual boundary against a background. It works less well on subjects without clear boundaries (smoke, fire, water spray, foliage edges) because the boundary itself isn't well-defined.
Can I use this for product photography?
Yes for casual/social-media use. For commercial product photography intended for catalogs or print, professional retouching tools (Photoshop's Select Subject + Refine Edge, Topaz Mask AI, or commercial cloud services with manual review) produce cleaner edges. This tool is the 'good enough quickly' option; professional tools are the 'perfect with more effort' option.
Is the image uploaded to a server?
No. The entire neural network runs in your browser via WebAssembly / WebGL. The model weights are fetched once from a CDN (just like a library — they're public files, not your image). Your image is read into memory, processed by the in-browser model, and the cutout is generated locally. The only network traffic is the one-time model download. Verify in DevTools — subsequent images produce zero requests.