Protect your photos before publishing: a practical guide for photographers and visual creators

You posted a photo on Instagram. Three days later, a brand is using it without credit. You contact their legal team, and the response comes back: "Prove it's your photo."

Without dated proof, you're stuck. When was your RAW file created? Who says your EXIF is credible? Was your Instagram post really the first one, or did someone repost it before you?

This happens to thousands of photographers, videographers and illustrators every year. The good news: you can prevent it in about 10 minutes per shoot, without becoming a lawyer or a blockchain expert.

Why traditional protections fall short

EXIF data: useful but fragile

EXIF metadata (capture date, camera model, GPS) is the first thing photographers think of. The problem: it can be edited with any metadata tool, and most platforms (Instagram, Facebook, X) strip it on upload.

In a dispute, opposing counsel can legitimately challenge EXIF as the sole proof. It remains a useful clue in a broader file, not standalone evidence.

Watermarks: deterrence, not protection

A visible watermark discourages opportunistic theft. But with current editing tools (including generative AI), a watermark can be removed in seconds. And a subtle watermark doesn't stop anyone from cropping the image.

Watermarks prove nothing legally. They don't establish a date and don't demonstrate authorship.

Online publication: a vague timestamp

Publishing on social media creates a date, but you don't control the server or the metadata. If someone published your photo elsewhere before you (after stealing it from a preview, a client delivery, a shared Drive), it's your word against theirs.

What real proof of authorship looks like

Solid proof rests on three pillars:

1. A frozen file: a specific version of your photo that doesn't change.
2. A hash (SHA-256): a unique mathematical fingerprint of the file. If a single pixel changes, the hash changes.
3. A verifiable timestamp: a date anchored in an independent mechanism (such as the Bitcoin blockchain via OpenTimestamps) that no one can alter after the fact.

With these three elements, you can demonstrate that this exact file existed at this date and has not been modified since.

Practical workflow: from shutter to proof

1. 1
   Shoot and keep your raw files

   Always keep your RAW files (CR3, NEF, ARW, RAF) or source files (PSD, AI, 16-bit TIFF). These are your irrefutable originals: they contain sensor metadata and cannot be fabricated from a JPEG.
2. 2
   Select and edit as usual

   Work in Lightroom, Capture One, or your usual tool. Nothing changes in your creative process at this stage. Keep the XMP sidecar file or catalog that logs your adjustments.
3. 3
   Freeze the files to protect before publishing

   Export final versions (high-resolution JPEG, TIFF, or both). Name them clearly: shoot-brand-X_001_final.jpg. For video rushes, export the master in ProRes or H.265.
4. 4
   Build the proof folder for the shoot

   Create a folder PROOF/2026-04-shoot-brand-X/ containing: selected RAWs, final exports, XMP/metadata, and a context.txt file with date, location, client, and brief.
5. 5
   Zip and timestamp

   Compress the folder into a stable ZIP archive. Upload it to LegalStamp: the SHA-256 hash is computed automatically, the timestamp is anchored via OpenTimestamps, and you receive a proof receipt.
6. 6
   Publish or deliver with confidence

   You can now post on Instagram, deliver to the client, or send to the agency. Your proof of prior authorship already exists and covers the exact version you're sharing.

Proof folder structure

Organize each shoot or project with a clear, stable directory layout:

PROOF/
└── 2026-04-shoot-brand-X/
    ├── originals/
    │   ├── DSC_0142.NEF        (RAW)
    │   ├── DSC_0142.xmp        (Lightroom sidecar)
    │   ├── DSC_0187.NEF
    │   └── DSC_0187.xmp
    ├── exports/
    │   ├── shoot-brand-X_001_final.jpg
    │   └── shoot-brand-X_002_final.jpg
    ├── context.txt
    └── receipt/
        └── 2026-04-shoot-brand-X.zip.ots

The context.txt file contains a few lines:

• Date and location of the shoot
• Client or project name
• Brief or assignment (one sentence is enough)
• Equipment used (camera body, lenses)
• Key file names

This folder is your proof archive. Keep it as-is -- don't modify files after timestamping.

Which formats to keep and why

What this proves and what it doesn't

What you can demonstrate:

• That this photo file existed in this exact form at the timestamp date
• That the file has not been modified since (integrity verified by the hash)
• That you had the RAW, the editing settings, and the production context

What timestamping alone doesn't prove:

• That you were physically behind the camera (though the combination of RAW + EXIF + context strongly supports that conclusion)
• That no other person had a similar image (rare but theoretically possible)

In practice, a photographer presenting the RAW file, XMP sidecars, shooting context, and a timestamped proof of prior ownership has a case that's very hard to dispute.

Real-world scenarios where this method saves you

Unauthorized use by a brand: you spot your photo in an ad campaign. You present your timestamped receipt predating the campaign, the original RAW, and the context. The brand can't claim the image came from their internal library.

Dispute with a client: a client contests your authorship of photos delivered six months ago. Your timestamped archive proves the files existed before the delivery date, with RAW files and settings that only the photographer could possess.

Theft between photographers: a competitor publishes your shot under their name. Your proof of prior authorship is dated, verifiable, and independent of any platform.

FAQ

Conclusion

Photo theft is a structural problem, not an accident. Every image published without proof of prior ownership is an image you may not be able to defend.

The habit to build: shoot -> keep the RAWs -> freeze the exports -> zip -> timestamp -> publish. Ten minutes per project, and you have a file any lawyer can work with.

LegalStamp handles the technical part (hash + timestamp + verifiable receipt) so you can focus on what you do best: creating images.