Image MIME Reference
FACTI
BlockFact Image
image/vnd.blockfact.facti
VS
SealedMedia SoftSeal JPEG
image/vnd.sealedmedia.softseal.jpg
SoftSeal-JPEG
A complete technical comparison of BlockFact Image and SealedMedia SoftSeal JPEG — covering compression, feature support, browser compatibility, magic bytes, and when to choose each format.
Equal browser support
Feature Support
| Feature | FACTI | SoftSeal-JPEG |
|---|---|---|
| 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)
SealedMedia SoftSeal JPEG
image/vnd.sealedmedia.softseal.jpg
Extension
.sjpg.sealed-jpg.sealed-jpeg
Container
SealedMedia SoftSeal Wrapper
Compression
Encrypted Payload (DCT)
Algorithm
AES EncryptionDiscrete Cosine Transform (Internal JPEG payload)
Color Depth
Encrypted Payload (Historically 24-bit RGB)
Developed by
SealedMedia (Acquired by Oracle Corporation)
Released
Late 1990s
Magic Bytes
Unknown (Proprietary SealedMedia Container)
Browser Support Comparison
| Browser | FACTI | SoftSeal-JPEG |
|---|---|---|
Chrome
|
✕ | ✕ |
Firefox
|
✕ | ✕ |
Safari
|
✕ | ✕ |
Edge
|
✕ | ✕ |
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
SoftSeal-JPEG
SoftSeal-JPEG Strengths
- Offered persistent document security; if a sensitive photo was emailed outside the company, it remained encrypted and unviewable without server authentication
- Administrators possessed the ability to remotely revoke viewing rights to a specific image globally at any time
Limitations
- Completely proprietary and relies on a central authentication server; if the server goes offline or the product is deprecated, the image is permanently inaccessible
- Zero support in modern operating systems, web browsers, or standard image editing suites without heavy enterprise client installations
- Oracle effectively discontinued the IRM product line, stranding many legacy sealed documents
When to choose which format
FACTI
Use FACTI when…
- Journalism and Media Authentication
- Legal and Insurance Evidence
- AI Deepfake Prevention
- Content Provenance and Authorship
SoftSeal-JPEG
Use SoftSeal-JPEG when…
- Enterprise Information Rights Management (IRM)
- Secure Distribution of Sensitive Photography
- Revocable Corporate Document Access