The Complete Guide to Image Formats in 2026

JPEG, PNG, WebP, AVIF, GIF, SVG, HEIC, TIFF, BMP, and JPEG XL, covered in one place. Real file size data, where each format wins, where it loses, and exactly which converter to use.

Daniel Osei·June 22, 2026·16 min read

There are ten image formats you will actually encounter in 2026, and most guides either drown you in codec history or oversimplify to "just use WebP." Neither approach helps when you are staring at a HEIC file that will not open, a TIFF from a scanner, or trying to decide whether that AVIF migration is actually worth the encoding overhead.

This guide covers all ten formats in active use today: JPEG, PNG, WebP, AVIF, GIF, SVG, HEIC, TIFF, BMP, and JPEG XL. For each one you will get what it actually is, the real file size numbers, where it wins, where it loses, and a direct link to convert it whenever you need to. If you only want the short answer, skip to the decision table near the end. If you want to understand why that table looks the way it does, read straight through.

The Two Fundamentally Different Ways Images Are Stored

Before comparing individual formats, there is one distinction that explains almost every decision in this guide: raster versus vector.

Raster images store color information for every individual pixel. A 1920x1080 raster image holds data for 2,073,600 separate pixels. The quality is fixed at capture: scale a raster image up and the individual pixels become visible as blur or blockiness. JPEG, PNG, WebP, AVIF, GIF, HEIC, TIFF, and BMP are all raster formats.

Vector images store geometric instructions instead: draw a circle here, fill it with this color, apply this gradient there. Because the image is described mathematically rather than pixel by pixel, it scales to any size with zero quality loss. SVG is the vector format in common web use.

This single distinction tells you immediately that a photograph can never be a vector format (cameras capture pixels, not shapes) and that a logo almost always should be vector when possible, because logos are simple enough to describe as shapes and benefit enormously from scaling cleanly across every screen size and resolution.

The second distinction that matters across every format below is lossy versus lossless compression. Lossless compression rearranges the data without throwing any of it away: save a lossless file, reopen it, save it again, and the pixels remain bit-for-bit identical forever. Lossy compression deliberately discards information the encoder judges you are unlikely to notice, which is how it achieves much smaller files. The tradeoff is permanent: each time you re-save a lossy file from a lossy source, you lose a little more. The guide on lossy versus lossless compression covers this mechanism in more depth if you want the full technical picture.

JPEG: The Universal Workhorse

JPEG was standardized in 1992 and remains the most widely used lossy format on the internet more than three decades later. Every browser, every operating system, every camera, every printer, and nearly every piece of software ever written can open a JPEG without question.

The compression algorithm divides an image into fixed 8x8 pixel blocks and discards detail the human eye is least likely to notice within each block. At quality 80, a JPEG photograph is typically indistinguishable from the source while weighing 5 to 10 times less. Push below quality 50 and the fixed block structure becomes visible as blocky artifacts, particularly around sharp edges and in smooth gradients like skies.

JPEG cannot do transparency at all. It has no alpha channel, so any area you want transparent gets filled with a solid color instead, usually white. It is also strictly 8-bit per color channel, meaning 256 shades of red, green, and blue each, which is fine for a finished photo on a normal screen but becomes a limitation in heavy editing.

Use JPEG for photographs going anywhere compatibility cannot be assumed: email attachments, document uploads, government portals, job applications, and as the universal fallback inside a <picture> element. The JPG to WebP and JPG to AVIF converters move you forward to a smaller modern format when compatibility is not the constraint. The guide on compressing images for job applications and compressing passport photos online both cover specific contexts where JPEG remains a hard requirement.

PNG: Lossless Precision for Graphics

PNG arrived in 1996 as a patent-free replacement for GIF and was built around one uncompromising goal: every pixel you save comes back exactly as you saved it, every single time, with full alpha channel transparency support.

That reliability comes at a real file size cost for photographic content. A photograph that is 300KB as JPEG can easily be 2 to 3MB as PNG, because storing every pixel losslessly on complex, varied content requires far more data than a lossy encoder needs. PNG is the wrong format for photographs, full stop, and the right format for anything where pixel-perfect accuracy matters more than file size: screenshots with text, logos with hard edges, UI graphics, and diagrams.

