Image MIME Reference
JNG
JPEG Network Graphics
image/x-jng
VS
T.38 Fax over IP (FoIP)
image/t38
T.38
A complete technical comparison of JPEG Network Graphics and T.38 Fax over IP (FoIP) — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | JNG | T.38 |
|---|---|---|
| Transparency (Alpha) | Yes | ✕ No |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | Yes | ✕ No |
| HDR Support | ✕ No | ✕ No |
| EXIF Metadata | Yes | ✕ No |
| ICC Color Profile | Yes | ✕ No |
JPEG Network Graphics
image/x-jng
Extension
.jng
Container
PNG-style Chunk Structure (JHDR, JDAT, IDAT, IEND)
Compression
Lossy (JPEG/DCT for color) / Lossless (Deflate for alpha mask)
Algorithm
JPEG (Discrete Cosine Transform)Deflate (LZ77)
Color Depth
8-bit, 12-bit, 24-bit (RGB), 32-bit (RGBA)
Developed by
MNG Development Group (Glenn Randers-Pehrson et al.)
Released
2001
Magic Bytes
8B 4A 4E 47 0D 0A 1A 0A
T.38 Fax over IP (FoIP)
image/t38
Extension
.t38
Container
UDPTL or TCP (Network Transport)
Compression
Lossless (MH, MR, MMR / T.4, T.6)
Algorithm
MH (Modified Huffman)MR (Modified Read)MMR (Modified Modified Read)
Color Depth
1-bit (Monochrome B&W)
Developed by
ITU-T (International Telecommunication Union)
Released
1998
Magic Bytes
None (Network Stream)
Browser Support Comparison
| Browser | JNG | T.38 |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
JNG
JNG Strengths
- Solved a massive technical hurdle in the early 2000s by combining high-compression lossy photographic data with crisp, 8-bit alpha transparency
- Utilized the highly robust, extensible chunk-based architecture of the PNG format
- Provided an excellent, bandwidth-saving alternative to massive 32-bit transparent PNGs for web design
Limitations
- Failed to achieve critical mass; browser vendors largely abandoned the MNG/JNG standard due to implementation complexity
- Completely obsolete today, having been superseded by natively supported, superior formats like WebP, AVIF, and HEIC
- Decoding requires a hybrid engine that can parse PNG chunks while simultaneously decoding a JPEG stream and a Deflate stream, complicating software support
T.38
T.38 Strengths
- Designed specifically to overcome the timing and packet-loss issues that plague traditional fax over standard VoIP audio codecs (like G.711)
- Reduces bandwidth requirements by transmitting fax protocol data rather than uncompressed audio tones
- Universally supported by enterprise SIP trunks and Session Border Controllers (SBCs) for FoIP
Limitations
- Not an actual image file format, causing confusion due to its 'image/' MIME classification
- Extremely complex to implement correctly over lossy UDP networks (relies on UDPTL redundancy mechanisms)
- Zero support in web browsers or standard image viewing software
When to choose which format
JNG
Use JNG when…
- Embedded frames in MNG animations
- Historical web graphics requiring lossy compression with transparency
T.38
Use T.38 when…
- Fax over IP (FoIP) Transmissions
- SIP/SDP Media Negotiation
- VoIP Gateways and PBX Systems
- Enterprise Fax Servers