Free webp to jpg
Image MIME Reference
DPX

Digital Picture Exchange

image/dpx
VS

BlockFact Image

image/vnd.blockfact.facti
FACTI

A complete technical comparison of Digital Picture Exchange and BlockFact Image — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.

Equal browser support

Feature Support

Feature DPX FACTI
Transparency (Alpha) Yes Yes
Animation Support ✕ No ✕ No
Progressive Loading ✕ No ✕ No
HDR Support Yes Yes
EXIF Metadata ✕ No Yes
ICC Color Profile ✕ No Yes
Digital Picture Exchange
image/dpx
Extension
.dpx
Container DPX (SMPTE ST 268)
Compression Uncompressed / RLE (Rarely used)
Algorithm
Uncompressed
Color Depth 8-bit, 10-bit, 12-bit, 16-bit, 32-bit (Float)
Developed by SMPTE (Society of Motion Picture and Television Engineers)
Released 1994
Magic Bytes
53 44 50 58 (Big-endian) / 58 50 44 53 (Little-endian)
Full DPX reference →
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)
Full FACTI reference →

Browser Support Comparison

Browser DPX FACTI
Chrome Chrome
Firefox Firefox
Safari Safari
Edge Edge
IE IE (Legacy)
DPX

DPX Strengths

  • Industry standard for transferring uncompressed, high-fidelity film and VFX data
  • Rich industry-specific metadata including timecode, keykode, and film stock information
  • Supports logarithmic color spaces (LogC, Cineon) to preserve the massive dynamic range of film negatives
Limitations
  • Massive file sizes (e.g., a single 4K 10-bit frame is ~50MB, resulting in ~1.2GB per second at 24fps)
  • Zero native support in web browsers or consumer OS image viewers
  • Requires heavy-duty, fast storage infrastructure (RAID/NVMe) to playback in real-time
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

DPX
Use DPX when…
  • Film Scanning
  • Visual Effects (VFX)
  • Digital Intermediate (DI)
  • Color Grading
  • Archival
FACTI
Use FACTI when…
  • Journalism and Media Authentication
  • Legal and Insurance Evidence
  • AI Deepfake Prevention
  • Content Provenance and Authorship
Share this comparison