Image MIME Reference
AIMG
Universal AI Media Format (Image)
image/prs.aimg
VS
High-Throughput JPEG 2000 Codestream
image/jphc
HTJ2K-Codestream
A complete technical comparison of Universal AI Media Format (Image) and High-Throughput JPEG 2000 Codestream — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | AIMG | HTJ2K-Codestream |
|---|---|---|
| Transparency (Alpha) | Yes | Yes |
| Animation Support | Yes | ✕ No |
| Progressive Loading | ✕ No | Yes |
| HDR Support | Yes | Yes |
| EXIF Metadata | Yes | ✕ No |
| ICC Color Profile | Yes | ✕ No |
Universal AI Media Format (Image)
image/prs.aimg
Extension
.aimg
Container
Universal AI Media Format (AIMF)
Compression
Container (Inherits payload compression, e.g., PNG/JPEG)
Algorithm
None (Pass-through to embedded payload)
Color Depth
Inherited from payload (8-bit, 16-bit, HDR)
Developed by
AI Media Format (ai-mf) Open-Source Project
Released
2026
Magic Bytes
Varies (Custom AIMF Header Prepended to Payload)
High-Throughput JPEG 2000 Codestream
image/jphc
Extension
.jhc
Container
None (Raw Codestream)
Compression
Lossy / Lossless
Algorithm
High-Throughput JPEG 2000 (HTJ2K)
Color Depth
8-bit, 16-bit, 32-bit, 38-bit
Developed by
Joint Photographic Experts Group (JPEG)
Released
2019
Magic Bytes
FF 4F FF 51
Browser Support Comparison
| Browser | AIMG | HTJ2K-Codestream |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
IE (Legacy)
|
✕ | ✕ |
AIMG
AIMG Strengths
- Provides a robust, tamper-evident cryptographic wrapper to definitively prove the origin of AI-generated media
- Header-first structure allows verifier nodes and APIs to validate an image's origin without needing to download or decode the entire massive pixel payload
Limitations
- Lacks native rendering support in browsers, requiring server-side extraction or client-side WebAssembly to display the embedded image
- Utilizes the IANA 'prs.' (personal/vanity) tree rather than the standards tree, which can cause strict enterprise firewalls to reject the MIME type as unverified
HTJ2K-Codestream
HTJ2K-Codestream Strengths
- Extremely fast encoding and decoding capabilities due to the parallelizable block coder
- Minimal file overhead since it lacks container headers and metadata
- Ideal for streaming applications or embedded systems where parsing a full container is unnecessary
Limitations
- Lacks standard metadata support (like EXIF, XMP, or ICC color profiles) since there is no container structure
- Zero native web browser compatibility
- Difficult to distinguish from standard JPEG 2000 codestreams without deeply parsing the internal marker segments
When to choose which format
AIMG
Use AIMG when…
- AI Provenance and Attribution
- Verifiable Deepfake Prevention
- Cryptographic Media Watermarking
- Generative AI Workflows
HTJ2K-Codestream
Use HTJ2K-Codestream when…
- Medical Imaging Pipelines
- Geospatial Data Streaming
- Digital Cinema
- Embedded Systems