Free webp to jpg
EN
Image MIME Reference
FLIF

Free Lossless Image Format

image/flif
VS

Portable Graymap

image/x-portable-graymap
PGM

A complete technical comparison of Free Lossless Image Format and Portable Graymap — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.

Equal browser support

Feature Support

Feature FLIF PGM
Transparency (Alpha) Yes ✕ No
Animation Support Yes ✕ No
Progressive Loading Yes ✕ No
HDR Support Yes Yes
EXIF Metadata Yes ✕ No
ICC Color Profile Yes ✕ No
Free Lossless Image Format
image/flif
Extension
.flif
Container FLIF Bitstream
Compression Lossless (MANIAC Entropy Coding)
Algorithm
MANIAC (Meta-Adaptive Near-zero Integer Arithmetic Coding)
Color Depth 1-bit to 16-bit (Per Channel), Grayscale, RGB, RGBA, CMYK
Developed by Jon Sneyers and Pieter Wuille (Cloudinary)
Released 2015
Magic Bytes
46 4C 49 46
Full FLIF reference →
Portable Graymap
image/x-portable-graymap
Extension
.pgm
Container Netpbm
Compression Uncompressed
Algorithm
None
Color Depth 8-bit (Grayscale), 16-bit (Grayscale)
Developed by Jef Poskanzer (Netpbm Project)
Released 1988
Magic Bytes
50 32 (ASCII) or 50 35 (Binary)
Full PGM reference →

Browser Support Comparison

Browser FLIF PGM
Chrome Chrome
✕ ✕
Firefox Firefox
✕ ✕
Safari Safari
✕ ✕
Edge Edge
✕ ✕
IE IE (Legacy)
✕ ✕
FLIF

FLIF Strengths

  • Achieves some of the highest lossless compression ratios ever developed for raster images
  • Incredible progressive decoding allows an image to be highly recognizable even after only 5% of the file has been downloaded
  • Supports animations and complex alpha channels losslessly
Limitations
  • Officially abandoned in favor of JPEG XL
  • Zero native support in web browsers or standard operating system previewers
  • Encoding speed can be significantly slower than standard PNG or WebP compression
PGM

PGM Strengths

  • Extremely simple format allows custom parsers to be written from scratch in minimal time
  • Supports 16-bit precision, making it highly valuable for scientific, medical, and height-map data where 8-bit precision is insufficient
  • ASCII encoding ('P2') allows manual editing and visual inspection of pixel values directly within a text editor
Limitations
  • Strictly limited to grayscale; cannot display color
  • Lack of compression results in massive file sizes, making it entirely impractical for web delivery or consumer storage
  • Does not support alpha transparency or modern metadata structures

When to choose which format

FLIF
Use FLIF when…
  • Archival of Uncompressed Image Assets
  • Bandwidth-Constrained Progressive Image Loading (Historical)
  • Medical and Scientific Imaging Storage
PGM
Use PGM when…
  • Computer Vision and Machine Learning Pre-processing
  • Scientific and Medical Image Processing
  • Unix/Linux Command-Line Image Pipelines

More comparisons

FLIF vs ACES → PGM vs ACES → FLIF vs APNG → PGM vs APNG → FLIF vs AVCI → PGM vs AVCI → FLIF vs AVCS → PGM vs AVCS → FLIF vs AVIF → PGM vs AVIF → All comparisons →
Share this comparison