Free webp to jpg
Image MIME Reference
HTJ2K-(JPH)

High-Throughput JPEG 2000 Image

image/jph
VS

Kodak KDC Raw Image

image/x-kodak-kdc
Kodak-KDC

A complete technical comparison of High-Throughput JPEG 2000 Image and Kodak KDC Raw Image — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.

Equal browser support

Feature Support

Feature HTJ2K-(JPH) Kodak-KDC
Transparency (Alpha) Yes ✕ No
Animation Support ✕ No ✕ No
Progressive Loading Yes ✕ No
HDR Support Yes Yes
EXIF Metadata Yes Yes
ICC Color Profile Yes Yes
High-Throughput JPEG 2000 Image
image/jph
Extension
.jph
Container JPH (ISO/IEC 15444-15)
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
00 00 00 0C 6A 50 20 20 0D 0A 87 0A ... 66 74 79 70 6A 70 68 20
Full HTJ2K-(JPH) reference →
Kodak KDC Raw Image
image/x-kodak-kdc
Extension
.kdc
Container TIFF/EP
Compression Uncompressed / Proprietary Lossless
Algorithm
NoneLossless JPEG (ITU-T81)Proprietary Kodak Compression
Color Depth 10-bit, 12-bit (Per Channel)
Developed by Eastman Kodak Company
Released 1995
Magic Bytes
49 49 2A 00 or 4D 4D 00 2A
Full Kodak-KDC reference →

Browser Support Comparison

Browser HTJ2K-(JPH) Kodak-KDC
Chrome Chrome
Firefox Firefox
Safari Safari
Edge Edge
IE IE (Legacy)
HTJ2K-(JPH)

HTJ2K-(JPH) Strengths

  • Delivers orders of magnitude faster encoding and decoding than standard JPEG 2000 by utilizing a new, parallelizable block coder
  • Supports mathematically lossless and lossy compression within the same codestream architecture
  • Allows for resolution scalability, progressive decoding, and region-of-interest extraction without needing to decode the entire image
Limitations
  • Zero native web browser support, requiring specialized libraries, API conversions, or WebAssembly (like OpenJPH.js) for web deployment
  • Lack of broad consumer awareness, keeping it confined to professional, medical, and scientific workflows
  • Requires more advanced software ecosystems to decode than ubiquitous formats like JPEG or WebP
Kodak-KDC

Kodak-KDC Strengths

  • Preserves original raw sensor data, allowing modern demosaicing software to extract significantly more detail and dynamic range than the camera's built-in JPEG engine could at the time
  • Utilizes the standard TIFF container structure, ensuring broad compatibility with open-source decoding libraries (like LibRaw)
Limitations
  • Completely obsolete proprietary format tied to a defunct line of consumer digital cameras
  • Subject to widespread misidentification by automated MIME detection libraries due to structural similarities with standard TIFFs
  • Cannot be natively viewed in web browsers or standard operating system image viewers without specialized decoders

When to choose which format

HTJ2K-(JPH)
Use HTJ2K-(JPH) when…
  • Medical Imaging (DICOM)
  • Geospatial Data
  • Digital Cinema
  • Professional Archiving
Kodak-KDC
Use Kodak-KDC when…
  • Vintage Digital Photography Archival
  • Kodak DC and EasyShare P-Series Raw Post-Processing
  • Historical Imaging Research
Share this comparison