Image MIME Reference
FACTI
BlockFact Image
image/vnd.blockfact.facti
VS
PTI Image (Personal/Vanity Tree)
image/prs.pti
PTI
A complete technical comparison of BlockFact Image and PTI Image (Personal/Vanity Tree) — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | FACTI | PTI |
|---|---|---|
| Transparency (Alpha) | Yes | ✕ No |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | ✕ No | ✕ No |
| HDR Support | Yes | ✕ No |
| EXIF Metadata | Yes | ✕ No |
| ICC Color Profile | Yes | ✕ No |
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)
PTI Image (Personal/Vanity Tree)
image/prs.pti
Extension
.pti
Container
Proprietary
Compression
Unknown / Proprietary
Algorithm
Unknown
Color Depth
Unknown
Developed by
Jürn Laun
Released
1999
Magic Bytes
Unknown
Browser Support Comparison
| Browser | FACTI | PTI |
|---|---|---|
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
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
PTI
PTI Strengths
- Provided a registered MIME type namespace for a specific application's proprietary image format without conflicting with standard web types
Limitations
- Completely undocumented and unsupported in modern ecosystems
- Zero web browser compatibility
- Falls into the 'vanity' tree, making it irrelevant for standard cross-platform data exchange
When to choose which format
FACTI
Use FACTI when…
- Journalism and Media Authentication
- Legal and Insurance Evidence
- AI Deepfake Prevention
- Content Provenance and Authorship
PTI
Use PTI when…
- Legacy Application Specific Workflows
- Proprietary Image Storage