Drop up to 20 images: SHA-256, dimensions, metadata status and carrier scores in one forensic table, exportable with release ID and planned method. Batch thinking without the app.
Turn a final delivery folder into a documented, repeatable preflight decision.
02Try
Audit the pack, fix tagged or weak files, and export the report with the release notes.
03Prove
You have a manifest that can explain what shipped, when, and under which method.
Loading the interactive demo for "Audit the whole pack the night before"… The lesson text below is already here. The hands-on part loads next (requires JavaScript).
Read the result correctly
Three outputs, three different claims
The labels are deliberately not interchangeable.
Visual similarityNot the audit goal
The report describes release inputs.
Carrier estimatePer-file context
A score helps plan a test.
Payload recoveryNot claimed
The exported report must not overstate survival.
Practice kit
Take the lesson outside the sample
Fictional fixtures only · downloads stay on your device
Route-test kit
A fictional original, transformed leak, delivery template, and evidence worksheet.
A plain-text checklist for preserving the exact file and context.
Look for
Similarity can support triage without proving a payload survived.
A route test must include the actual export or delivery transformation.
The evidence record is useful even when the hidden ID cannot be recovered.
All files and identities are fictional training fixtures; they are not evidence of a real leak.
Studios don't eyeball packs. They put them in a table. Drop up to twenty files and get SHA-256, dimensions, metadata status and carrier scores per file, exportable as a forensic CSV.
This is the closest free taste of Distribution mode: the same gates, run by hand, once per pack.
Reading the table
Tags column: any number above zero ships location and device data unless you strip it. The metadata chapter is the fix.
Carrier column: green means standard methods, amber means robust, red means verify with a round-trip before trusting.
Unreadable rows are usually HEIC or TIFF. Convert to delivery formats first, then re-audit.
The night-before ritual
Audit, strip tagged files, assign methods by carrier tier, export the CSV into your release notes. Four steps, roughly ten minutes, fewer avoidable retractions.
The exported report is your paper trail: it records the source and output names, SHA-256, metadata status, carrier score, release ID and planned method. Keep it beside the release notes so a later leak has a file-level starting point.
Takeaways
Audit packs as tables, not guesses: every file gets dimensions, tags, and a carrier score.
Strip tagged files, assign methods by carrier tier.
Export the report into your release notes for the paper trail.
Check yourself
Optional, local, instant. 0/2 answered.
The tags column shows 14 on three files. What now?
What goes into your release notes?
Evidence checkpoint
Prove the release record
Lab first
Export a release report that someone can inspect after a leak.
The report should describe what shipped, not what you intended to ship.
A saved report is the paper trail for the release.
The real route test still belongs beside the pack manifest.
For your niche
Photographers
Wedding deliveries run hundreds of files: audit in 20-file batches per gallery section and staple the CSVs together.
Subscription creators
Monthly packs are small enough to audit whole. Make it the last step before the drop goes live.
Illustrators & designers
Client revision folders accumulate strays. Audit the final delivery folder, not the working one.
Demo transcript
Questions creators ask
Keep handyLearn glossary11 recurring terms
Carrier
The image content that offers texture or edges where a watermark can be tested.
A carrier estimate is not a survival result.
Delivery ID
An identifier for one particular delivery event or copy.
Keep it separate from the stable recipient ID.
DCT
A transform that represents image blocks as spatial-frequency coefficients.
The Learn visualization is illustrative.
LSB
Least-significant-bit hiding: changing the smallest binary bit of pixel values.
It is fragile under common re-encodes.
Metadata
Attached file information such as EXIF, GPS, software, color, and creation tags.
Metadata hygiene does not protect pixel payloads.
Payload recovery
Successfully reading the hidden identifier from the exact leaked file.
This is different from visual similarity or carrier capacity.
Re-encode
Decoding and saving an image again, often with a different format or quality setting.
It can change pixels, metadata, dimensions, and color behavior.
Recipient ID
A stable opaque identifier for the person or account receiving a copy.
Never recycle it between recipients or releases.
Release ID
An identifier for a batch, edition, or release of content.
One recipient may receive multiple releases.
Similarity
A visual or perceptual comparison suggesting whether two files resemble each other.
It is triage, not attribution.
Stable map
A validated delivery record connecting a recovered ID to one unambiguous recipient.
Duplicate IDs break attribution.
Workflow Upgrade
Automate this for every drop
You just audited 20 files by hand. Foddo Distribution runs these same gates per subscriber copy automatically, at any pack size.
