Image MIME Reference
FACTI
BlockFact Image
image/vnd.blockfact.facti
VS
Progressive JPEG (Legacy IE Alias)
image/pjpeg
PJPEG
A complete technical comparison of BlockFact Image and Progressive JPEG (Legacy IE Alias) — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
PJPEG wins on browser support
Feature Support
| Feature | FACTI | PJPEG |
|---|---|---|
| Transparency (Alpha) | Yes | ✕ No |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | ✕ No | Yes |
| HDR Support | Yes | ✕ No |
| EXIF Metadata | Yes | Yes |
| ICC Color Profile | Yes | Yes |
BlockFact Image
image/vnd.blockfact.facti
Extension
.facti
Container
BlockFact Authenticated Container
Compression
Container (Inherits payload compression, e.g., JPEG/PNG)
Algorithm
None (Pass-through to embedded payload)
Color Depth
Inherited from payload
Developed by
BlockFact
Released
2025
Magic Bytes
Unknown (Proprietary Container)
Progressive JPEG (Legacy IE Alias)
image/pjpeg
Extension
.jpeg.jpg.pjpeg.pjp.jfif
Container
JPEG (ISO/IEC 10918-1)
Compression
Lossy (DCT)
Algorithm
Discrete Cosine Transform (DCT)
Color Depth
8-bit, 12-bit
Developed by
Joint Photographic Experts Group / Microsoft (Alias)
Released
1992
Magic Bytes
FF D8 FF E0 (JFIF) / FF D8 FF E1 (Exif)
Browser Support Comparison
| Browser | FACTI | PJPEG |
|---|---|---|
Chrome
|
✕ |
✓ All
|
Firefox
|
✕ |
✓ All
|
Safari
|
✕ |
✓ All
|
Edge
|
✕ |
✓ All
|
IE (Legacy)
|
✕ |
✓
|
FACTI
FACTI Strengths
- Provides undeniable, mathematically verifiable proof of a photo's origin (time, location, and device) via the StarkNet blockchain [1.3.1]
- Privacy-first design utilizes zero-knowledge proofs (Groth16), meaning the actual image is never uploaded to a central server or blockchain
- Invisible watermarking ensures that even if the image is screenshotted or cropped, tampering can be detected
Limitations
- Lacks native rendering support in web browsers and standard image viewers, requiring specialized software to view
- Requires blockchain registration at the moment of capture, making it incompatible with existing legacy photos
- The proprietary nature of the container limits integration to environments supporting the BlockFact SDK
PJPEG
PJPEG Strengths
- Progressive JPEGs (which this MIME type attempted to describe) provide excellent perceived loading speeds on slow connections by rendering a low-resolution preview first
- Files sent with this MIME type are fully backwards compatible with any standard JPEG decoder
Limitations
- It is a non-standard MIME type that violates IANA specifications
- Causes strict file upload validation scripts to fail if not explicitly whitelisted or mapped
- Creates unnecessary confusion, as the official image/jpeg MIME type already fully encompasses progressive encoding
When to choose which format
FACTI
Use FACTI when…
- Journalism and Media Authentication
- Legal and Insurance Evidence
- AI Deepfake Prevention
- Content Provenance and Authorship
PJPEG
Use PJPEG when…
- Legacy Internet Explorer File Uploads
- Progressive Image Rendering (Historical context)