WebP lossless now beats PNG on file size in the majority of cases (more on the exact numbers in the WebP section below), which has made PNG's remaining advantage mostly about universal compatibility rather than any technical edge. If you are choosing a format for a new graphic today, WebP lossless usually wins. If you need a format guaranteed to open in absolutely everything, including older software that has never heard of WebP, PNG remains the safer bet.

The PNG to WebP converter and PNG to JPG converter handle the most common conversions away from PNG. The full PNG versus WebP comparison covers the file size data and the transparency handling differences in detail if this is the specific decision in front of you.

WebP: The Practical Default for the Web

Google released WebP in 2010, building on the VP8 video codec's predictive coding techniques to beat both JPEG and PNG at their own jobs in a single format. WebP supports lossy compression (the JPEG replacement), lossless compression (the PNG replacement), transparency, and animation, all in one container.

The numbers are well established at this point. Lossy WebP files run 25 to 35% smaller than equivalent JPEG at the same visual quality. Lossless WebP files run roughly 26% smaller than equivalent PNG according to Google's own published study, which tested across a corpus of 12,000 real web images and found gains as high as 42% over standard PNG compression tools.

Browser support sits above 97% globally as of 2026, covering Chrome, Firefox, Safari (since version 14), Edge, and Opera. Most modern CMS platforms, including WordPress 5.8 and newer, Shopify, and Squarespace, convert uploaded images to WebP automatically. For nearly all web content in 2026, WebP needs no fallback for practical purposes.

For full coverage of the WebP-versus-JPEG decision specifically, the WebP vs JPG comparison goes deep on where each format wins. For the WebP-versus-PNG decision, the PNG vs WebP comparison covers transparency handling in detail. The JPG to WebP and PNG to WebP converters handle the actual conversion in your browser with nothing uploaded to a server.

AVIF: The Compression Leader

AVIF (AV1 Image File Format) is derived from the AV1 video codec, developed by the Alliance for Open Media, a consortium including Google, Apple, Netflix, Meta, Microsoft, and Amazon. It is royalty-free and represents the current ceiling of practical web image compression.

At equivalent visual quality, independent benchmarks consistently place AVIF 40 to 55% smaller than JPEG and roughly 20% smaller than WebP. A 500KB JPEG photograph typically compresses to around 250KB as AVIF with no visible quality difference at normal viewing sizes. A 2026 benchmark testing ten formats across 1,000 images found AVIF averaging 142KB at quality 85 against JPEG's 245KB at the same setting, while scoring higher on SSIM, a perceptual quality metric, meaning AVIF was not just smaller but measurably closer to the source image in that test.

AVIF also supports HDR, wide color gamut, and 10 to 12 bit color depth, none of which JPEG or standard WebP can do. The tradeoff that keeps AVIF from being an unconditional win is encoding speed: AVIF takes 5 to 20 times longer to encode than JPEG or WebP. For build-time pipelines where you encode once and serve many times, this barely matters. For on-the-fly, per-request encoding, it adds real latency to the first request for each variant.

Browser support reached roughly 93 to 95% globally as of early 2026, covering Chrome 85+, Firefox 93+, Safari 16+, and Edge 121+. The JPG to AVIF and PNG to AVIF converters run the conversion in your browser. The full AVIF versus JPG comparison and the broader WebP versus AVIF comparison cover the decision in more depth than fits here.

GIF: Obsolete for Photos, Surviving for Memes

GIF dates to 1987 and is limited to a 256-color palette, a constraint that makes it technically unsuitable for photographic content. Run any real photograph through GIF's color reduction and you get visible banding and posterization. A 2026 benchmark scoring image quality on the SSIM scale found GIF at just 0.82 against JPEG's 0.94, AVIF's 0.96, and WebP's 0.95, confirming numerically what is visually obvious: GIF degrades photographic content far more than any other format in common use.

GIF's only remaining genuine use case is animation, and even there it has been outperformed for over a decade. Animated WebP produces the same visual effect at roughly 10 times smaller file size. Short looping video (an autoplaying, muted, looped <video> element) is smaller again, often by a further order of magnitude. The honest reason GIF persists at all in 2026 is compatibility: certain messaging apps, some email clients, and internet culture itself (memes, reaction images) still expect the format specifically. If your destination genuinely requires animated GIF, that is the only good reason left to produce one.

