Free webp to jpg
EN
Image MIME Reference
JNG

JPEG Network Graphics

image/x-jng
VS

JPEG XS Codestream

image/jxsc
JPEG-XS-Codestream

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

Equal browser support

Feature Support

Feature JNG JPEG-XS-Codestream
Transparency (Alpha) Yes Yes
Animation Support ✕ No ✕ No
Progressive Loading Yes ✕ No
HDR Support ✕ No Yes
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 →
JPEG XS Codestream
image/jxsc
Extension
.jxsc.jxs
Container None (Raw Codestream)
Compression Lossy (Visually Lossless) / Mathematically Lossless
Algorithm
JPEG XS (ISO/IEC 21122-1)
Color Depth 8-bit, 10-bit, 12-bit, 14-bit, 16-bit
Developed by Joint Photographic Experts Group (JPEG) / intoPIX
Released 2019
Magic Bytes
FF 10
Full JPEG-XS-Codestream reference →

Browser Support Comparison

Browser JNG JPEG-XS-Codestream
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
JPEG-XS-Codestream

JPEG-XS-Codestream Strengths

  • Eliminates container overhead, maximizing parsing speed and minimizing latency to fractions of a millisecond
  • Highly optimized for direct hardware implementation in FPGAs and ASICs
  • Perfect for continuous data streaming over IP networks without needing to establish file headers
Limitations
  • Lacks standard container metadata (EXIF, XMP, ICC profiles), meaning color space and orientation data must be handled externally or out-of-band
  • Zero support in web browsers or standard consumer operating systems
  • Often requires specialized broadcast hardware or custom software libraries to decode

When to choose which format

JNG
Use JNG when…
  • Embedded frames in MNG animations
  • Historical web graphics requiring lossy compression with transparency
JPEG-XS-Codestream
Use JPEG-XS-Codestream when…
  • Hardware Decoding Pipelines (FPGA/ASIC)
  • Live Broadcast Infrastructure
  • Video over IP Transport
  • Embedded Camera Systems

More comparisons

JNG vs ACES → JPEG-XS-Codestream vs ACES → JNG vs APNG → JPEG-XS-Codestream vs APNG → JNG vs AVCI → JPEG-XS-Codestream vs AVCI → JNG vs AVCS → JPEG-XS-Codestream vs AVCS → JNG vs AVIF → JPEG-XS-Codestream vs AVIF → All comparisons →
Share this comparison