Free webp to jpg
Image MIME Reference
DECE-Graphic

Digital Entertainment Content Ecosystem (DECE) Graphic

image/vnd.dece.graphic
VS

High-Throughput JPEG 2000 Codestream

image/jphc
HTJ2K-Codestream

A complete technical comparison of Digital Entertainment Content Ecosystem (DECE) Graphic 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 DECE-Graphic 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 ✕ No ✕ No
Digital Entertainment Content Ecosystem (DECE) Graphic
image/vnd.dece.graphic
Extension
.jpg.png.uvi
Container Standard JPEG/PNG within DECE CFF structures
Compression Lossy (JPEG) / Lossless (PNG)
Algorithm
DCT (JPEG)DEFLATE (PNG)
Color Depth 8-bit (RGB), 24-bit (RGB)
Developed by Digital Entertainment Content Ecosystem (DECE) LLC
Released 2011
Magic Bytes
FF D8 FF (If JPEG) / 89 50 4E 47 (If PNG)
Full DECE-Graphic 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 DECE-Graphic HTJ2K-Codestream
Chrome Chrome
Firefox Firefox
Safari Safari
Edge Edge
IE IE (Legacy)
DECE-Graphic

DECE-Graphic Strengths

  • Allowed the UltraViolet DRM ecosystem to easily distinguish structural UI/cover graphic assets from actual encrypted video tracks in a Common File Format container
Limitations
  • Completely obsolete since the 2019 shutdown of UltraViolet
  • Unnecessary abstraction, as the underlying files were just standard JPEGs or PNGs
  • Causes modern strict MIME-type validators to fail if they rely on the Content-Type header
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

DECE-Graphic
Use DECE-Graphic when…
  • UltraViolet Movie Cover Art
  • Common File Format (CFF) Asset Manifests
  • Legacy DRM Ecosystems
HTJ2K-Codestream
Use HTJ2K-Codestream when…
  • Medical Imaging Pipelines
  • Geospatial Data Streaming
  • Digital Cinema
  • Embedded Systems
Share this comparison