1Upload the images you want cut out — a clear subject against a distinguishable background gives the model the least to guess at.
2Wait while the segmentation model predicts a per-pixel alpha matte; there is no masking for you to do by hand.
3Check the edges in the preview, particularly hair, fur, glass and motion blur, which are where any automatic matte struggles.
4Download the result as PNG or WebP so the transparency actually survives — saving a cut-out as JPG puts the white back.
Remove Image Background FAQ
Can I process a whole batch of images?
+
Yes. Every image is segmented independently, so a set of product shots can be cut out in one pass — which is normally the point, since doing it by hand is the slow part of a catalogue shoot.
How does Remove Image Background decide what is background?
+
Concretely, a U^2-Net segmentation model predicts the alpha matte on whatever you upload, and the output is always written to a format that can actually carry transparency rather than silently flattening onto white. There is no manual masking step — a neural segmentation model does the separation and you get a transparent result back.
Anything specific to Image I should consider?
+
Yes — the pipeline reads the real format from the file header rather than the extension, so a mislabelled upload still works. That shapes both what the model sees and what the output can carry.
What format should the result be saved in?
+
One with a real alpha channel — PNG or WebP. Saving a cut-out as JPG throws the transparency away and composites the subject onto white, which defeats the entire operation and is the single most common thing that goes wrong here.
Which image formats does Remove Image Background accept?
+
All of the common ones — JPG, JPEG, PNG, WebP, GIF, BMP, TIFF, SVG, ICO, PSD, JFIF and HEIC. You can mix formats freely in one batch; each file is identified from its header and routed to the right decoder.
Is there a file size limit on Remove Image Background?
+
Yes: free accounts process images up to 25 MB each regardless of which image format you brought; ImageMagick, libjpeg-turbo, libpng and libwebp do the actual work. The cap is per file, so a batch of twenty 5 MB photos is fine even though the total is well over the limit.
Will Remove Image Background lower the quality of my images?
+
That depends on what you brought. A lossless source (PNG, BMP, TIFF) round-trips exactly; a lossy one (JPG, WebP, GIF) is already the product of one quantisation pass and only re-encodes if the operation genuinely requires it.
Can I run Remove Image Background on several images at once?
+
Yes, and mixing formats in the batch is fine — settings are applied per file with the right decoder for each. Free accounts run one file at a time; a pass removes that.
Why does a EPUB site host Remove Image Background?
+
EPUB.to is built around the open eBook format — XHTML in a zip, reflowable by design, and readable on hardware nobody has thought about the layout for. A book is a zip full of markup, images and fonts, so almost every job people bring to an eBook site is really a job on one of those things. Remove Image Background runs on the same upload and the same account as the conversions because that is where it is needed.
What should I do with the result once Remove Image Background is finished?
+
The converter on this site moves books between EPUB, MOBI, AZW3, PDF and DOCX, so a title ends up on whatever hardware is actually going to read it. Doing that after Remove Image Background means the conversion is made from the version you settled on, not from the one you were still fixing.
Is Remove Image Background here the same tool the sibling sites run?
+
The engines are shared — the same toolchain, the same workers, the same limits. What a EPUB site adds is a view on reflow: which of these operations a reflowable book genuinely supports, and which ones only make sense on the fixed-layout media inside it. It also starts from one fact about the format this site is named after: the book is a zip of XHTML with a manifest, so the text costs almost nothing and every decision that matters is about the embedded images and font subsets.
Do I need an account, and does anything get kept?
+
No account, and nothing is kept: uploads are deleted from the workers shortly after the job finishes, nothing is read and nothing is indexed. Free accounts exist for history and batch size, not for access.
