Remove Background from WebP Images (Keep Transparency)

WebP transparency survives background removal, but only if you ask for it. The format supports an alpha channel, and a background remover treats a WebP file the same way it treats a PNG: it finds the subject, replaces everything else with transparency, and hands you back a cutout. The caveat is the export step. Choose transparent WebP and you get a modern, compact file with real alpha. Choose an export that writes a white or coloured matte and the transparency is gone — you have a flat image with a painted background, which is the exact opposite of what you wanted.

The second caveat is less about the file and more about the destination. Modern browsers render transparent WebP natively, so anything you host yourself is fine. Marketplaces are stricter and often publish an explicit list of accepted formats that predates WebP. If your cutout is headed for a product listing, the format question comes before the quality question.

This guide covers both sides: how WebP handles transparency, what Google’s own published figures say about file size, the step-by-step workflow, the four pitfalls that quietly ruin a WebP cutout, and how to decide between transparent WebP and transparent PNG for a given destination.

What’s Different About WebP and Transparency

WebP is not one format, it is two, and both can carry transparency:

The interesting combination is lossy WebP with alpha. It produces transparent images much smaller than the equivalent PNG — this is the point Google made in its own WebP announcement, and it is the whole reason a transparent WebP is worth caring about for a catalogue. A transparent PNG of a product shot can be surprisingly heavy, because PNG is a lossless format and it stores every edge pixel exactly. Lossy WebP trades a small amount of colour precision for a large reduction in bytes.

One practical consequence: a tool that only accepts PNG or JPEG will force you to convert before you start, which costs you a generation of quality and a step in the workflow. Working with a tool that reads WebP directly removes both. If you need to move between formats, our image converter covers that direction, including the reverse case where a platform demands PNG.

The Size Argument, With Google’s Own Numbers

File size is the reason WebP exists, so it is worth quoting the figures from the source rather than repeating a vague claim that it is “smaller”. Google reports that:

• lossless WebP comes out around 26% smaller than PNG. Measured on their own test corpus, at equivalent quality.
• lossy WebP comes out around 25–34% smaller than a comparable JPEG at equivalent quality.

The honest summary: WebP usually wins on size, and the win is usually large enough to matter for a web page or a large catalogue. Verify it on your own busiest images rather than trusting a headline percentage — and read those figures as published benchmarks, not as a guarantee for every file.

Step by Step: Remove the Background from a WebP Image

The workflow has four steps, and only the last one is easy to get wrong:

If you need a solid colour or a custom background behind the cutout, that is a setting in the same tool rather than a separate editing session. The reverse direction works too: when a design tool exports PNG and you want WebP at the other end, the same WebP background removal path covers the cutout, and the image converter handles the format change, so you never run the job twice.

The Four Pitfalls That Ruin a WebP Cutout

These are the reasons people conclude that “WebP doesn’t do transparency” when in fact something in the pipeline flattened it:

Three of these four are pipeline problems rather than format problems, which is the useful takeaway: when a WebP cutout goes wrong, look at the steps around the background removal before you conclude the format cannot do the job.

Does My Destination Accept WebP?

Browser support is broad. Modern browsers render WebP, including transparent WebP, natively, so a cutout you host yourself will display correctly for essentially every visitor. If the image lives on your own site, the format question is closed.

Marketplaces are a different matter. Their requirements are written for their own rendering pipeline, and they enumerate what they accept. Amazon’s documented main-image formats are JPEG, TIFF, PNG and non-animated GIF, with JPEG recommended — WebP is not among them. Amazon’s documented formats don’t include WebP, so check the current spec before uploading, and export PNG when in doubt. Specifications change, so treat any third-party summary — including this one — as a prompt to open the official page rather than as the final word.

The practical rule that follows:

• Your own website: transparent WebP. Smaller files, no compatibility risk, and it renders natively in modern browsers.
• Marketplace listings: transparent PNG. It is on the documented list, it is universally accepted, and it will not be the reason a listing gets rejected.
• Anywhere you are unsure: export PNG, and keep the WebP as your web-facing master.

Because both outputs come from the same cutout, this is not a decision you have to make before you start. Run the background removal once and export twice if you need to — the alpha channel is identical either way.

WebP vs PNG vs JPEG for Transparent Product Shots

For cutouts specifically, the three formats are not interchangeable. Only two of them can hold transparency at all:

JPEG is in the table to make the point that it is not an option for a cutout: it has no alpha channel, so saving a cutout as JPEG fills the transparent area with a solid colour. That is exactly the matte problem from the pitfalls section, arrived at from the other direction.

If you are optimising a whole catalogue rather than a single file, transparency and compression are separate problems — which is the subject of the next section.

Compress After You Remove the Background

A transparent image is not automatically a small image. Removing the background deletes pixels, but the subject that remains can still be heavy — especially at catalogue resolution, and especially if you exported PNG for compatibility. Compressing after the cutout is the step that brings the file size back down.

The rule to hold on to: compress without flattening the alpha. Plenty of compression settings and export presets are designed for ordinary photographs and will composite your cutout onto white on the way out. If a “compressed” file suddenly has a white background, that is what happened — the compressor, not the background remover, is the culprit.

The image compressor handles the size reduction step, and it scales the same way: batch the cutouts, then batch the compression, checking the output on a coloured background so a lost alpha channel is obvious immediately. If page speed is the real goal rather than file size for its own sake, our guide to WebP and page speed covers the delivery side — caching, decoding, and where the bytes actually cost you.

For teams doing this at volume rather than by hand, RMBG.PRO’s REST endpoint is a single POST to https://api.rmbg.pro/v1.0.1/remove_background with an X-API-KEY header, so the cutout can sit inside an upload flow or a CMS save hook instead of being a manual step. There are integrations for WordPress, Shopify and PrestaShop for the same reason, and a macOS app for desktop work.

Background removal in the browser costs 1 credit per image, and a new account starts with 10 free credits — enough to run your own images through the full WebP-and-PNG export pair before deciding anything.

Remove the Background and Keep the Transparency

RMBG.PRO takes a WebP in and gives you a transparent WebP or PNG back, in the browser, with no conversion detour:

• Transparent WebP and transparent PNG output from the same cutout.
• Batch upload for whole catalogues rather than one file at a time.
• Optional custom background colour or image when you need something other than alpha.
• Logo overlay with a 3×3 position grid and size control.
• 1 credit per image, with 10 free credits at signup.
• A REST endpoint at POST https://api.rmbg.pro/v1.0.1/remove_background for pipelines.

Frequently Asked Questions