Authenticity for the AI Era
SteMi Labs • Early prototype
PixelSeal embeds cryptographic integrity directly into a digital master image so any modification becomes detectable — even if metadata is removed. The image remains visually unchanged.
Cryptographic tamper detection for high-value images
PixelSeal binds integrity to the image data itself. If pixels change, verification fails.
Trust is becoming a technical problem
In the AI era, images can be generated, edited, and republished effortlessly. For high-value digital assets, trust increasingly depends on verifiable integrity, not assumptions.
- Metadata can be stripped or rewritten.
- Certificates can be separated from files.
- Visual inspection can’t reliably prove authenticity.
The image proves its own integrity
PixelSeal makes images tamper-evident by embedding cryptographic integrity directly into the pixels — so any modification becomes detectable, even if metadata is removed.
Why PixelSeal when C2PA already exists?
C2PA and PixelSeal solve different parts of the authenticity problem. C2PA focuses on provenance — who created or edited a file and how. PixelSeal focuses on integrity — whether the image itself has changed since sealing.
Provenance and content history
- Tracks origin, edits, and workflow history.
- Relies on signed metadata and ecosystem support.
- Useful when provenance travels with the asset.
File-level tamper detection
- Embeds tamper-evident integrity directly into image data.
- Works even if metadata is removed.
- Useful when the key question is: Was this file changed?
PixelSeal tells you if the image was changed.
Best for C2PA
Provenance workflows, publishing chains, and environments where content credentials remain attached.
Best for PixelSeal
High-value master files, archives, submissions, and integrity-sensitive image workflows.
Together
C2PA can provide provenance metadata, while PixelSeal can provide intrinsic tamper detection inside the image itself.
Three simple steps
Seal
Seal a lossless master image (PNG, WebP, BMP, or TIFF).
Share
Use and distribute the sealed image as your authoritative master copy.
Verify
Verify later to confirm the file is unchanged (Verified / Modified).
What it proves
- The sealed image file has not changed since it was sealed.
- Any pixel modification becomes detectable.
- Optional signing enables stronger trust assertions.
What it does not claim
- It does not prove a scene is “real.”
- It does not detect whether content is AI-generated.
- It does not preserve verification through lossy conversions (for example, JPEG).
Designed for high-value digital assets
PixelSeal is best for protecting master files that should not change after finalization.
Fine-art photography masters
Seal final exhibition-quality files for archival and provenance workflows.
Limited-edition digital art
Protect the canonical digital master used to produce editions.
Gallery & studio archives
Maintain an integrity-verifiable archive of high-value assets.
Competition submissions
Seal the submitted master file and verify later if questioned.
Legal / insurance images
Protect lossless masters used in documentation workflows.
Scientific imaging (future)
Potential fit for lossless scientific master images and archives.
Try the concept in 60 seconds
- Upload a lossless image.
- Seal it and download the sealed result.
- Make a small edit and re-verify to see verification fail.
Demo URL: https://demo.stemilabs.com/
Quick answers
What formats are supported?
The prototype supports lossless formats: PNG, WebP (lossless), BMP, and TIFF.
Why not JPEG?
JPEG is lossy; saving or re-saving changes pixel values and breaks pixel-level integrity verification.
Does it work if metadata is removed?
Yes—because the integrity seal is embedded into image data rather than relying only on metadata.
Is it a replacement for C2PA?
No. C2PA focuses on provenance metadata; PixelSeal focuses on tamper-evident integrity of the file itself.