Free webp to jpg
Image MIME Reference
HTJ2K-Codestream

High-Throughput JPEG 2000 Codestream

image/jphc
VS

Kodak KDC Raw Image

image/x-kodak-kdc
Kodak-KDC

A complete technical comparison of High-Throughput JPEG 2000 Codestream 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-Codestream Kodak-KDC
Transparency (Alpha) Yes ✕ No
Animation Support ✕ No ✕ No
Progressive Loading Yes ✕ No
HDR Support Yes Yes
EXIF Metadata ✕ No Yes
ICC Color Profile ✕ No Yes
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
Full HTJ2K-Codestream 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-Codestream Kodak-KDC
Chrome Chrome
Firefox Firefox
Safari Safari
Edge Edge
IE IE (Legacy)
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
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-Codestream
Use HTJ2K-Codestream when…
  • Medical Imaging Pipelines
  • Geospatial Data Streaming
  • Digital Cinema
  • Embedded Systems
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