Image MIME Reference
FPX
FlashPix
image/vnd.fpx
VS
High-Throughput JPEG 2000 Codestream
image/jphc
HTJ2K-Codestream
A complete technical comparison of FlashPix and High-Throughput JPEG 2000 Codestream — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | FPX | HTJ2K-Codestream |
|---|---|---|
| Transparency (Alpha) | Yes | Yes |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | ✕ No | Yes |
| 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
High-Throughput JPEG 2000 Codestream
image/jphc
Extension
.jhc
Container
None (Raw Codestream)
Compression
Lossy / Lossless
Algorithm
High-Throughput JPEG 2000 (HTJ2K)
Color Depth
8-bit, 16-bit, 32-bit, 38-bit
Developed by
Joint Photographic Experts Group (JPEG)
Released
2019
Magic Bytes
FF 4F FF 51
Browser Support Comparison
| Browser | FPX | HTJ2K-Codestream |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
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
HTJ2K-Codestream
HTJ2K-Codestream Strengths
- Extremely fast encoding and decoding capabilities due to the parallelizable block coder
- Minimal file overhead since it lacks container headers and metadata
- Ideal for streaming applications or embedded systems where parsing a full container is unnecessary
Limitations
- Lacks standard metadata support (like EXIF, XMP, or ICC color profiles) since there is no container structure
- Zero native web browser compatibility
- Difficult to distinguish from standard JPEG 2000 codestreams without deeply parsing the internal marker segments
When to choose which format
FPX
Use FPX when…
- Legacy Digital Photography
- Kodak Picture CDs (Historical)
- Early High-Resolution Image Viewers
HTJ2K-Codestream
Use HTJ2K-Codestream when…
- Medical Imaging Pipelines
- Geospatial Data Streaming
- Digital Cinema
- Embedded Systems