Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO/IEC 16485-04: Mixed Raster Content (MRC) — Architecture, Implementation, and Compliance
A comprehensive technical overview of the international standard for mixed raster content encoding used in digital imaging and document compression
Scope and Application
ISO/IEC 16485-04, adopted in Canada as CAN/CSA ISO/IEC 16485-04, defines the Mixed Raster Content (MRC) model for representing and compressing documents that contain a combination of text, line art, continuous-tone images, and graphics. This standard aligns with ITU-T Recommendation T.44 and provides the foundational architecture used in modern document imaging workflows, including PDF, network scanners, digital copiers, and archival systems.
The MRC model enables significant compression gains — often 5–10 times over single-method compression — by decomposing a page into several layers, each optimized for a specific content type. The standard covers both the encoding syntax and the decoding process, ensuring interoperability across different implementations.
Technical Architecture and Requirements
Layer Model
Under the MRC model, a page is divided into a sequence of stripes, each stripe containing up to three layers:
| Layer | Type | Compression Method | Typical Content |
|---|---|---|---|
| Background (Layer 0) | Continuous-tone | JPEG, JPEG 2000 | Photographs, gradients |
| Foreground (Layer 1) | Continuous-tone | JPEG, JPEG 2000 | Colored text, logos, line art |
| Mask (Layer 2) | Binary | JBIG2, G4 (MMR) | Text shapes, thin lines |
The mask layer controls the pixel-by-pixel selection between the background and foreground layers, enabling sharp edges for text while maintaining continuous-tone quality in image regions.
Stripe Processing
Each page is partitioned into horizontal stripes (typically 256 lines high). Each stripe is independently encoded, which allows parallel processing and partial decoding for viewport navigation. Stripes are further divided into blocks that can hold different types of data, including instructions for layer merging and color space conversions.
Compression and Coding
The standard requires that background and foreground layers be coded with a lossy or lossless continuous-tone algorithm (e.g., JPEG, JPEG 2000, or deflate), while the mask layer must use a binary compression method (JBIG2 preferred for text, G4 for legacy compatibility). Key requirements include:
- Color spaces: sRGB, CIELAB, or monochrome; ICC profiles may be embedded.
- Resolution independence: input resolution is signaled in the data stream.
- Stripe synchronization: decoders must handle stripes in any order if the format permits.
Tip: For optimal compression, use JBIG2 for the mask layer and lossy JPEG (quality ~85) for continuous-tone layers. This typically yields compression ratios of 20:1 or higher for mixed-content pages.
Implementation Highlights
Encoding and Decoding Process
A conforming encoder must perform page segmentation to assign each pixel to one of the three layers. This segmentation is the most computationally intensive part of the encoding. The standard does not mandate a specific segmentation algorithm, leaving room for innovation, but the output bitstream must conform to the MRC syntax as described in the normative clauses.
Decoding follows a strict pipeline: decode each layer independently, then composite using the mask. The compositing rule is: output = mask ? foreground : background. Decoders must support all allowed compression algorithms and color spaces; fallback modes are allowed for unsupported methods only if the encoder sets a compatibility flag.
Performance Considerations
- Memory: Striping limits memory footprint to a few stripe rows.
- Latency: Parallel stripe decoding reduces overall latency for large pages.
- Interoperability: Some segments (e.g., image objects) may be encrypted or signed; the standard defines containers for such protected data.
Important: Encoders must carefully handle anti-aliasing around text edges. If the mask layer is not properly anti-aliased, visual artifacts such as jagged edges or halo effects may appear in the composite output.
Compliance and Certification
For a product to claim compliance with ISO/IEC 16485-04 (or CAN/CSA ISO/IEC 16485-04), it must pass conformance testing as defined in the standard’s Annex A. Key compliance checks include:
- Correct stripe structure and block ordering
- Valid color space descriptors and transfer functions
- Proper use of marker codes and reserved bits
- Decoded image fidelity within specified error thresholds
Although self-declaration is permitted, certification bodies such as CSA Group offer formal verification programs. Many enterprise contracts and government procurement requirements mandate CSA-certified implementations for document archiving and exchange.
Compliance Benefit: Adhering to the standard ensures that documents compressed with MRC can be reliably exchanged between different vendors’ systems, preserving both file size efficiency and visual quality.
Non-compliance risk: Deviations from the stripe syntax or unsupported compression methods can render a bitstream unreadable by conforming decoders, leading to data loss in archival workflows.
Frequently Asked Questions
Q: Is ISO/IEC 16485-04 the same as ITU-T T.44?
A: Yes. The MRC model in ISO/IEC 16485-04 is technically aligned with ITU-T Recommendation T.44, though the ITU-T version uses different annex numbering. Implementers can refer to either document for core requirements.
A: Yes. The MRC model in ISO/IEC 16485-04 is technically aligned with ITU-T Recommendation T.44, though the ITU-T version uses different annex numbering. Implementers can refer to either document for core requirements.
Q: Can MRC files be directly used in PDF documents?
A: Yes. PDF 1.5 and later support MRC-based compression using an Image XObject with the MRC filter, though many PDF writers implement the model internally without exposing the MRC syntax directly.
A: Yes. PDF 1.5 and later support MRC-based compression using an Image XObject with the MRC filter, though many PDF writers implement the model internally without exposing the MRC syntax directly.
Q: What is the maximum resolution supported by the standard?
A: The standard does not define a hard resolution limit, but the stripe height field (8-bit) limits stripes to 256 lines. For pages taller than 256 pixels, multiple stripes are used. Resolutions up to 1200 dpi are commonly implemented.
A: The standard does not define a hard resolution limit, but the stripe height field (8-bit) limits stripes to 256 lines. For pages taller than 256 pixels, multiple stripes are used. Resolutions up to 1200 dpi are commonly implemented.
Q: Is JBIG2 mandatory for the mask layer?
A: No. The standard allows any binary compression method. JBIG2 is strongly recommended for text, but G4 (MMR) is also compliant. The encoder must signal the method used in the block header.
A: No. The standard allows any binary compression method. JBIG2 is strongly recommended for text, but G4 (MMR) is also compliant. The encoder must signal the method used in the block header.
ISO/IEC 16485-04 and CAN/CSA ISO/IEC 16485-04 are copyright protected by their respective standards bodies. This article provides general technical guidance and does not substitute the official normative text. © 2026