Image format feature comparison for JPG, PNG, WebP, and AVIF
Selecting an output format balances file size, visual fidelity, and compatibility when you convert photos online or prepare web graphics. Each option under Convert to targets a specific publishing workflow, from email attachments to modern web delivery.
Lossy photo compression with JPG, WebP, and AVIF
Lossy encoders discard subtle color variations that human vision rarely notices, shrinking camera photos by 70% or more compared to raw bitmaps. JPG works in virtually every operating system, printer kiosk, and legacy CMS without extra codecs.
WebP and AVIF achieve tighter compression at comparable visual quality while supporting semi-transparent edges. If you only need to produce legacy JPG files from AVIF photos, that dedicated tool skips extra format toggles.
Lossless PNG preservation and alpha transparency
According to the W3C PNG Third Edition Specification, PNG stores RGB or RGBA pixel data using lossless Deflate compression. Text overlays, UI screenshots, and diagrams stay razor-sharp without mosquito noise around high-contrast edges.
Because PNG retains every pixel verbatim, photographic exports grow much larger than JPG or WebP equivalents. Use PNG when editing assets further or when an app rejects lossy artifacts.
| Output format | Compression type | Alpha transparency | Typical best use case | Browser encoding support |
|---|---|---|---|---|
| JPG | Lossy | No (uses Background fill) | Everyday photos and email attachments | Universal across all browsers |
| PNG | Lossless | Yes (full 8-bit alpha) | Screenshots, UI icons, and sharp text | Universal across all browsers |
| WebP | Lossy or lossless | Yes | Modern websites and fast page loads | Supported in modern browsers |
| AVIF | Lossy (AV1-based) | Yes | Smallest web payloads and HDR pipelines | Chrome and Firefox (varies in Safari) |
Why is AVIF encoding disabled in some browsers?
Browser engines expose different native encoders through the canvas API, so AVIF export availability depends on your active browser rather than the website itself. When the converter initializes, it runs an internal canEncode probe to verify whether image/avif produces a valid binary blob.
Browser capability checks with HTMLCanvasElement.toBlob
Per the MDN HTMLCanvasElement.toBlob() documentation, browsers return null or fall back to image/png when asked to encode an unsupported MIME type. Checking the returned blob type at startup prevents silent mislabeled downloads.
When canEncode("image/avif") returns false, the AVIF radio button appears dimmed and unclickable with a short browser notice underneath. Chrome and Firefox pass this probe natively on desktop, whereas WebKit builds often omit the AVIF encoder.
Automatic fallback from AVIF to WebP or PNG
If a browser loses encoding support mid-session, resolveOutputType steps down safely from AVIF to WebP, or to PNG when WebP is unavailable. File extensions update automatically via EXTENSIONS so a PNG fallback never ships with a .avif filename.
When you need lossless archival copies from modern web formats instead of lossy transcoding, you can convert WebP images to lossless PNG while keeping transparency in one dedicated pass.
Managing transparency fills, quality presets, and batch ZIPs
Export controls adapt dynamically based on the format selected under Convert to. Switching from PNG to JPG reveals matte options, while picking any lossy format unlocks the Quality selector.
Replacing transparent pixels with White, Black, or custom matte
Because JPEG lacks an alpha channel, semi-transparent PNG logos or WebP stickers turn black if painted onto an uninitialized canvas. The Background fill control paints a solid backdrop beneath the source image before encoding.
Click White (#ffffff) for document embeds, Black (#000000) for dark-mode previews, or use the color swatch input to match a brand hex code. Under the IETF RFC 9649 WebP Image Format, WebP preserves alpha natively, so switching to WebP keeps transparent cutouts intact without any matte.
Quality presets from Smaller file (0.75) to Maximum (0.97)
The Quality dropdown maps directly to three encoder ratios: Smaller file (0.75), High (0.9 default), and Maximum (0.97). PNG ignores this control because Deflate compression is always lossless.
Tip: Start with the default High (0.9) setting for photos and drop to Smaller file (0.75) only when targeting strict upload caps. If you want to shrink files further without changing formats, run them through Compress image afterward.
Adding two or more files switches the output panel automatically from a direct file download to a single .zip archive. Each file keeps its original base name paired with the new format extension.
Convert image formats in browser with local privacy
Modern cameras and design tools produce container formats that standard HTML <img> elements cannot always decode directly. Built-in in-browser image converter privacy keeps every byte inside your local tab without touching an external server.
Self-hosted HEIC decoding and SVG script sanitization
When a browser fails to decode an iPhone .heic or .heif photo natively, decodeImage inspects the ISOBMFF ftyp header for Apple HEIC brands (heic, heix, hevc, mif1). It then loads a self-hosted heic-net WebAssembly decoder capped at 64 megapixels (64,000,000 pixels).
Vector .svg files (including extensionless XML payloads up to 10 MiB) pass through createSafeSvgBlobUrl before rasterization, stripping embedded scripts and unsafe event handlers. If you need custom pixel scaling (1x to 8x) for icons or logos, open the SVG to PNG rasterizer before converting.
EXIF orientation correction and 4,096-pixel canvas caps
Photos taken on portrait phones often store rotated pixel buffers alongside an EXIF orientation tag. Calling createImageBitmap with imageOrientation: "from-image" rotates pixels upright before drawing, preventing sideways exports.
As defined in the AOMedia AV1 Image File Format (AVIF) specification, high-resolution cameras and ISOBMFF containers can exceed mobile browser memory limits. To prevent WebKit canvas crashes, clampCanvasSize caps outputs at 4,096 px per side and 16,777,216 total pixels, scaling oversized inputs proportionally.