Images

PNG to WebP Guide: Keep Transparency and Choose Useful Quality

·

PNG to WebP creates new WebP images from still PNG files in your browser. Choose your files, set quality and an optional maximum side, convert, then compare the results before downloading. Transparent areas remain transparent; rotation and flips can be applied in the same job.

A WebP file can be smaller than its PNG source, but the result depends on the picture, dimensions and quality setting. This tool lets the browser encode WebP using a quality setting and has no explicit lossless switch; lossy encoding can alter image detail. Keep your original PNG when exact pixels, source metadata or an editable master matter.

PNG to WebP

Convert a small sample before a large batch

Choose images or drop up to 20 PNG files into the workspace. Wait for previews to settle, then select Convert to WebP. The initial quality is 90 and Maximum image side is 0, which keeps the source dimensions unless you rotate the image. Each completed result shows a preview, dimensions, source size and output size.

Start with one representative image. Inspect fine text, thin lines, gradients and transparent edges at the intended display size, then download the result separately. A successful conversion prepares a download; it does not replace the source file, save automatically or update an image already published on a website.

  • Keep an original PNG as the comparison reference.
  • Try a quality and size setting on a representative image before applying it to the whole queue.
  • Compare both appearance and the actual output byte count before replacing a website asset.

Google: WebP compression and format capabilitiesweb.dev: Use WebP images

Choose a format for the image and its destination

PNG stores image samples losslessly and supports transparency. WebP supports lossy and lossless encoding. This workspace requests browser-generated WebP with transparency using a quality hint, without an explicit mode selector. Its controls do not expose every feature of the WebP format: there is no animated output, explicit lossless mode, encoder-effort setting or target number of bytes.

WebP is useful when the destination accepts it and the saved bytes justify any visible change. Logos, screenshots and small interface text deserve close inspection because lossy encoding can alter sharp boundaries. A website must also be configured to serve the new file; downloading WebP does not change an existing image URL or create fallback markup.

Choose a format for the image and its destination
NeedPractical choiceCheck before replacing the source
A smaller web image with transparent regionsTry this WebP converterInspect edges and compare actual bytes.
Exact original samples or archival metadataRetain the original PNGThis conversion re-encodes pixels and does not copy source metadata.
AnimationUse a workflow that explicitly supports animationAnimated PNG input is rejected here.
A destination requiring PNG or JPGUse that destination’s required formatRenaming .webp cannot change the encoded format.

W3C: PNG Third EditionGoogle: WebP compression and format capabilitiesweb.dev: Use WebP images

Quality is a tradeoff, not a percentage of original detail

The quality slider runs from 10 to 100 and starts at 90. It supplies a quality hint to the browser encoder. Lower values often reduce output size but can introduce visible artifacts; the exact result depends on image content and browser implementation. A value of 80 does not mean that 80% of the original information is retained or that the file will be 20% smaller.

Quality 100 is not a promise of lossless pixel identity. Compare at a useful display size and keep the original when you cannot accept any pixel changes. This converter returns a WebP even when its output is larger than the PNG. Try a lower quality or smaller dimensions when suitable, or keep the PNG if it is already the better result.

MDN: OffscreenCanvas.convertToBlob()Google: WebP compression and format capabilities

Preserve transparent regions without removing a background

The WebP output can retain fully transparent and partially transparent pixels. An opaque white area remains an opaque white area: conversion does not detect a subject or remove its background. Resizing and lossy color encoding can affect the appearance around edges, so check the result against the background where it will actually be displayed.

The shared settings include a control labeled JPG background. It applies to JPEG output in other workspaces and does not flatten this WebP result. Changing it does not replace transparent pixels with that color. Keep the source PNG if exact color samples, high bit depth or a particular color-management workflow must be preserved.

Google: WebP compression and format capabilitiesW3C: PNG Third EditionMDN: Window.createImageBitmap()

Resize proportionally after choosing rotation and flips

Maximum image side accepts whole numbers from 0 to 12000. Zero keeps dimensions; a positive limit reduces the longer side when needed and preserves proportions, with pixel dimensions rounded to whole numbers. It never enlarges a smaller image. This route has no separate width and height boxes, cropping rectangle or stretch mode.

Rotation offers 0, 90, 180 and 270 degrees clockwise. Horizontal and vertical flips apply after rotation, relative to the rotated image. The maximum side is evaluated using that orientation, so a quarter turn swaps the width and height in the result. One set of settings applies to every image in the queue.