SVG: The Right Format for Almost Every Logo

SVG (Scalable Vector Graphics) is fundamentally different from every other format in this guide because it is not raster at all. It stores an image as XML markup describing shapes, paths, and colors rather than pixel values, which gives it two properties no raster format can match: infinite scaling with zero quality loss, and direct accessibility to CSS and JavaScript, meaning individual elements inside an SVG can be styled, animated, or made interactive.

File sizes are typically tiny. A simple SVG icon commonly runs 1 to 10KB. The equivalent PNG icon prepared at 2x resolution for high-DPI screens can easily be 8 to 40KB for the same visual result, and unlike the PNG, the SVG never looks soft on a higher resolution display than the one it was designed for.

SVG is the right choice whenever a graphic was created as vectors in the first place: logos, icons, simple illustrations, charts, and diagrams. It is the wrong choice for photographs, which cannot be meaningfully expressed as geometric shapes. Never use JPEG-style lossy compression logic on logos containing sharp edges or text; the blocky DCT artifacts that are invisible on a photograph become obvious and ugly on a clean vector shape rendered as a raster. The SVG to PNG and SVG to WebP converters handle rasterizing a vector source when you need a raster output for a specific context, such as an email or a platform that does not accept SVG uploads.

HEIC: Excellent Inside Apple's Ecosystem, Friction Everywhere Else

HEIC (High Efficiency Image Container) became the default photo format on iPhone with iOS 11 in September 2017. It uses HEVC, the H.265 video codec, to compress still images, achieving files roughly 40 to 50% smaller than equivalent JPEG at the same visual quality. It also supports 10 to 16-bit color depth, native transparency, and the ability to store multiple images in a single file, which is exactly the mechanism behind Live Photos.

The problem is everything outside Apple's own devices. Windows does not open HEIC natively without installing a separate codec extension from the Microsoft Store, and even then, performance and reliability vary. Many client gallery platforms, print labs, government portals, and older desktop software either reject HEIC outright or fail silently, skipping the file during a batch operation without warning. Late 2025 and early 2026 brought HEIC support to some mid-range and premium Android devices, narrowing the gap slightly, but JPEG remains the format every collaborative workflow defaults to specifically because failures with HEIC tend to be silent and confusing rather than a clear error message.

If you are sending or uploading a HEIC file anywhere outside Apple's ecosystem, convert it first. The HEIC to JPG converter handles this in your browser in about ten seconds, and the complete guide on converting HEIC to JPG covers the underlying compatibility problem and several other practical angles, including how to stop your iPhone from saving HEIC in the first place.

TIFF: The Archival and Print Standard

TIFF (Tagged Image File Format) dates to 1986 and remains, in 2026, the preferred format for professional photography masters, scanned document archives, and print production. It supports lossless compression, layers, multiple pages within a single file, extensive embedded metadata, and high bit depth, all properties that matter enormously for long-term archival and print accuracy and barely at all for casual web use.

The tradeoff is size. TIFF files tend to be large, sometimes dramatically so, because the format favors complete fidelity and rich metadata over compactness. A TIFF saved in 2007 will be bit-for-bit identical when opened in 2026, which is precisely the guarantee an archive needs and precisely the property a website does not need to pay the file size cost for.

The practical rule that shows up consistently across professional photography workflows: capture in RAW or JPEG, maintain your editing master in TIFF, and deliver the final version in JPEG, WebP, or AVIF depending on the destination. TIFF belongs in the middle of that pipeline, not at either end facing the public. The TIFF to JPG and TIFF to WebP converters handle moving a TIFF master toward a web-appropriate delivery format.

BMP: A Legacy Format With No Modern Advantage

BMP (Bitmap) was introduced by Microsoft with Windows 1.0 in 1985 and stores image data largely uncompressed. Every pixel's red, green, and blue values are stored directly with essentially no encoding cleverness applied, which produces extremely large files for very little benefit in 2026.

