Free webp to jpg
Image MIME Reference
DGN

MicroStation Design File

image/x-vnd.dgn
VS

High-Throughput JPEG 2000 Codestream

image/jphc
HTJ2K-Codestream

A complete technical comparison of MicroStation Design File 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 DGN 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
MicroStation Design File
image/x-vnd.dgn
Extension
.dgn
Container Microsoft OLE Compound File (V8) / IGDS (V7)
Compression Uncompressed / OLE Structured Storage
Algorithm
None
Color Depth Indexed Color (V7), 24-bit True Color (V8)
Developed by Intergraph (Originally) / Bentley Systems (Currently)
Released 1980
Magic Bytes
D0 CF 11 E0 A1 B1 1A E1 (For V8 DGN)
Full DGN 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 DGN HTJ2K-Codestream
Chrome Chrome
Firefox Firefox
Safari Safari
Edge Edge
IE IE (Legacy)
DGN

DGN Strengths

  • Exceptionally robust at handling massive, coordinate-heavy infrastructure models that would frequently crash older versions of competing CAD software
  • Deeply entrenched as the absolute standard format for many global departments of transportation and civil engineering firms
  • V8 architecture supports boundless design plane coordinates, eliminating the physical scaling limitations of V7
Limitations
  • Deeply proprietary format requiring complex third-party libraries (like the ODA SDK) to parse or write programmatically outside of the Bentley ecosystem
  • V8's reliance on the archaic Microsoft OLE Compound File container makes file introspection cumbersome
  • Cannot be rendered natively in web browsers without converting to WebGL/Canvas formats or SVG
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

DGN
Use DGN when…
  • Civil Engineering and Plant Design
  • Large-scale Architecture and Construction (AEC)
  • 2D/3D Infrastructure Modeling
HTJ2K-Codestream
Use HTJ2K-Codestream when…
  • Medical Imaging Pipelines
  • Geospatial Data Streaming
  • Digital Cinema
  • Embedded Systems
Share this comparison