Free webp to jpg
Image MIME Reference
JPX

JPEG 2000 Part 2 (Extended)

image/jpx
VS

Microsoft Document Imaging

image/vnd.ms-modi
MODI

A complete technical comparison of JPEG 2000 Part 2 (Extended) and Microsoft Document Imaging — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.

Equal browser support

Feature Support

Feature JPX MODI
Transparency (Alpha) Yes ✕ No
Animation Support Yes ✕ No
Progressive Loading Yes ✕ No
HDR Support Yes ✕ No
EXIF Metadata Yes ✕ No
ICC Color Profile Yes ✕ No
JPEG 2000 Part 2 (Extended)
image/jpx
Extension
.jpx.jpf
Container ISOBMFF / JPX (ISO/IEC 15444-2)
Compression Lossy / Lossless
Algorithm
Discrete Wavelet Transform (DWT)
Color Depth 8-bit, 16-bit, 32-bit, 38-bit
Developed by Joint Photographic Experts Group (JPEG)
Released 2002
Magic Bytes
00 00 00 0C 6A 50 20 20 0D 0A 87 0A ... 66 74 79 70 6A 70 78 20
Full JPX reference →
Microsoft Document Imaging
image/vnd.ms-modi
Extension
.mdi
Container TIFF Variant
Compression LZW / Proprietary MS Compression
Algorithm
LZW (Modified)
Color Depth 1-bit (Monochrome), 8-bit (Grayscale), 24-bit (RGB)
Developed by Microsoft Corporation
Released 2001
Magic Bytes
49 49 2A 00
Full MODI reference →

Browser Support Comparison

Browser JPX MODI
Chrome Chrome
Firefox Firefox
Safari Safari
Edge Edge
IE IE (Legacy)
JPX

JPX Strengths

  • Removes the color space limitations of baseline JP2, adding native support for CMYK, CIE Lab, and custom vendor color spaces
  • Supports multiple codestreams in a single file, allowing for rich compositing and animation
  • Enables fragmented files where image data and metadata can reside in separate physical files via data references
Limitations
  • Extremely complex specification makes full software implementation rare, leading to compatibility issues
  • Zero web browser support, rendering it unsuitable for public internet distribution
  • Often overkill for standard imaging tasks where baseline JP2 or modern alternatives like AVIF suffice
MODI

MODI Strengths

  • Historically provided an excellent all-in-one scanned document format with built-in OCR and annotations before PDF editing became universally accessible
  • Tightly integrated with Microsoft Office and SharePoint workflows in the early 2000s
Limitations
  • Completely proprietary and obsolete; Microsoft abandoned it in favor of standard TIFF and PDF
  • Causes widespread identification conflicts since its file signature is identical to a standard TIFF
  • Extremely difficult to open on modern operating systems without relying on third-party conversion utilities

When to choose which format

JPX
Use JPX when…
  • Prepress & Commercial Printing (CMYK)
  • Geospatial Data
  • Archival Preservation
  • Medical Imaging
MODI
Use MODI when…
  • Legacy Scanned Document Archival
  • Microsoft Office XP/2003/2007 Workflows
  • Embedded OCR Text Storage
Share this comparison