There is genuinely no modern workflow where BMP outperforms an available alternative. For archival accuracy, TIFF does everything BMP does while supporting actual lossless compression to keep file sizes reasonable. For web use, PNG or WebP cover the same lossless need at a fraction of the size. BMP survives almost entirely in legacy Windows applications, certain scientific and industrial imaging contexts where raw, completely unprocessed pixel data is specifically required by an older system, and old scanner software that has never been updated. If you receive a BMP file today, the practical move is converting it immediately rather than working with it directly. The BMP to PNG and BMP to JPG converters handle this in seconds.

JPEG XL: Technically Excellent, Still Waiting on Adoption

JPEG XL is the most technically ambitious format in this guide and the one with the most complicated adoption story. Developed by the same standards body behind the original JPEG, it claims compression up to 55% smaller than JPEG and up to 25% smaller than AVIF at equivalent quality, while supporting both lossy and lossless modes, transparency, animation, true progressive rendering (a meaningful advantage AVIF specifically lacks, since AVIF files must download completely before displaying anything), and lossless recompression of existing JPEG files into a smaller JPEG XL container that can be losslessly converted back to the original JPEG bytes exactly.

The adoption story is genuinely unusual. Google shipped early Chrome support, then removed it in 2022, a decision that drew criticism from developers and was never fully explained, with speculation pointing toward Google's own investment in WebP and AVIF as competing formats it already controlled. Apple's Safari has supported JPEG XL since 2024. Reports through late 2025 and into 2026 suggest Chrome may be reconsidering reinstating support, which would be the development that finally makes JPEG XL viable as a primary production format rather than an experimental one.

As things stand today, native browser support is limited to Safari, with partial support in some Firefox and Chromium builds and in Linux desktop environments running KDE Plasma or GNOME. That is not broad enough to serve as your only production format in 2026. JPEG XL is worth watching closely and worth testing in non-critical contexts, but anyone building a production image pipeline today should treat it as promising future infrastructure rather than something to depend on for visitors right now.

The Decision Table

Pulling every format into one practical reference:

For photographs displayed on a web page: AVIF first, WebP second, JPEG as the final fallback, served through a <picture> element so each visitor's browser picks the smallest format it can render.

For logos and icons: SVG whenever the source is vector-based, which covers the large majority of logos. WebP lossless or PNG when a raster format is unavoidable.

For screenshots and graphics with sharp text: PNG or WebP lossless, never standard lossy JPEG, since DCT-based compression visibly blurs sharp edges and small text.

For animated content: WebP animated or a looping muted video element. Reach for GIF only when a specific destination explicitly requires it.

For iPhone photos leaving Apple's ecosystem: convert HEIC to JPEG before sharing, uploading, or sending to anyone whose system you do not control.

For professional editing masters and archival storage: TIFF, kept separate from whatever lighter format you ultimately deliver to the web or to a client.

For anything you encounter in BMP format: convert it immediately. There is no reason to keep working with it directly.

For email attachments, government portals, and any upload form: JPEG remains the safe universal choice until the receiving system explicitly says otherwise.

Implementing the Recommendation

Serving the right format to each visitor without writing any detection logic comes down to one HTML element:

<picture>
  <source srcset="photo.avif" type="image/avif" />
  <source srcset="photo.webp" type="image/webp" />
  <img src="photo.jpg" alt="Descriptive alt text" width="1200" height="800" />
</picture>

Browsers that support AVIF request it. Browsers that support WebP but not AVIF fall through to it. Everything else falls through to the JPEG. No JavaScript, no server-side user-agent sniffing, and the fallback only costs anything for the small and shrinking share of visitors who actually need it.

Format choice is one input among several in overall image performance, and it works best alongside correct sizing and compression rather than as a substitute for either. The image optimization checklist walks through the complete set of practical steps, and the guide on how image compression affects SEO and page speed covers exactly how format and file size connect to Core Web Vitals and search rankings if you want to understand the business case behind all of this rather than just the technical one.

Every converter referenced throughout this guide runs entirely in your browser using WebAssembly. Nothing is uploaded to a server at any point, which matters whether you are converting a personal photo, a client's product image, or a confidential document scan.

Written by

Daniel Osei

Web Performance Engineer

Daniel has spent 6 years optimizing images and web assets for publishers and e-commerce brands. He writes about image formats, compression techniques, and web performance at ImgTweak.