Image MIME Reference
AVCI
AVC Image (HEIF Container)
image/avci
VS
BlockFact Image
image/vnd.blockfact.facti
FACTI
A complete technical comparison of AVC Image (HEIF Container) and BlockFact Image — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | AVCI | FACTI |
|---|---|---|
| Transparency (Alpha) | Yes | Yes |
| Animation Support | ✕ No | ✕ No |
| Progressive Loading | ✕ No | ✕ No |
| HDR Support | Yes | Yes |
| EXIF Metadata | Yes | Yes |
| ICC Color Profile | Yes | Yes |
AVC Image (HEIF Container)
image/avci
Extension
.avci.hif
Container
HEIF / ISOBMFF (ISO/IEC 14496-12)
Compression
Lossy / Lossless
Algorithm
AVC (Advanced Video Coding / H.264)
Color Depth
8-bit, 10-bit, 12-bit
Developed by
Moving Picture Experts Group (MPEG) / ISO/IEC JTC 1
Released
2015
Magic Bytes
XX XX XX XX 66 74 79 70 61 76 63 69
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)
Browser Support Comparison
| Browser | AVCI | FACTI |
|---|---|---|
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
|
|
✕ | ✕ |
AVCI
AVCI Strengths
- Shares the robust, flexible HEIF container architecture that allows for rich metadata, HDR, and depth maps.
- Backed by the highly ubiquitous AVC (H.264) codec, which is widely supported in hardware decoding.
- Supports rectangular cropping and rotation metadata without needing to re-encode the pixel data.
Limitations
- No native support within web browsers for HTML rendering.
- Inferior compression efficiency when compared to newer container formats like HEIC (HEVC) or AVIF (AV1).
- Easily confused with HEIC and AVIF, which use the same base ISOBMFF container.
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
When to choose which format
AVCI
Use AVCI when…
- Digital Photography
- Camera Capture
- Archival Storage
FACTI
Use FACTI when…
- Journalism and Media Authentication
- Legal and Insurance Evidence
- AI Deepfake Prevention
- Content Provenance and Authorship