A few years ago, a client I’d worked with on several projects reached out in a panic. His Instagram page had been taken down, and he was sure it was because of copyrighted music in one of the videos I’d edited. The whole strory is not about just one video but…

I went back through everything, old project files, exports, timelines and spent about three and a half hours reconstructing what I’d actually used. It turned out he’d been working with more than one editor around the same time, and the music causing the problem wasn’t in any of my projects. Because I still had the original files, I could send them over and he could see for himself.

That whole afternoon stuck with me, not because of the mistake. There wasn’t one at least on my end.

But because of how close it came to being unsolvable. If I hadn’t kept those files, there would have been no way to prove it either way. And that’s the real issue: when you hire a video editor, you’re not just trusting them with your footage. You’re trusting them with assets that carry legal weight long after the project ends.

Good editors already take this seriously. But as a client, you should stay in the loop too.

(none of this is legal advice. For anything with real money or real risk on the line, that’s a conversation with a lawyer, not my blog post)

A video can be live for months, sometimes years, before anything happens. It performs well. Nobody says a word. Then one day a copyright claim appears, or a platform’s detection system flags a track, or the original rights holder challenges the use.

By then, you might not remember who edited the video. You might not remember which stock library the footage came from. And if you’ve worked with multiple editors over the years, the odds of anyone remembering get worse, not better. You’ll recall the video existed, your editor might recall editing it, but neither of you will necessarily recall where every third-party asset in it came from.

That gap is exactly what documentation is for.

“Royalty-Free” Isn’t the Whole Story

If your editor regularly pulls in music, stock footage, sound effects, or graphics, it’s worth knowing which libraries they use. Envato, Epidemic Sound, Storyblocks, Adobe Stock, or something else. The licensing terms between these vary more than most people assume, which is why

“it’s royalty-free” isn’t really enough information.

Royalty-free doesn’t mean copyright-free. It doesn’t automatically cover every type of commercial use, and it doesn’t mean every use is included under every subscription tier. What actually matters is the specific license and what it permits — not the general reputation of the platform it came from.

Most legitimate libraries hand you that information automatically when you download something, whether it’s labeled a download license, a usage certificate, or just a license PDF sitting next to the file. So if your editor tells you, “I used a licensed track,” a completely reasonable follow-up is: “Which library, and do we have the documentation?” That’s not being difficult. That’s just being organized.

Know Whose Account the Subscription Is On

Here’s a question most clients never think to ask: whose account is the asset library subscription actually under? Yours, your editor’s, an agency’s, something shared?

It matters more than it sounds like it should. If a project is an important, ongoing part of your business, it’s worth having the relevant subscriptions under your own account rather than being dependent on a freelancer’s login history if a question ever comes up. And if you are relying on your editor’s subscription, you should at least know what it covers and whether your use actually fits inside those terms.

None of this needs to be complicated. It’s just about knowing where the rights actually come from.

Ask for a Licenses Folder

This is a small habit that pays for itself the first time you need it. When a project wraps, ask your editor to hand over a folder that looks something like this:

PROJECT/
├── Project Files/
├── Footage/
├── Audio/
├── Graphics/
├── Exports/
└── Licenses/
    ├── music-track-license.pdf
    ├── stock-footage-license.pdf
    └── asset-sources.txt

The exact structure doesn’t matter. What matters is that if a video contains third-party assets, there’s a way to trace each one back to where it came from and what it’s licensed for. Even a plain text file works:

Music:
Track: Example Song
Source: Example Music Library
License: Commercial use
Date downloaded: 2026-08-18

Stock footage:
Source: Example Stock Library
Asset ID: 123456
License: Commercial use

Now picture a copyright question landing two years from now. Instead of trying to remember, you open a folder and find the answer already sitting there.

A License Isn’t just a Guarantee. It’s Evidence

Having a valid license doesn’t mean an automated system will never flag your video. Content-recognition tools don’t know the context of your license; a properly licensed track can still get caught by a platform’s automated system. The difference is that you have proof you’re allowed to use it, which matters a great deal when you need to dispute a claim.

Think of licensing documentation less as a shield and more as evidence you’re allowed to use what you published.

It’s Not Just for Music

Music tends to get all the attention, but editors work with plenty of other third-party assets. Sound effects, stock footage, stock photography, fonts, templates, motion graphics, LUTs. Each one can carry its own restrictions. A professional workflow means knowing where something came from before it goes into the timeline, not just after someone asks.

Stay Informed But Don’t Micromanage

You don’t need to approve every track before it lands in your editor’s timeline, and you definitely don’t need to become a licensing expert. But it’s worth knowing which asset libraries your editor uses, who owns the subscriptions, and whether the licenses actually cover what you’re using them for. Ask for that Licenses folder when a project wraps. These are small habits, and they’re the kind you only regret skipping once…

usually right when you need them most.

It took me three and a half hours to reconstruct a project I already knew, on a system I already understood, as one of the two editors involved. Now imagine the same question landing on a three-year-old project, an editor who’s no longer around, and ten different hard drives. A saved PDF starts to look very cheap by comparison. And worse, there are more than 2 editors that dealt with similer projects. Things get real messy really quick.

Because two years from now, if someone asks where a piece of music came from, it’s much better to hand them a file than a guess.

_

  • this blog was originally written on November 27, 2025 as my instagram story. And edited/re-published here on August 29, 2026.