Free webp to jpg
Image MIME Reference
NAPLPS

North American Presentation Level Protocol Syntax

image/naplps
VS

PCO B16 Image

image/vnd.pco.b16
PCO-B16

A complete technical comparison of North American Presentation Level Protocol Syntax and PCO B16 Image — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.

Equal browser support

Feature Support

Feature NAPLPS PCO-B16
Transparency (Alpha) ✕ No ✕ No
Animation Support Yes ✕ No
Progressive Loading Yes ✕ No
HDR Support ✕ No ✕ No
EXIF Metadata ✕ No ✕ No
ICC Color Profile ✕ No ✕ No
North American Presentation Level Protocol Syntax
image/naplps
Extension
.nap.naplps
Container NAPLPS Byte Stream
Compression Uncompressed (Tokenized ASCII Commands)
Algorithm
None (Coordinate encoding)
Color Depth 16-color palette (Indexed from larger color spaces)
Developed by ANSI / CSA (Based on Canadian CRC's Telidon)
Released 1983
Magic Bytes
1B (Variable / ESC sequences)
Full NAPLPS reference →
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
Full PCO-B16 reference →

Browser Support Comparison

Browser NAPLPS PCO-B16
Chrome Chrome
Firefox Firefox
Safari Safari
Edge Edge
IE IE (Legacy)
NAPLPS

NAPLPS Strengths

  • Extremely bandwidth-efficient, enabling colorful graphical interfaces over early 300 baud dial-up connections
  • Resolution-independent vector scaling allowed the exact same file to be displayed accurately on varied early PC monitors and television sets
Limitations
  • Completely obsolete and unsupported by modern web technologies
  • Relies heavily on stateful parsing and terminal emulators rather than straightforward file decoding
  • Easily misidentified by MIME sniffers as plain text or generic binary streams due to the lack of a standardized file header
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

When to choose which format

NAPLPS
Use NAPLPS when…
  • 1980s Videotex Services
  • Prodigy Online Service Graphics
  • Historical BBS Terminal Graphics
  • Legacy Teletext Broadcasts
PCO-B16
Use PCO-B16 when…
  • Microscopy and Life Sciences
  • High-Speed Camera Recording
  • Machine Vision and Industrial Inspection
  • Scientific Photometry
Share this comparison