Free webp to jpg
Image MIME Reference
FACTI

BlockFact Image

image/vnd.blockfact.facti
VS

JPEG XL

image/jxl
JXL

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

JXL wins on browser support

Feature Support

Feature FACTI JXL
Transparency (Alpha) Yes Yes
Animation Support ✕ No Yes
Progressive Loading ✕ No Yes
HDR Support Yes Yes
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)
Full FACTI reference →
JPEG XL
image/jxl
Extension
.jxl
Container ISOBMFF / JPEG XL Codestream
Compression Lossy (VarDCT) / Lossless (Modular)
Algorithm
VarDCT (Variable block-size DCT)Modular (Predictive coding for lossless)
Color Depth 8-bit, 10-bit, 12-bit, 16-bit, 32-bit (Float)
Developed by Joint Photographic Experts Group (JPEG)
Released 2021
Magic Bytes
FF 0A (Codestream) / 00 00 00 0C 4A 58 4C 20 0D 0A 87 0A (Container)
Full JXL reference →

Browser Support Comparison

Browser FACTI JXL
Chrome Chrome
Firefox Firefox
Safari Safari
✓ 17+
Edge Edge
IE 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
JXL

JXL Strengths

  • Capable of losslessly recompressing legacy JPEG files, saving ~20% space while retaining perfect byte-for-byte restorability
  • Highly superior progressive decoding (Saliency-driven), allowing recognizable images to load extremely fast on slow connections
  • Outperforms WebP and competes favorably with AVIF, especially at high-fidelity settings and for complex textures/photography
  • Royalty-free with an open-source reference implementation (libjxl)
Limitations
  • Google's removal of JXL support from Chrome severely hindered its adoption as a universal web standard
  • Lack of hardware decoding chips compared to video-derived codecs like AVIF (AV1)
  • File parsing logic is complex due to the split between raw codestreams and ISOBMFF containers

When to choose which format

FACTI
Use FACTI when…
  • Journalism and Media Authentication
  • Legal and Insurance Evidence
  • AI Deepfake Prevention
  • Content Provenance and Authorship
JXL
Use JXL when…
  • High-End Web Delivery (via Safari/Polyfills)
  • HDR Photography
  • Legacy JPEG Archiving
  • Digital Art & Image Storage
Share this comparison