Free webp to jpg
EN
Image MIME Reference
FPX

FlashPix

image/vnd.fpx
VS

Portable Pixmap

image/x-portable-pixmap
PPM

A complete technical comparison of FlashPix and Portable Pixmap — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.

Equal browser support

Feature Support

Feature FPX PPM
Transparency (Alpha) Yes ✕ No
Animation Support ✕ No ✕ No
Progressive Loading ✕ No ✕ No
HDR Support ✕ No Yes
EXIF Metadata Yes ✕ No
ICC Color Profile Yes ✕ No
FlashPix
image/vnd.fpx
Extension
.fpx
Container Microsoft OLE Structured Storage (COM)
Compression JPEG (Lossy) / Uncompressed / Single-color (Solid)
Algorithm
JPEGNone
Color Depth 8-bit (Grayscale/Indexed), 24-bit (RGB), 32-bit (CMYK/RGBA)
Developed by Eastman Kodak, Microsoft, Hewlett-Packard, Live Picture
Released 1996
Magic Bytes
D0 CF 11 E0 A1 B1 1A E1
Full FPX reference →
Portable Pixmap
image/x-portable-pixmap
Extension
.ppm
Container Netpbm
Compression Uncompressed
Algorithm
None
Color Depth 24-bit (RGB), 48-bit (RGB High Color)
Developed by Jef Poskanzer (Netpbm Project)
Released 1988
Magic Bytes
50 33 (ASCII) or 50 36 (Binary)
Full PPM reference →

Browser Support Comparison

Browser FPX PPM
Chrome Chrome
✕ ✕
Firefox Firefox
✕ ✕
Safari Safari
✕ ✕
Edge Edge
✕ ✕
IE IE (Legacy)
✕ ✕
FPX

FPX Strengths

  • Allowed early, low-RAM computers to view and edit massive, high-resolution digital photos instantly by only loading the needed tiles and resolutions
  • Pioneered the multi-resolution pyramid and tiling concepts heavily used today in modern deep-zoom and web mapping applications (like Google Maps)
Limitations
  • Completely obsolete and unsupported by modern web browsers or operating systems
  • Uses the complex, proprietary Microsoft OLE container format, making it incredibly difficult to parse or extract data from without dedicated legacy libraries
  • Prone to being misidentified by MIME sniffers as an old Microsoft Office document
PPM

PPM Strengths

  • Absolute structural simplicity allows parsers and renderers (such as custom raytracers) to write directly to the format with virtually no overhead or external libraries
  • Supports 16-bit per channel (48-bit total) precision, preserving deep color accuracy before converting to final delivery formats
  • ASCII encoding ('P3') allows manual editing and visual inspection of RGB values directly within a text editor
Limitations
  • Zero compression results in astronomical file sizes, making it entirely impractical for web delivery or consumer storage
  • Does not natively support an alpha channel for transparency (this is handled by the newer PAM extension format within the Netpbm suite)
  • Lacks support for modern metadata standards like EXIF, XMP, or embedded ICC color profiles

When to choose which format

FPX
Use FPX when…
  • Legacy Digital Photography
  • Kodak Picture CDs (Historical)
  • Early High-Resolution Image Viewers
PPM
Use PPM when…
  • Intermediary Format for Image Format Conversion
  • Academic Computer Graphics and Raytracing Output
  • Unix/Linux Command-Line Image Pipelines

More comparisons

FPX vs ACES → PPM vs ACES → FPX vs APNG → PPM vs APNG → FPX vs AVCI → PPM vs AVCI → FPX vs AVCS → PPM vs AVCS → FPX vs AVIF → PPM vs AVIF → All comparisons →
Share this comparison