Free webp to jpg
EN
Image MIME Reference
JNG

JPEG Network Graphics

image/x-jng
VS

Portable Bitmap

image/x-portable-bitmap
PBM

A complete technical comparison of JPEG Network Graphics and Portable Bitmap — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.

Equal browser support

Feature Support

Feature JNG PBM
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
Full JNG reference →
Portable Bitmap
image/x-portable-bitmap
Extension
.pbm
Container Netpbm
Compression Uncompressed
Algorithm
None
Color Depth 1-bit (Monochrome)
Developed by Jef Poskanzer (Netpbm Project)
Released 1988
Magic Bytes
50 31 (ASCII) or 50 34 (Binary)
Full PBM reference →

Browser Support Comparison

Browser JNG PBM
Chrome Chrome
✕ ✕
Firefox Firefox
✕ ✕
Safari Safari
✕ ✕
Edge Edge
✕ ✕
IE 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
PBM

PBM Strengths

  • Absolute structural simplicity allows parsers to be written from scratch with just a few lines of code
  • ASCII encoding allows manual editing and debugging directly within a standard text editor
  • Serves as a flawless, lossless intermediary for 1-bit raster data like scanned documents or barcodes
Limitations
  • Strictly limited to 1-bit monochrome images; cannot natively display shades of gray or color
  • Lack of compression results in extremely large file sizes, particularly when using the ASCII 'P1' encoding
  • No support for alpha transparency or modern metadata standards like EXIF

When to choose which format

JNG
Use JNG when…
  • Embedded frames in MNG animations
  • Historical web graphics requiring lossy compression with transparency
PBM
Use PBM when…
  • Optical Character Recognition (OCR) Pre-processing
  • Unix/Linux Command-Line Image Pipelines
  • Academic Image Processing Teaching

More comparisons

JNG vs ACES → PBM vs ACES → JNG vs APNG → PBM vs APNG → JNG vs AVCI → PBM vs AVCI → JNG vs AVCS → PBM vs AVCS → JNG vs AVIF → PBM vs AVIF → All comparisons →
Share this comparison