Image MIME Reference
PCO-B16
PCO B16 Image
image/vnd.pco.b16
VS
T.38 Fax over IP (FoIP)
image/t38
T.38
A complete technical comparison of PCO B16 Image 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 | PCO-B16 | T.38 |
|---|---|---|
| Transparency (Alpha) | ✕ No | ✕ No |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | ✕ No | ✕ No |
| HDR Support | ✕ No | ✕ No |
| EXIF Metadata | ✕ No | ✕ No |
| ICC Color Profile | ✕ No | ✕ No |
PCO B16 Image
image/vnd.pco.b16
Extension
.b16
Container
PCO B16 Binary Container
Compression
Uncompressed (Raw Sensor Data)
Algorithm
None
Color Depth
16-bit (Monochrome or Bayer Raw Color)
Developed by
PCO AG (Excelitas PCO GmbH)
Released
Early 2000s
Magic Bytes
50 43 4F 2D
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 | PCO-B16 | T.38 |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
PCO-B16
PCO-B16 Strengths
- Preserves exact, uncompressed 16-bit raw sensor data, which is critically important for accurate scientific measurements, fluorescence microscopy, and photometry
- The simple, linear struct header is highly predictable and easy to parse in custom Python, MATLAB, or C++ scripts for researchers building bespoke pipelines
Limitations
- Generates massive file sizes due to the complete lack of image compression [1.3.1]
- Completely unsupported by standard operating systems, web browsers, and consumer image editing suites
- Strictly tied to the hardware and software ecosystems of a single camera manufacturer
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
PCO-B16
Use PCO-B16 when…
- Microscopy and Life Sciences
- High-Speed Camera Recording
- Machine Vision and Industrial Inspection
- Scientific Photometry
T.38
Use T.38 when…
- Fax over IP (FoIP) Transmissions
- SIP/SDP Media Negotiation
- VoIP Gateways and PBX Systems
- Enterprise Fax Servers