Free webp to jpg
Image MIME Reference
CGM

Computer Graphics Metafile

image/cgm
VS

High-Throughput JPEG 2000 Codestream

image/jphc
HTJ2K-Codestream

A complete technical comparison of Computer Graphics Metafile 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 CGM HTJ2K-Codestream
Transparency (Alpha) Yes Yes
Animation Support ✕ No ✕ No
Progressive Loading ✕ No Yes
HDR Support ✕ No Yes
EXIF Metadata ✕ No ✕ No
ICC Color Profile Yes ✕ No
Computer Graphics Metafile
image/cgm
Extension
.cgm
Container CGM
Compression Uncompressed / Binary / Character / Clear Text
Algorithm
Deflate (in some WebCGM profiles)
Color Depth 8-bit, 16-bit, 24-bit, 32-bit
Developed by ISO / IEC
Released 1987
Magic Bytes
00 20 (Binary) / 42 45 47 49 4E 20 4D 45 54 41 46 49 4C 45 (Clear Text)
Full CGM reference →
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 →

Browser Support Comparison

Browser CGM HTJ2K-Codestream
Chrome Chrome
Firefox Firefox
Safari Safari
Edge Edge
IE IE (Legacy)
CGM

CGM Strengths

  • Strictly standardized by ISO, ensuring long-term archiving and cross-platform compatibility in engineering
  • Excellent support for rich metadata, hyperlinks, and technical hotspots via the WebCGM profile
  • Can store complex 2D geometry, rasters, and text in a single lightweight file
Limitations
  • Multiple encoding schemes (Binary, Character, Clear Text) make parser development difficult
  • Zero native support in modern web browsers without third-party plugins
  • Largely replaced by SVG for general-purpose 2D vector graphics on the web
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

CGM
Use CGM when…
  • Technical Illustrations
  • Aerospace & Defense (S1000D)
  • CAD/CAM
  • Geophysics
HTJ2K-Codestream
Use HTJ2K-Codestream when…
  • Medical Imaging Pipelines
  • Geospatial Data Streaming
  • Digital Cinema
  • Embedded Systems
Share this comparison