What is JPEG?
JPEG is a widely supported method of lossy compression for raster photographs and other continuous-tone imagery. Compression quality is adjustable, but common JPEG encoding does not provide transparency.
How JPEG works
The classic coding process transforms small image blocks into spatial-frequency coefficients, quantizes them, and entropy-codes the result. Quantization removes precision and is the main source of the familiar ringing, mosquito noise, and block visibility at constrained sizes. Chroma subsampling may reduce color resolution separately from the quantization setting. In a publishing pipeline, the coded scan data normally travels inside a marker-based JFIF or Exif-flavored file with profiles, orientation, and descriptive metadata handled independently.
Key facts
- 1Baseline JPEG commonly encodes each component in block-based discrete-cosine coefficients; damage near sharp edges becomes more obvious as quantization grows coarser.
- 2Progressive JPEG distributes coefficients across multiple scans so a decoder can refine the whole picture, while sequential JPEG completes blocks in a single scan.
- 3Resaving decoded pixels creates a new quantization generation, but copying or remuxing the original compressed scan data does not itself add image loss.
When JPEG matters
Choose JPEG when broad compatibility and small photographic files matter more than exact pixel preservation. Repeated encoding or aggressive compression can introduce blocking, ringing, and lost detail.
Common use cases for file formats & compression
These examples cover file formats & compression broadly, not specifically JPEG.
- 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 JPEG.
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.