Image MIME Reference
MODI
Microsoft Document Imaging
image/vnd.ms-modi
VS
Valve Texture Format
image/vnd.valve.source.texture
VTF
A complete technical comparison of Microsoft Document Imaging and Valve Texture Format — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | MODI | VTF |
|---|---|---|
| Transparency (Alpha) | ✕ No | Yes |
| Animation Support | ✕ No | Yes |
| Progressive Loading | ✕ No | ✕ No |
| HDR Support | ✕ No | Yes |
| EXIF Metadata | ✕ No | ✕ No |
| ICC Color Profile | ✕ No | ✕ No |
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
Valve Texture Format
image/vnd.valve.source.texture
Extension
.vtf
Container
Valve Texture Format Header
Compression
DXTC (DXT1, DXT3, DXT5) / Uncompressed (BGRA8888, RGB888, etc.)
Algorithm
DXT1-DXT5None
Color Depth
8-bit, 24-bit (RGB), 32-bit (RGBA), 16-bit Floating Point (HDR)
Developed by
Valve Corporation
Released
2004
Magic Bytes
56 54 46 00
Browser Support Comparison
| Browser | MODI | VTF |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
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
VTF
VTF Strengths
- Extremely fast loading within the Source Engine because the block-compressed data goes directly into the GPU's VRAM without CPU decompression overhead
- Bundles mipmaps, volumetric slices, cubemap faces, and animation frames entirely within a single file
- Openly documented by the Valve Developer Community, leading to a massive ecosystem of third-party modding tools
Limitations
- Strictly tied to the Source Engine ecosystem; entirely useless in standard web or print contexts
- No native support in standard image editors without hunting down and installing specialized plugins
- Block compression algorithms (DXT) are lossy and can cause visible artifacting, especially on normal maps or smooth gradients
When to choose which format
MODI
Use MODI when…
- Legacy Scanned Document Archival
- Microsoft Office XP/2003/2007 Workflows
- Embedded OCR Text Storage
VTF
Use VTF when…
- Source Engine Game Textures
- Custom Maps and Modding (Garry's Mod, CS:GO)
- Animated In-Game Decals and Sprays
- Environment Cubemaps (Skyboxes)