Image MIME Reference
FITS
Flexible Image Transport System
image/fits
VS
T.38 Fax over IP (FoIP)
image/t38
T.38
A complete technical comparison of Flexible Image Transport System 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 | FITS | T.38 |
|---|---|---|
| Transparency (Alpha) | ✕ No | ✕ No |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | ✕ No | ✕ No |
| HDR Support | Yes | ✕ No |
| EXIF Metadata | ✕ No | ✕ No |
| ICC Color Profile | ✕ No | ✕ No |
Flexible Image Transport System
image/fits
Extension
.fits.fit.fts
Container
FITS
Compression
Uncompressed / Tile Compressed (Rice, GZIP)
Algorithm
UncompressedRiceGZIPHcompress
Color Depth
8-bit, 16-bit, 32-bit, 64-bit (Float/Double)
Developed by
IAU FITS Working Group / NASA
Released
1981
Magic Bytes
53 49 4D 50 4C 45 20 20 3D 20
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 | FITS | T.38 |
|---|---|---|
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
FITS
FITS Strengths
- The undisputed global standard for archiving and sharing astronomical data
- Self-documenting: Headers are written in plain ASCII, ensuring data is readable decades later regardless of software
- Supports incredibly high dynamic range, N-dimensional arrays, and complex binary tables
Limitations
- No support in standard consumer software or web browsers
- Uncompressed raw FITS files from modern telescopes can be excessively large
- Does not use standard metadata models like EXIF or XMP, requiring specialized parsers
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
FITS
Use FITS when…
- Astronomy & Astrophysics
- Space Telescope Data (Hubble, JWST)
- Scientific Data Archiving
- Spectroscopy
T.38
Use T.38 when…
- Fax over IP (FoIP) Transmissions
- SIP/SDP Media Negotiation
- VoIP Gateways and PBX Systems
- Enterprise Fax Servers