PicaJet
Search Build shortlist

Reference Formats

JPEG 2000

A wavelet-based standard (ISO/IEC 15444) supporting both lossy and mathematically lossless compression with progressive, resolution-scalable decoding, used in cinema, medical and archival imaging.

Extension

.jp2

Full name

JPEG 2000 (ISO/IEC 15444)

Introduced

December 2000 (ISO/IEC 15444-1 Part 1)

Vendor

Joint Photographic Experts Group (ISO/IEC JTC 1)

What is inside the container

Unlike JPEG's DCT approach, JPEG 2000 uses discrete wavelet transform compression, supporting 1 to 38 bits per component (far beyond JPEG's 8-bit ceiling) in either lossy or reversible lossless mode, plus progressive resolution/quality streaming. Metadata lives in an XML box within the JP2 container structure — the mechanism the Library of Congress's National Digital Newspaper Program profile relies on — alongside support for embedded XMP and ICC color profiles.

How to open it

GIMP Import support for years; GIMP 3.2 (2026) added JP2 export as well
Photoshop No native support — requires a third-party plug-in
Specialist software Standard codec in DICOM medical-imaging PACS systems and Digital Cinema Package (DCP) mastering tools
Web browsers Not supported inline by any major browser as of 2025/2026, though embedded JPEG 2000 streams inside PDFs are commonly supported

For archives

Recommended as a viable archival master, particularly in its lossless mode, for large-scale digitization: institutions like the Library of Congress use JPEG 2000 (lossless or high-quality lossy) precisely because uncompressed TIFF masters become impractically large at gigapixel scale, and JPEG 2000's reversible compression keeps full fidelity in a much smaller footprint with progressive/scalable access.

JPEG 2000 was developed through the late 1990s and published as an ISO/IEC standard in December 2000, as the JPEG committee’s answer to the compression-artifact and scalability limits of the original DCT-based JPEG. Its wavelet-based approach enables progressive decoding: a viewer can pull a low-resolution preview instantly and stream in detail on demand, without downloading the full file — a property that made it the mandated codec for Digital Cinema Packages from 2004 onward and a standard component of the DICOM medical-imaging format for X-ray, MRI, and CT storage.

In a DAM, JPEG 2000 shows up less as an everyday preview format — browser and general-app support has never been strong — and more as a space-efficient archival master for very large scans. Its lossless mode preserves full fidelity from the source while compressing meaningfully better than uncompressed TIFF, which is why mass-digitization programs (newspaper archives, large-format cultural-heritage scans) have adopted it specifically to keep archival storage costs manageable without sacrificing quality.

The practical pitfall for DAM operators is tooling: Photoshop has no native JP2 support and needs a plug-in, and no mainstream browser renders it inline, so any DAM using JPEG 2000 as a master needs a dedicated derivative-generation step to produce JPEG or WebP previews for search results and web delivery. Its progressive/scalable decoding is a genuine asset for serving gigapixel masters (e.g., in a viewer that streams detail as the user zooms), but only if the DAM’s rendering pipeline is built to take advantage of it rather than just decoding the whole file.

Frequently asked

Is JPEG 2000 a viable DAM archival master format?

Yes, particularly in its lossless mode. Institutions like the Library of Congress use JPEG 2000 for large-scale digitization because uncompressed TIFF masters become impractically large at gigapixel scale, and JPEG 2000's reversible compression keeps full fidelity in a much smaller footprint.

Does JPEG 2000 work in web browsers?

No mainstream browser renders JPEG 2000 inline as of 2025/2026. Chrome, Firefox, and Edge never supported it in the img tag. Safari was the sole exception, via macOS's Image I/O framework, but Apple dropped that support in Safari 18 and macOS Sequoia (2024) — so native browser support is now effectively zero. PDF viewers still commonly decode JPEG 2000 streams embedded inside PDFs, but for web display a DAM must always generate a converted JPEG or WebP derivative.

Where does metadata live in a JPEG 2000 file?

Metadata lives in an XML box within the JP2 container structure — the mechanism the Library of Congress's National Digital Newspaper Program profile relies on — alongside support for embedded XMP and ICC color profiles.

Where is JPEG 2000 used outside of general DAM workflows?

JPEG 2000 is the mandated compression codec for Digital Cinema Packages (DCP), the format theaters use to receive feature films — the DCI spec requires a 12-bit X'Y'Z' color space at 4:4:4 sampling. It's also a required component of the DICOM medical-imaging standard, compressing X-ray, MRI, and CT scans, where DICOM permits up to JPEG 2000's full 38-bit sample precision. Beyond DAM and these two industries, museums and satellite-imagery archives also rely on it for master-quality storage.

Does Photoshop support JPEG 2000 natively?

No — current Photoshop (2024/2025) has no built-in JP2 support; opening or saving a JPEG 2000 file needs a third-party plug-in. That wasn't always so: Photoshop 7 through CS3 shipped an optional JPEG 2000 plug-in on the install disc that users had to manually install from the Goodies folder, never enabled by default, and Adobe later dropped that bundled plug-in entirely. GIMP, by contrast, added native JP2 export in GIMP 3.2 (2026), on top of its long-standing JP2 import support.

What bit depth does JPEG 2000 support compared to JPEG?

JPEG 2000's codestream format supports 1 to 38 bits per component — the DICOM standard's upper limit for medical imaging — versus ordinary JPEG's fixed 8-bit-per-channel ceiling. In practice, most photo-editing and DAM tooling reads or writes up to 16-bit-per-channel JPEG 2000 files, since that matches the depth most cameras, scanners, and editing pipelines actually produce. Either way, JPEG 2000 gives archival masters far more tonal headroom than standard JPEG, in both lossy and lossless modes.

What does JPEG 2000's progressive decoding offer a DAM?

Progressive resolution and quality streaming let a viewer pull a low-resolution preview instantly and stream in detail on demand — genuinely useful for serving gigapixel masters in a zoomable viewer, provided the DAM's rendering pipeline is built to take advantage of it.

What extra step does a DAM need for JPEG 2000 assets?

Because browser and general-app support has never been strong, any DAM using JPEG 2000 as a master needs a dedicated derivative-generation step to produce JPEG or WebP previews for search results and web delivery.

Sources