Resize proportionally after choosing rotation and flips
Source and rotationMaximum sideResult dimensions
4000 × 3000, no rotation04000 × 3000
4000 × 3000, no rotation12001200 × 900
4000 × 3000, 90° clockwise1200900 × 1200
600 × 400, 90° clockwise1200400 × 600; no enlargement

MDN: Window.createImageBitmap()

Check the source limits before selecting a resize

Each source must fit both the byte and dimension limits. The tool checks source dimensions before output resizing, so a huge PNG is not accepted simply because you request a small result. Reduce an oversized source in another suitable image editor first, then choose the smaller file. MB here means decimal bytes, not MiB.

Input and encoded-output totals are separate limits. The combined WebP payloads may total at most 100000000 bytes; ZIP packaging adds its own container overhead. These bounds limit work but do not guarantee that every permitted job will finish on every device. The worker has a sixty-second deadline, and available browser memory also matters.

Check the source limits before selecting a resize
LimitMaximumWhat is counted
Selected files20The complete queue for one conversion job.
Bytes per PNG25000000 bytesThe selected source file, including its metadata.
Source dimensions24000000 pixels and 12000 per edgeBoth width × height and each individual side must qualify.
Combined source bytes100000000 bytesAll selected input files together.
Combined encoded output100000000 bytesWebP payloads before ZIP container overhead.

MDN: OffscreenCanvas.convertToBlob()

A thumbnail or filename does not prove the input is eligible

The file picker suggests PNG files, and conversion checks the file contents before decoding. A JPG renamed to .png is still a JPG and is rejected. Shared previews can display other supported still-image formats, so seeing a thumbnail does not mean that this PNG-only converter will accept the file. A damaged file can also pass an initial header check and still fail during browser decoding.

Animated PNG is rejected rather than silently exported as a still frame. The check includes animation-control data beyond the initial header area; even an animation declaration with one frame is outside this tool’s still-image policy. Export a genuine still PNG from an animation editor if a single frame is what you need. This workspace cannot preserve animation timing or combine frames into animated WebP.

W3C: PNG Third EditionMDN: Window.createImageBitmap()

Keep source metadata and image fidelity requirements separate

Conversion decodes the image, draws it to a browser canvas and writes new WebP bytes. Original metadata is not copied into the result. Where supported, orientation information can influence the decoded picture, but that does not preserve the original orientation tag, comments or other source metadata. Keep the PNG when those records are part of your archive.

PNG can carry high-bit-depth samples and color information that a browser canvas workflow does not promise to reproduce exactly. Default color conversion is browser-dependent. Transparency support therefore does not imply archival equivalence, identical hidden colors under transparent pixels, or an unchanged color profile. Compare in the application that will consume the image.

W3C: PNG Third EditionMDN: Window.createImageBitmap()MDN: OffscreenCanvas.convertToBlob()

Organize files before producing the final results

You can move files up or down, sort by filename, reverse their order or remove an item. The result prefix follows the current queue order. Adding accepted files, changing settings or reordering invalidates old results, so convert again before downloading. A selection that would take the queue over 20 files is rejected as a whole; the already selected files remain.

Conversion processes the batch in sequence. If one file fails, the workspace does not expose previously processed images from that job as a partial result. Remove or replace the problem file and retry. Clear files empties the queue and results, but retains global choices such as quality, rotation and maximum side; check those values when starting a new batch.

MDN: OffscreenCanvas.convertToBlob()

Recover from errors without losing the source files

Cancel stops the active conversion worker and keeps the selected source files for another attempt. It does not save a partly finished batch. After a timeout or failure, try fewer images, smaller sources or less demanding output dimensions where appropriate. The sixty-second worker deadline is a limit, not an estimate of how long a particular conversion should take.

Correcting a setting clears an old processing error and invalidates stale results. Removing files clears the rejected-selection warning; clearing the queue also removes its preview-size notice. A preview error is distinct from a final conversion error: once preview work settles, conversion still performs its own validation. Reloading may discard the in-tab selection, so retain the original files.

MDN: OffscreenCanvas.convertToBlob()MDN: Window.createImageBitmap()

Download each image or package the batch as a ZIP

Each result can be downloaded individually. Output names use an ordinal prefix such as 01-, a cleaned version of the original basename and the .webp extension. Characters unsuitable for a filename are replaced and long basenames are shortened. The name does not change which image format is inside the file.

