Free webp to jpg
Image MIME Reference
DGN

MicroStation Design File

image/x-vnd.dgn
VS

Progressive JPEG (Legacy IE Alias)

image/pjpeg
PJPEG

A complete technical comparison of MicroStation Design File and Progressive JPEG (Legacy IE Alias) — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.

PJPEG wins on browser support

Feature Support

Feature DGN PJPEG
Transparency (Alpha) Yes ✕ No
Animation Support ✕ No ✕ No
Progressive Loading ✕ No Yes
HDR Support ✕ No ✕ No
EXIF Metadata ✕ No Yes
ICC Color Profile ✕ No Yes
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 →
Progressive JPEG (Legacy IE Alias)
image/pjpeg
Extension
.jpeg.jpg.pjpeg.pjp.jfif
Container JPEG (ISO/IEC 10918-1)
Compression Lossy (DCT)
Algorithm
Discrete Cosine Transform (DCT)
Color Depth 8-bit, 12-bit
Developed by Joint Photographic Experts Group / Microsoft (Alias)
Released 1992
Magic Bytes
FF D8 FF E0 (JFIF) / FF D8 FF E1 (Exif)
Full PJPEG reference →

Browser Support Comparison

Browser DGN PJPEG
Chrome Chrome
✓ All
Firefox Firefox
✓ All
Safari Safari
✓ All
Edge Edge
✓ All
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
PJPEG

PJPEG Strengths

  • Progressive JPEGs (which this MIME type attempted to describe) provide excellent perceived loading speeds on slow connections by rendering a low-resolution preview first
  • Files sent with this MIME type are fully backwards compatible with any standard JPEG decoder
Limitations
  • It is a non-standard MIME type that violates IANA specifications
  • Causes strict file upload validation scripts to fail if not explicitly whitelisted or mapped
  • Creates unnecessary confusion, as the official image/jpeg MIME type already fully encompasses progressive encoding

When to choose which format

DGN
Use DGN when…
  • Civil Engineering and Plant Design
  • Large-scale Architecture and Construction (AEC)
  • 2D/3D Infrastructure Modeling
PJPEG
Use PJPEG when…
  • Legacy Internet Explorer File Uploads
  • Progressive Image Rendering (Historical context)
Share this comparison