Free webp to jpg
Image MIME Reference
AIMG

Universal AI Media Format (Image)

image/prs.aimg
VS

JPEG Stereo Image

image/x-jps
JPS

A complete technical comparison of Universal AI Media Format (Image) and JPEG Stereo Image — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.

JPS wins on browser support

Feature Support

Feature AIMG JPS
Transparency (Alpha) Yes ✕ No
Animation Support Yes ✕ No
Progressive Loading ✕ No Yes
HDR Support Yes ✕ No
EXIF Metadata Yes Yes
ICC Color Profile Yes Yes
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)
Full AIMG reference →
JPEG Stereo Image
image/x-jps
Extension
.jps
Container JPEG (JFIF/Exif)
Compression Lossy (JPEG/DCT)
Algorithm
JPEG (Discrete Cosine Transform)
Color Depth 8-bit (Grayscale), 24-bit (RGB)
Developed by Stereoscopic Community (Unofficial Standard)
Released 1990
Magic Bytes
FF D8 FF
Full JPS reference →

Browser Support Comparison

Browser AIMG JPS
Chrome Chrome
✓ 1
Firefox Firefox
✓ 1
Safari Safari
✓ 1
Edge Edge
✓ 12
IE 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
JPS

JPS Strengths

  • 100% backward compatible with every standard 2D image viewer and web browser (which simply display the two halves side-by-side)
  • Inherits JPEG's excellent lossy compression, resulting in small file sizes ideal for web transmission
  • Extremely easy to generate programmatically by simply stitching two JPEG images side-by-side onto a wider canvas
Limitations
  • Lack of a dedicated metadata standard means viewing software has to guess whether the layout is 'cross-eyed' (right eye left, left eye right) or 'parallel' (left eye left, right eye right), occasionally causing inverted depth
  • Suffers from JPEG compression artifacts, which can break the stereoscopic illusion if compression noise differs between the left and right eyes
  • Superseded in consumer electronics by the MPO (Multi-Picture Object) format, which stacks separate full-resolution JPEGs rather than squishing them side-by-side

When to choose which format

AIMG
Use AIMG when…
  • AI Provenance and Attribution
  • Verifiable Deepfake Prevention
  • Cryptographic Media Watermarking
  • Generative AI Workflows
JPS
Use JPS when…
  • Stereoscopic 3D Photography
  • Virtual Reality (VR) Image Galleries
  • Cross-eye / Parallel Stereograms
Share this comparison