Free webp to jpg
Image MIME Reference
FPX

FlashPix

image/vnd.fpx
VS

PiCture eXchange

image/x-pcx
PCX

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

Equal browser support

Feature Support

Feature FPX PCX
Transparency (Alpha) Yes ✕ No
Animation Support ✕ No ✕ No
Progressive Loading ✕ No ✕ No
HDR Support ✕ No ✕ No
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 →
PiCture eXchange
image/x-pcx
Extension
.pcx
Container ZSoft Proprietary Header (128 bytes)
Compression Run-Length Encoding (RLE)
Algorithm
ZSoft RLE
Color Depth 1-bit (Monochrome), 4-bit (16 colors), 8-bit (256 colors), 24-bit (True Color)
Developed by ZSoft Corporation
Released 1985
Magic Bytes
0A (followed by version, e.g., 0A 05 01 08)
Full PCX reference →

Browser Support Comparison

Browser FPX PCX
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
PCX

PCX Strengths

  • Incredibly simple RLE algorithm makes it very fast to decode, which was historically vital for early 3D video game engines
  • Retains crisp, lossless pixel data suitable for pixel art and interface assets
  • Well-documented and highly supported by older desktop publishing and image editing software
Limitations
  • Extremely inefficient compression by modern standards, producing large file sizes compared to PNG
  • Lacks modern imaging features such as alpha channel transparency, EXIF metadata, and color profiles
  • Zero support in web browsers; must be converted to PNG for web use

When to choose which format

FPX
Use FPX when…
  • Legacy Digital Photography
  • Kodak Picture CDs (Historical)
  • Early High-Resolution Image Viewers
PCX
Use PCX when…
  • MS-DOS and Early Windows Graphics
  • 1990s Video Game Assets (Textures, UI)
  • Retro Computing Archival
Share this comparison