Image MIME Reference
KTX2
Khronos Texture 2.0
image/ktx2
VS
Microsoft Document Imaging
image/vnd.ms-modi
MODI
A complete technical comparison of Khronos Texture 2.0 and Microsoft Document Imaging — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | KTX2 | MODI |
|---|---|---|
| Transparency (Alpha) | Yes | ✕ No |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | ✕ No | ✕ No |
| HDR Support | Yes | ✕ No |
| EXIF Metadata | ✕ No | ✕ No |
| ICC Color Profile | ✕ No | ✕ No |
Khronos Texture 2.0
image/ktx2
Extension
.ktx2
Container
KTX 2.0
Compression
Basis Universal (ETC1S / UASTC) / Zstandard (zstd) Supercompression / Uncompressed
Algorithm
ETC1SUASTCZstandard (zstd)Raw GPU Formats (ASTC, BCn)
Color Depth
8-bit, 16-bit, 32-bit (Float)
Developed by
Khronos Group
Released
2021
Magic Bytes
AB 4B 54 58 20 32 30 BB 0D 0A 1A 0A
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
Browser Support Comparison
| Browser | KTX2 | MODI |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
KTX2
KTX2 Strengths
- Universal hardware compatibility: write once, transcode anywhere to the target GPU's preferred format (ASTC, BC7, PVRTC, etc.)
- Drastically reduces transmission size over networks thanks to Basis Universal and Zstandard supercompression
- Seamless integration with the glTF ecosystem for optimized 3D asset delivery
Limitations
- Requires WebAssembly (Wasm) decoders and JavaScript loaders for web viewing, increasing initial application payload slightly
- Encoding textures into high-quality Basis Universal UASTC can be computationally intensive and slow
- Zero support in traditional 2D image viewers or native OS previews
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
KTX2
Use KTX2 when…
- glTF 3D Models (KHR_texture_basisu)
- WebGPU and WebGL Applications
- Game Engines (Unity, Unreal, Godot)
- Augmented and Virtual Reality (AR/VR)
MODI
Use MODI when…
- Legacy Scanned Document Archival
- Microsoft Office XP/2003/2007 Workflows
- Embedded OCR Text Storage