PNG vs WebP vs JPEG after background removal

PNG for transparent cutouts

PNG supports an alpha channel, so it can store the soft transparency around a removed subject. bgcut uses PNG as the default output in its browser and CLI workflows.

PNG is a safe choice when the result will move between editors, design tools, browsers, or other systems and preserving transparency matters more than minimizing the file size.

A transparent pixel is still a pixel with color channels plus alpha. Applications can handle the hidden color channels differently around edges, which is one reason to inspect the final result in the destination tool when edge quality matters.

WebP when you want transparency in another format

WebP supports alpha transparency and can be useful for web delivery or pipelines that already use WebP assets.

bgcut's WebP output is lossless. That keeps the format choice from adding lossy compression artifacts to the cutout.

Use WebP only when the systems that consume the output accept it. A technically smaller or newer format is not useful if the next tool in the workflow requires PNG.

JPEG needs an opaque background

JPEG does not have an alpha channel. A background-removed image cannot stay transparent when it is encoded as JPEG.

bgcut uses a white background for JPG output. That can be useful for catalogs or systems that require JPEG, but it is a different result from a transparent cutout.

If you may need to place the subject on another background later, keep a PNG or WebP transparent master and make a JPEG copy only for the destination that requires it.

A simple format rule

Choose the format based on the next step in the workflow. Do not convert just because one extension is more familiar.

• Choose PNG for a broadly compatible transparent master.
• Choose lossless WebP when your downstream system accepts WebP and you want transparency.
• Choose JPEG only when you want or require an opaque image.