With multiple results, Download all as ZIP creates toolmellow-images.zip containing the encoded WebP files without another image-conversion pass. Related actions can pass results to the image-resizing or image-to-PDF workspace in the same tab. That handoff is temporary local state, not a permanent share link, cloud backup or saved project. Download files you want to keep.

Google: WebP compression and format capabilities

Local conversion still depends on the browser

Selected file bytes are handled by local browser workers, with no file-upload step in the implemented conversion or ZIP path. Loading the page can still involve ordinary asset and analytics requests. Local processing does not mean the whole website makes no network requests, and it does not promise that a fresh page will work offline.

The browser must support the image-decoding and canvas-encoding features used here. If it cannot encode the requested WebP type, the tool rejects an unexpected output type rather than naming a fallback PNG as .webp. Try a browser with the required support or a separate converter. The generic suggestion to choose JPG or PNG refers to an alternative workflow; this page itself has a fixed WebP target.

MDN: OffscreenCanvas.convertToBlob()MDN: Window.createImageBitmap()

Use the failure to choose the next useful action

A smaller output is not the only sign of a useful result. A tiny optimized PNG can grow after conversion, and a much smaller lossy file may blur text or damage an edge you care about. Compare the specific image and destination instead of relying on a format-wide savings percentage.

If a batch fails, isolate one valid still PNG to distinguish a file problem from browser support or memory pressure. Keep errors about file bytes, pixel dimensions and animation separate: reducing quality cannot fix an unsupported source format, and an output resize cannot bypass the source-dimension check.

Use the failure to choose the next useful action
SymptomLikely boundaryNext action
A .png filename is rejectedThe bytes may be another format or damagedExport a fresh still PNG; changing the extension is insufficient.
A small requested output is still rejectedSource dimensions or source bytes exceed a limitReduce the source in another editor before adding it.
No batch results after one bad fileThe job fails as a wholeRemove or replace that item, then convert again.
WebP is larger or looks worseThe size–quality tradeoff did not help this imageTry suitable quality/dimensions or retain the PNG.

W3C: PNG Third EditionMDN: OffscreenCanvas.convertToBlob()

Frequently asked questions

Does PNG to WebP keep transparency?

This route retains transparent and partially transparent regions in WebP. It does not remove an opaque background. Inspect edge appearance after resizing or lossy encoding.

Is quality 100 lossless?

No lossless guarantee is provided. This tool exposes a browser quality hint and no explicit lossless mode. Keep the original PNG when exact pixels matter.

Why can my WebP be larger than my PNG?

The encoded size depends on the image, dimensions, quality and browser. This converter returns WebP even when it is larger; compare the displayed sizes and retain the PNG when it is better.

Can I convert an animated PNG?

No. PNG animation-control data is rejected, including a declaration of one frame. Export a genuine still frame first, or use an animation-capable workflow.

Can I resize an oversized source here to get under the limit?

Source byte and dimension limits apply before resizing. First reduce an oversized PNG in another suitable editor, then add the smaller source.

How many files and bytes can I select?

Choose up to 20 PNG files, each at most 25000000 bytes, with at most 100000000 source bytes together. Each source must also fit 24000000 pixels and 12000 pixels per edge. Encoded output has a separate 100000000-byte total cap.

Does Maximum image side 0 produce a zero-sized image?

No. Zero means keep the original dimensions. A positive maximum reduces larger images proportionally without enlarging smaller ones; a quarter rotation swaps width and height.

Does JPG background change the transparent area in WebP?

No. That shared control is used for JPEG output. The fixed WebP output here retains transparency and does not use the chosen background color.

Will my source metadata be preserved?

Original metadata is not copied. Orientation may be applied during decoding, which is different from retaining the original tag. Keep source files for metadata, exact samples or archival color requirements.

Does Clear files reset quality and rotation?

No. It clears the selected files and results while retaining global settings. Check quality, rotation, flips and maximum side before a new batch.

Are image bytes uploaded to convert them?

The implemented conversion and ZIP paths handle file bytes locally in your browser. The website can still request assets and analytics; this is not a claim that the page has no network activity.

Will a downloaded WebP automatically replace my website image?

No. Upload or deploy it through your own website workflow, update the relevant asset reference and confirm that the intended file is served. A local download alone changes no published page.

Sources and further reading

Put it into practice.

Related guides