Batch Background Removal: Transparent PNGs and ZIP Export

For a batch of product photos or design assets, add up to 20 JPG, PNG or WebP files to QuickBGCut, start background removal and inspect the finished results. Files are processed one at a time on your device. Download a transparent PNG for each accepted result, or collect completed results in a ZIP. You do not need an account.

Use three checks before handing off the archive: the completed count matches your intended batch, each cutout passes review on its destination background, and the downloaded files open correctly. A completed model run is not an approval of image quality. Keep failed sources and their originals separate from accepted PNGs.

Background removal begins with boundary information. A sharp source with visible contrast gives the model more evidence than a compressed screenshot, a motion-blurred photo, or a subject photographed against a similar color. Leave margin around the subject so small edges are not cut off before processing begins.

Our lab uses four synthetic inputs with published generation records. The generated bottle includes a window scene behind amber glass, and the fictional portrait includes sky, water, and sand. Both produce a PNG, but retained background around the hair and glass shows why export success is different from a clean cutout.

QuickBGCut accepts files identified by the browser as image/jpeg, image/png, or image/webp, up to 20 MiB each (shown as 20MB in the interface). The queue holds up to 20 files, including completed files. A file can also be skipped if the queue already contains the same name, size, and last-modified timestamp. Check these conditions before trying the upload again.

HEIC photos, PDFs, and SVG files are not accepted by this tool. Export an actual JPG, PNG, or WebP copy in an editor first; changing the filename extension does not convert the image. If the queue is full, download completed results before removing items to make room. Keep your originals.

Add a JPG, PNG, or WebP file to QuickBGCut and process it in the browser. The first run also prepares the model. In the October 7 local test on an Apple M3 Pro, the four processing calls totaled 61.6 seconds. The first included model initialization and local asset loading; public-network download time was not measured. Background-tab scheduling can affect elapsed time, so these numbers are not a speed guarantee.

When processing a larger batch, test one file that contains the same lighting, camera angle, and background as the rest. If that representative file loses an important edge, changing the source setup is usually more useful than repeating the same export twenty times.

The synthetic bottle keeps its shape but has pale and warm edge pixels. The fictional Sample Name handwriting keeps its underline but has a light halo. The portrait keeps large sky fragments around the hair. All are technically successful PNG exports, and all need further edge review before publication.

Preview the PNG on white, black, gray, and the actual brand color. Zoom in for a hero image, then zoom out to the real avatar, product-card, or document size. A small defect may be irrelevant in an icon and unacceptable in a large banner.

Local processing still needs a network connection to download the model and WebAssembly runtime. During a first run, the download stage can take longer than the cutout itself. Keep the tab open while progress advances. A failed model download is different from a poor-quality cutout: retrying a network error may help, but repeating the same image does not repair missing hair or a white fringe.

After an error, first save any completed PNGs. Confirm the page and its model files can load, then retry one failed image. If the browser reports a memory problem or closes the tab, close other heavy tabs and try a smaller-dimension copy of the source. A file below the upload size limit can still expand into a large decoded image. A smaller copy reduces detail as well as memory use, so keep the original for a later attempt.

If it still fails, send support the browser version, device type, image dimensions, file format, and visible error text. Do not send a private signature or portrait just to report a loading error. These details help distinguish a download failure, unsupported browser feature, and memory limit without sharing the image itself.

PNG is the safest master format for these results because it preserves the alpha channel. JPG cannot store transparency. WebP can, but PNG remains easier to move between document editors, marketplaces, and design tools.

Keep the full-resolution PNG and create smaller derivatives from it. This avoids repeating the cutout whenever a platform needs a different crop or background. Store signatures, portraits, and unpublished products carefully even when the background removal itself happens locally.

The ZIP contains completed results only. Failed and still-queued files are not silently repaired or included, so compare the finished count with the files you expected before closing the tab. If ZIP creation fails, download completed PNGs individually. Building the archive needs additional memory because the finished files are assembled in the browser.

A white preview does not by itself mean transparency was lost. Some viewers place transparent pixels on white. Place the downloaded PNG over a dark or colored background in an image editor and inspect it there. If the whole rectangle stays white, check that you opened the downloaded result rather than the original, a screenshot of the preview, or a copy converted to JPG. If only the edge has a pale outline, use the halo diagnosis guide; a different viewer will not remove those pixels.