SteMi Labs
Read Q&A Try the demo →
Live Demo • API available

Trusting Images in the AI Era

SteMi Labs • PixelSeal

When trust matters, PixelSeal helps detect whether an image has been modified—even if metadata is removed.

Trust should live inside the file—not around it.
1. Seal 2. Share 3. Verify
Try the demo → How it works Q&A
Lossless formats: PNG / WebP / BMP / TIFF JPG / HEIC uploads are converted automatically Deterministic verify: Verified / Modified
HOW PIXELSEAL HELPS

Detect image modifications with confidence

PixelSeal embeds tamper-evident integrity directly into an image. If the image changes, verification detects it.

Designed for integration into existing workflows through the PixelSeal API.

What PixelSeal is not
PixelSeal is not “AI detection.” It does not determine how an image was created. It detects whether a sealed image has been modified.
See the demo flow ↓
The challenge

How do you know an image hasn't been changed?

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.
Product

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.

Core  Seal a master image
Core  Verify integrity anytime
Core Does not alter the visual appearance of the image
Developer API  API for workflow integration — view docs
Optional Embed signed metadata, identity, or certificates directly into the image
How it works

Three simple steps

1

Seal

Seal a master image. Lossless formats are sealed directly; JPG and HEIC are converted automatically.

2

Share

Use and distribute the sealed image as your authoritative master copy.

3

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, JPG/JPEG).
Use cases

Where Image Integrity Matters

Examples of workflows where PixelSeal may help establish trust in digital images.

Insurance & Claims Documentation

Help establish trust in images used for claims, reviews, and dispute resolution.

Legal Documentation

Potential fit for evidence, intellectual property, and legal documentation workflows.

Scientific & Research Imaging

Potential fit for research data, laboratory imaging, and scientific archives.

Fine-Art Photography

Seal exhibition-quality images for archival and provenance workflows.

Gallery & studio archives

Maintain a trusted archive of high-value assets with verifiable integrity.

Limited-edition digital art

Protect the original digital master used to produce editions.

Positioning

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.

C2PA

Provenance and content history

  • Tracks origin, edits, and workflow history.
  • Relies on signed metadata and ecosystem support.
  • Useful when provenance travels with the asset.
PixelSeal

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?
C2PA tells you how an image was created.
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.

Prototype demo

Try the concept in 60 seconds

  1. Upload an image — JPG/HEIC are converted automatically.
  2. Seal it and download the result.
  3. Make a small edit and re-verify to see verification fail.
Open demo → Developer API Read Q&A

Demo URL: https://demo.stemilabs.com/

Q&A

Quick answers

What formats are supported?

PixelSeal seals lossless formats (PNG, WebP, BMP, TIFF). JPG and HEIC uploads are accepted and converted to PNG before sealing.

Why not JPEG or HEIC?

JPEG and HEIC are lossy formats, meaning pixel values can change when the image is saved or re-saved. PixelSeal relies on stable pixel data for verification, so it seals images in a lossless format. JPG and HEIC uploads are automatically converted to PNG before sealing.

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.