Free plan: 1 conversion/hour, 1 file at a time
Go Unlimited →

Remove WebP Background

Transparent WebP images in One Click

Choose your files

*Files deleted after 24 hours

Transform files free, Pro users can convert much larger files; Sign up now

Uploading

0%

How to Remove WebP Backgrounds

1 Upload the WebP images you want cut out — a clear subject against a distinguishable background gives the model the least to guess at.
2 Wait while the segmentation model predicts a per-pixel alpha matte; there is no masking for you to do by hand.
3 Check the edges in the preview, particularly hair, fur, glass and motion blur, which are where any automatic matte struggles.
4 Download the result as PNG or WebP so the transparency actually survives — saving a cut-out as JPG puts the white back.

Remove WebP Background FAQ

Does my source format affect the quality of the matte?
+
Yes. WebP carries both a lossy VP8 mode and a lossless mode plus full alpha, typically landing 25-35% under a JPG of matching visual quality. Compression artefacts around a subject are exactly what a segmentation model has to disambiguate, so cleaner input gives a cleaner edge.
Yes — the same .webp extension can hold a lossy VP8 frame, a lossless one, or an animation, so the sensible processing path is decided per file rather than per extension. That shapes both what the model sees and what the output can carry.
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.
Concretely, a U^2-Net segmentation model predicts a per-pixel alpha matte and the background is cut away — but a lossy source has soft, compressed edges, so the matte is refined afterwards, and the output has to go to a format with an alpha channel rather than back to a lossy one. There is no manual masking step — a neural segmentation model does the separation and you get a transparent result back.
Yes. Drop the whole set into the upload area and they queue in parallel with identical settings — that is the main reason to do this in a browser rather than one file at a time in an editor. Free accounts run one file per batch; a pass lifts that.
Camera EXIF (ISO, shutter, lens, GPS) and the embedded ICC profile are carried across by default, because dropping the profile is what makes colours shift on re-import. Use the privacy option to strip metadata before download if you are about to publish the file.
Yes: free accounts process images up to 5 MB each, which covers essentially every camera JPG and phone photo; the work is done by libjpeg-turbo and libwebp, the same libraries a desktop editor links against. Larger files are the one thing the free tier will stop you on, and the limit is per file rather than per batch.
A lossy source is already the result of one quantisation pass, and any operation that has to re-encode adds a second. Where the job can be done without touching the pixel data we do that instead, and where it cannot you choose the quality factor yourself rather than getting a fixed default.
WORD.to is built around the editable end of a document's life — the DOCX that is still being written, still being styled and still being argued over, before anyone flattens it for sending. Office files are containers full of other people's media — images, embedded audio, fonts — so the work people need on them is usually the work they would need on those contents anyway. Remove WebP Background shares the upload, the caps and the account with the conversions for that reason.
The converter on this site takes documents out to PDF for sending, to images for embedding and to plain text for anything that has to read them programmatically, and back the other way. Doing that afterwards keeps the editable original around, which is the part you cannot get back once it has been flattened.
The engines are shared — the same document toolchain, the same workers, the same limits. What a Word site adds is a view on what survives leaving the Office format and what does not, which is the question every one of these jobs actually turns on. It also starts from one fact about the format this site is named after: the document is a zip of XML, so text edits are cheap and the weight is almost always the embedded images.
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.

Rate this utility
5.0/5 - 0 votes
ns6.com — Free WHOIS privacy, DNS and SSL on every domain.
Or release your files here