What is PJPEG?
PJPEG commonly refers to progressive JPEG, which stores an image in multiple scans. A decoder can show a coarse version of the entire image before later scans add finer detail.
How PJPEG works
A progressive JPEG divides coefficient information into a sequence of scans rather than coding each image region to completion in one pass. Early scans establish the broad structure across the frame, and later scans supply additional frequency detail or coefficient precision. It remains part of the conventional JPEG ecosystem, so it can pass through normal photographic asset pipelines, but the visible refinement behavior depends on both decoder and presentation software.
Key facts
- 1Progression may use spectral selection, successive approximation, or both to divide DCT coefficient data among scans; it is not a stack of independently encoded thumbnails.
- 2Progressive files normally retain the .jpg or .jpeg extension and the image/jpeg media type. The legacy image/pjpeg label is not required to identify their scan structure.
- 3A decoder that supports progressive JPEG can produce the final image from all scans even if it never displays intermediate passes; staged on-screen rendering is a separate implementation choice.
When PJPEG matters
Choose progressive JPEG when early visual feedback during a large photographic download is valuable. Mainstream browsers and imaging libraries decode progressive scans reliably, so reserve compatibility checks for constrained targets such as embedded or hardware decoders that implement only baseline JPEG.
Common use cases for file formats & compression
These examples cover file formats & compression broadly, not specifically PJPEG.
- Accepting heterogeneous uploads while producing a controlled set of delivery formats.
- Moving assets between cameras, editors, browsers, archives, and downstream APIs.
- Separating long-lived source files from compact derivatives optimized for a particular channel.
Working with file formats & compression
This guidance covers file formats & compression broadly, not just PJPEG.
A parser reads the file structure, identifies contained streams and metadata, and exposes them to a decoder or application. Conversion usually decodes the source representation and writes compatible information into a different structure or encoding.
This category covers file and bitstream formats, their structures, and the compression methods they use. A filename extension can be misleading, so evaluate the detected format, decoding support, metadata, transparency, color, timing, patents, and archival needs before choosing an output.
What you gain
- A suitable format preserves the properties a workflow actually needs.
- Standardized structures allow files to move between compatible tools and systems.
- Format conversion can improve delivery size, editability, or long-term accessibility.
What it costs
- Modern formats can save bandwidth but may need fallbacks for older clients and production tools.
- Converting to a simpler format can discard transparency, animation, metadata, color precision, or editability.
- Archival suitability, browser support, and editing support often favor different choices.
Before production
- 1Inspect the detected container, codec, MIME type, and magic bytes instead of trusting a suffix.
- 2Verify decoder support and preserve metadata, color, transparency, or timing when required.
- 3Retain the source when the chosen delivery format is lossy or tied to current software.