Skip to content
EU AI Act Article 50 is in force. Grace period for existing AI systems ends 2 Dec 2026.EU AI Act Article 50 is in force. The grace period ended on 2 Dec 2026. Check your exposure →

com.originalpictures.pixelseal.1

Meta PixelSeal image watermark: Original Pictures' invisible image watermark, built on Meta FAIR PixelSeal, with its own payload layout, calibration and detection threshold. Not interchangeable with other deployments of the same model.

  • 61-bit identifier in 256 model bits
  • Encoded media types: image/avif, image/jpeg, image/png, image/tiff, image/webp
  • Registration requested with the C2PA soft binding algorithm list

Identity

FieldValue
Algorithm identifier (alg)com.originalpictures.pixelseal.1
TypeWatermark
Decoded media typeImage
Encoded media typesimage/avif, image/jpeg, image/png, image/tiff, image/webp
Underlying modelMeta FAIR PixelSeal
Provider identity and versioncom.meta.pixelseal 1.0-870ca7fb-s0.15-0.25-repeat4-crc12-61b-sealer.v1
API value (watermark_algorithm)pixelseal (the default for image when a request names none)
Registry entrypixelseal-sign09-2
Payload61 logical bits in 256 physical bits
Error correctionop.repeat4-crc12.v1
Strength ladder0.15, 0.2, 0.25
Calibrationop.pixelseal-sign09.2.calibration.v1
Detection thresholdop.metaseal.repeat4-crc12-agreement-0.80-crc2.v1
Runtime revisionop.image-bindings.sign09.2
LicencesCode: MIT. Weights: MIT (facebookresearch/videoseal README: all models MIT).

Model checkpoints

Every file the runtime loads is pinned by SHA-256; a file with any other hash is refused.

FileSHA-256SizeSource
pixelseal.pth0c5665cff20eb6ce1b5aaa7d91c19dafb418bfee32d02dd3344e4ed60d9d75bd1237.4 MBdownload

Payload and error correction

The 61-bit identifier is written 4 times, followed by a CRC-12 over it, in the model's 256 bits. The identifier is an opaque record number issued by Original Pictures for one signed file. It carries no personal data and no content of the file, and on its own it means nothing outside Original Pictures' records.

Strength

Starts at 0.15 and steps up (0.15, 0.2, 0.25) only when the lighter mark does not read back. Every strength must keep the picture above a PSNR floor of 36 dB; an image that cannot be marked within it is refused, not marked harder. Per request, watermark_strength picks a slice of the same ladder: subtle 0.15; balanced 0.15, 0.2, 0.25; robust 0.15, 0.2, 0.25. No request can go above the qualified ladder.

Marks written by an earlier lane of the same model are read the same way and resolve to the same records: pixelseal (superseded for new jobs; model version 1.0-870ca7fb-s0.15-0.25-repeat4-crc12-61b, calibration op.pixelseal-sign09.calibration.v1, runtime op.image-bindings.sign09.1).

How detection works

The detector reads the model's bits, adds up the copies of the identifier (soft combination of the model's scores) and reports a detection only when the combined codeword agrees on at least 80% of its bits and at most 2 of the 12 CRC bits disagree. A detection is then looked up by exact equality among the recorded identifiers of the same algorithm, calibration and threshold, within the account that signed the file.

What a positive result means

A match means the file carries a watermark that leads to a record the signer's account made when it signed a file. It points to that file's C2PA manifest, which declares its origin. It is a probabilistic lead, not cryptographic proof: a watermark can be damaged by heavy edits or targeted attacks, and it says nothing about whether the content is true. The signed manifest, where it survives, is the proof.

False matches

On Original Pictures' 2026 benchmark (configuration PixelSeal@0.15), the production rule (key_match: a detection counts only when the decoded identifier exactly matches a recorded one) produced 0 false matches in 17,340 trials on unmarked media, a 95% upper bound of 1.73 × 10^-4 per check. Under the gating attack (jpeg75) the identifier was read back at 98.8% bit accuracy. These are measurements on a fixed test set, not a guarantee for every file.

How to check a file

  • Content Credentials. Any C2PA-aware validator can read and check the manifest of a file that still carries one, without calling Original Pictures.
  • The watermark. Watermark recovery runs inside a verification: POST /v1/verifications on the Original Pictures API. When no manifest can be read, the verification searches the watermark and reports a single match as recovery-only (VALIDATION_RECOVERY_ONLY), never as cryptographic validity. Recovery searches only the bindings of the account that runs the verification. See lookup and recovery and watermarks.
  • There is no public soft-binding resolution API. A third party can check a file on the signer's hosted verify page, if the signer publishes one; that page searches the signer's own watermarks only when the signer has switched recovery on (recover_own_assets). Otherwise, contact the signer or us.

Relation to C2PA

When a soft-binding algorithm has an identifier on the C2PA soft-binding algorithm list, the manifest can carry a c2pa.soft-binding assertion that names it in its alg field, and the watermark action is c2pa.watermarked.bound. Registration for com.originalpictures.pixelseal.1 has been requested with the C2PA soft binding algorithm list; no identifier has been assigned yet. Until one is, files watermarked with this algorithm record the action c2pa.watermarked.unbound and carry no watermark soft-binding assertion for it. This page is the entry's informational URL.

Status and contact