Forensic watermarking: your invisible proof of delivery.

When you deliver a video through Coredon, your file is invisibly marked before it reaches the client. There's nothing visible on the screen — no banner, no logo, no overlay. The watermark is embedded in the video data itself, imperceptible to the human eye.

This is called forensic watermarking, and it's the same technology used by major streaming platforms to track unauthorized distribution of premium content. For video editors, it serves a different but equally important purpose: proving that you delivered what you delivered, when you delivered it, to whom.

What the watermark contains.

Every watermark embedded by Coredon contains a unique identifier tied to your project — the client, the timestamp of delivery, and the specific file version. This information is encoded into the video at the pixel level using a technique that survives most forms of compression, re-encoding, and format conversion.

In plain terms: if a client downloads your file and later claims they never received it, or tries to use the footage without releasing payment, the watermark is proof. It ties that specific file to that specific project, that specific date, and that specific delivery through Coredon.

Why this matters in a dispute.

The most common dispute scenario in video editing isn't outright fraud. It's ambiguity. A client says the deliverable didn't match what was agreed. They claim they never received a usable file. They say the quality wasn't what was promised.

Without forensic watermarking, these disputes come down to your word against the client's. With it, Coredon's dispute team can verify exactly what file was delivered, when it was accessed, and whether it matches the project specifications locked in the original contract.

This doesn't mean every dispute resolves in your favor automatically. It means the resolution is based on evidence, not whoever argues more convincingly.

What it doesn't do.

Forensic watermarking is a delivery verification tool. It confirms what was delivered and when. It doesn't prevent a client from downloading the file — that's not the goal. The goal is to create an immutable record that backs up your delivery claim if anything goes wrong.

The full protection stack on Coredon is: escrow (payment is locked before delivery), protected proxy (files route through Coredon's infrastructure), forensic watermarking (every delivered file is traceable), and legally binding contracts (scope and terms are locked before work starts). Each layer handles a different risk.

It happens automatically.

You don't need to do anything to enable forensic watermarking. Every file delivered through Coredon is watermarked automatically as part of the delivery process. There's nothing to configure, no plugin to install, no extra step.

You upload your final cut. Coredon handles the rest.