Image MIME Reference
PCO-B16
PCO B16 Image
image/vnd.pco.b16
VS
Pentax Electronic File
image/x-pentax-pef
Pentax-PEF
A complete technical comparison of PCO B16 Image and Pentax Electronic File — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | PCO-B16 | Pentax-PEF |
|---|---|---|
| Transparency (Alpha) | ✕ No | ✕ No |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | ✕ No | ✕ No |
| HDR Support | ✕ No | Yes |
| EXIF Metadata | ✕ No | Yes |
| ICC Color Profile | ✕ No | Yes |
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
Pentax Electronic File
image/x-pentax-pef
Extension
.pef
Container
TIFF-based (Proprietary)
Compression
Uncompressed / Proprietary Lossless
Algorithm
NonePentax Proprietary Lossless
Color Depth
12-bit (Per Channel), 14-bit (Per Channel)
Developed by
Pentax (now Ricoh Imaging Company, Ltd.)
Released
2003
Magic Bytes
49 49 2A 00 (Little-endian) or 4D 4D 00 2A (Big-endian)
Browser Support Comparison
| Browser | PCO-B16 | Pentax-PEF |
|---|---|---|
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
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
Pentax-PEF
Pentax-PEF Strengths
- Retains absolute maximum sensor data, enabling massive shadow recovery and highlight protection compared to compressed in-camera JPEGs
- White balance and sharpening are saved as metadata instructions rather than 'baked in', meaning they can be perfectly adjusted in post-production
- Utilizes the standard TIFF container structure, making it relatively straightforward for open-source software like LibRaw to parse
Limitations
- Proprietary format requires continuous updates to third-party processing software whenever Pentax releases a new camera model (unlike the open DNG format)
- Produces very large file sizes compared to standard web formats
- Cannot be directly embedded into web pages or used in standard HTML/CSS contexts
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
Pentax-PEF
Use Pentax-PEF when…
- Professional Digital Photography
- Non-destructive Image Post-Processing
- Pentax Camera Archival