JPEG 2000: Browser Support, vs JPEG, Use Cases

What is JPEG 2000?

JPEG 2000 is an image compression standard that the Joint Photographic Experts Group published as ISO/IEC 15444. It uses a discrete wavelet transform instead of the discrete cosine transform that legacy JPEG uses, supports both lossless and lossy compression in one architecture, and stores images in files with the .jp2 file extension.

Which browsers does JPEG 2000 support?

Safari was the only browser that ever supported JPEG 2000 natively, and Safari 18 removed that support, so no shipping browser today renders JPEG 2000 in HTML. Every other major browser shows a broken image icon for .jp2 sources.

What are the use cases of JPEG 2000?

JPEG 2000 lost the web but won several specialist industries that need lossless modes, scalable codestreams, and a single file format for both archive and delivery.

• Digital cinema: The Digital Cinema Initiatives Digital Cinema Package (DCP) standard uses JPEG 2000 as the picture codec, so every theatrical release that ships to a movie theater is a sequence of .j2c files inside an MXF container.
• Medical imaging: The DICOM specification accepts JPEG 2000 for CT, MRI, mammography, and pathology slides, since the lossless mode preserves diagnostic detail and the codestream supports tiled progressive viewing of gigapixel scans.
• Archives and digital preservation: The Library of Congress, national archives, and the FADGI imaging guidelines list JPEG 2000 as a recommended preservation format for high-resolution book scans, maps, and photo collections.
• Geospatial and GIS: Earth-observation satellites, aerial photography platforms, and GIS tools use JPEG 2000 (often as ECW or JP2 with GeoJP2 metadata) to deliver multi-gigabyte raster maps with progressive zoom and pan.
• Broadcast and post-production: Master-quality frame storage and contribution feeds inside broadcast plants use JPEG 2000 because the codestream supports frame-accurate access and visually lossless compression at 50 to 250 megabits per second.
• Long-term photography backups: Photographers who want a single archival format that carries both a lossless master and lossy proxies in one file pick JPEG 2000 over a DNG plus JPEG pair.

How do you view JPEG 2000 files in your browser?

No shipping browser renders a raw .jp2 file today, so opening JPEG 2000 in a browser tab needs a conversion or an embedding step. The numbered steps below cover the four practical paths.

• Convert to a web format with ffmpeg: Run ffmpeg -i input.jp2 output.png from a terminal. ffmpeg ships with the OpenJPEG decoder, so the converted PNG renders in every browser. Swap PNG for WebP or AVIF if you want a smaller file.
• Convert with ImageMagick: Run magick input.jp2 output.jpg if ffmpeg is not on the box. ImageMagick uses the same OpenJPEG library for JPEG 2000 input and writes a standards-compliant JPEG that any browser can show.
• Wrap the image inside a PDF: Drop the .jp2 into a PDF using a PDF authoring tool, then open the PDF in Chrome, Edge, or Firefox. The browser's PDF viewer (PDFium for Chromium browsers, PDF.js for Firefox) decodes JPEG 2000 inside the PDF even though the same browser refuses the raw .jp2 file.
• Use a desktop image viewer: Open the file in IrfanView, XnView, GIMP, Adobe Photoshop, or Apple Preview if a browser tab is not strictly required. Photoshop needs the JPEG 2000 plug-in installed once, then handles .jp2 natively.
• Decode in JavaScript with OpenJPEG.js: Load OpenJPEG compiled to WebAssembly, fetch the .jp2 over HTTPS, and draw the decoded pixels onto a canvas element. This is the only path that keeps the JPEG 2000 file as the source of truth on the page.

If the converted file looks washed out, check that the source .jp2 used the lossless 5/3 wavelet rather than the lossy 9/7 wavelet, since some converters apply a default tone map only on the lossy path.

What are the known issues with JPEG 2000?

JPEG 2000 has rich technical features, but real-world web delivery has more rough edges than working paths.

• Safari 18 removed support: Safari was the only browser that ever shipped a JPEG 2000 path, and WebKit removed the decoder in Safari 18 on macOS Sequoia and iOS 18. Sites that still serve .jp2 to Safari now break for users on the latest Apple OS.
• No Chromium, Firefox, or legacy support: Chrome, Edge, Opera, Samsung Internet, the legacy Android Browser, and Internet Explorer never decoded JPEG 2000 in HTML. The format has zero coverage on the open web outside of PDF embeds.
• User-Agent sniffing CDN traps: Some content delivery networks used UA sniffing to serve JPEG 2000 only to Safari, and Apple flagged this in the Safari 18 release notes as a breakage path. Audit your CDN rules if your image pipeline targets Safari by user agent.
• PDF.js decoder gaps: Firefox renders JPEG 2000 inside PDFs through PDF.js, but rare encoding modes (predictable termination, certain COD options) trigger the warning "Unable to decode image: JpxError" and leave a blank tile. Re-encode the source through OpenJPEG with default options to avoid this.
• Slower than native decoders: The PDF.js JavaScript decoder for JPEG 2000 is two to four times slower than the native PDFium path in Chrome on the same PDF, so multi-page scans inside Firefox feel laggy on older laptops.
• WebP, AVIF, and JPEG XL took the slot: Modern web image formats already match or beat JPEG 2000 on file size, ship in every major browser (with JPEG XL still landing), and carry no patent friction. There is no compression-led reason left to pick JPEG 2000 for the public web.
• Editor and tooling drag: Many image editors need a separate JPEG 2000 plug-in or codec pack, and command-line tools that do not bundle OpenJPEG fail with cryptic errors when fed a .jp2. This makes designer hand-offs slow.

In my experience, the cleanest migration off JPEG 2000 on the web is to transcode the master .jp2 to AVIF for modern browsers and JPEG for legacy fallback, both wrapped in a picture element, instead of trying to keep a JPEG 2000 path alive for the shrinking pool of Safari-on-iOS-17 devices.

Citations

All JPEG 2000 version numbers and platform notes in this guide come from these primary sources:

• ISO/IEC 15444-1 - JPEG 2000 image coding system: iso.org/standard/78321.html
• JPEG.org - JPEG 2000: jpeg.org/jpeg2000
• Wikipedia - JPEG 2000: en.wikipedia.org/wiki/JPEG_2000
• WebKit Bugzilla 178758 - Remove the support for JPEG2000: bugs.webkit.org/show_bug.cgi?id=178758
• WebKit - WebKit Features in Safari 18.0: webkit.org/blog/15865/webkit-features-in-safari-18-0
• Mozilla Bugzilla 36351 - Support the JPEG 2000 (JP2) format: bugzilla.mozilla.org/show_bug.cgi?id=36351
• Mozilla pdf.js OpenJPEG decoder: github.com/mozilla/pdf.js.openjpeg
• MDN Web Docs - Image file type and format guide: developer.mozilla.org/en-US/docs/Web/Media/Guides/Formats/Image_types
• Adobe - JPEG 2000 files: pros and cons: adobe.com/creativecloud/file-types/image/raster/jpeg-2000-file.html
• Digital Cinema Initiatives DCP specification: dcimovies.com/specification