Paying for the Video Does Not Automatically Buy the Copyright
Most buyers assume commissioning a video means owning every part of it. US copyright law is narrower than that. The Copyright Office's Circular 30, Works Made for Hire, states the rule plainly: work produced by an independent contractor counts as a work made for hire only if it falls into one of nine specific statutory categories and both parties sign a written agreement saying so. Without that signature, the person who made the work is the author of it. Circular 1, Copyright Basics, adds the other half — a transfer of exclusive rights must also be in writing and signed by the owner.
Nobody litigates over a YouTube edit. What actually happens is duller and more expensive. You want to re-cut a video eighteen months later for a new offer, you email the editor who made it, and you get silence, a dead Dropbox link, or a quote to rebuild something you already paid for.
Across 10,000+ delivered editing projects sitting behind 200M+ views and over $10M in client revenue, this is the most common thing new clients arrive without. They have the videos — those are on YouTube. What they cannot produce is anything that would let a second editor work on them. That is a different problem from YouTube channel access and permission roles, which governs who can publish. This one governs who can rebuild.
What follows is standard industry practice and the language worth asking for, not legal advice. For anything with real money attached, have a lawyer read the contract.
Four Different Things People Mean by "My Files"
"Send me my files" sounds like one request. It is four, and they behave completely differently:
| Layer | What it actually is | Handed over by default? | What losing it costs you |
|---|---|---|---|
| Deliverables | The exported MP4s, thumbnails, caption files | Yes — this is what you bought | Nothing; you already have them |
| Project file | The .prproj, .drp or .fcpbundle timeline with every cut, title and effect | Rarely, unless named | Every future edit starts from scratch |
| Source media | Raw footage, audio stems, graphics, proxies, brand assets | Sometimes — often because you supplied it | No future edit is possible at all |
| Licensed assets | Music, stock clips, fonts, plugin and template licences | Almost never | Exposure on clips you already published |
The gap that catches people is row two. A typical engagement defines delivery as the finished video, which is entirely reasonable — it is what the client watched, approved and paid for. But that definition quietly leaves the timeline, the source media and the licences in three different places, none of which are yours, and none of which anybody thinks about until the day you need them.
A Project File on Its Own Is an Empty Timeline
Here is the part buyers consistently underestimate: the project file is a set of instructions, not a video. Open a .prproj on a machine that does not have the media and you get a timeline of offline clips — right structure, no picture. The same is true of a DaVinci Resolve database entry without its media pool.
So "just send me the project file" is not a request that produces anything usable. Four dependencies have to travel with it:
- The media, in the same relative folder structure, or every clip needs relinking by hand
- The fonts, because a missing typeface silently substitutes and your lower thirds reflow
- The plugins and templates, since a timeline built on a paid transition pack opens broken without it
- A compatible application version, because project formats move forward and not backward
Both major NLEs have a built-in answer. Premiere Pro's Project Manager consolidates a sequence and its media into a single self-contained folder (Adobe's Premiere Pro user guide covers the consolidate and archive options), and DaVinci Resolve exports a .drp project archive that bundles the timeline with its media. Ask for the archive, not the project file. The distinction is the difference between a handover that works and one that technically happened.
The Licence Layer Is the One That Bites Later
This is the quiet one. Subscription music and stock libraries license to an account, not to a video. If your editor scores your channel from Epidemic Sound on their own subscription, the clearance is attached to their account and their registered channels — and when that subscription lapses or the relationship ends, the cover over your already-published back catalogue goes with it. The first sign is usually a Content ID claim on a video that has been live and monetised for a year. Our guide to YouTube music licensing and Content ID covers what to do when a claim lands; the cheaper move is never to be in that position.
The same logic applies to stock footage, motion templates and licensed fonts. The fix is boring and works: buy the licences on your own account and give your editor seat access, rather than reimbursing theirs. You pay the same money and the paperwork ends up in your name.
Six Things to Settle in Writing Before Work Starts
- Copyright in the finished video transfers to you on final payment — stated explicitly, in writing, signed. Not implied by an invoice.
- Deliverables are itemised, and the project archive is one of the line items. "One edited video" is not a deliverables list.
- Licences are bought on your account, or the agreement names which ones are not and what that means when the engagement ends.
- Source media has a home you control — your cloud storage, your drive — and the agreement says who pays for it.
- A retention period is named. Most studios keep projects 30 to 90 days after delivery before archiving to cold storage. Ask what happens on day 91 and what retrieval costs.
- Offboarding is defined before onboarding. What you receive, in what format, within how many days of the relationship ending.
Marketplace engagements are where this most often goes unstated, because the platform's default delivery definition is the exported file and nothing else — one of the structural trade-offs in our freelance marketplaces comparison. It is not a trap, but it is a default, and defaults hold unless you write over them. This is also worth asking about during a trial rather than after; our post on how to vet a video editing service treats the answer to "what do I get at the end?" as a signal in its own right, because a shop that has a clean answer ready has done this before.
What a Clean Handover Looks Like
When we close out an engagement, the client receives one folder in their own storage, structured like this:
ClientName_Archive_2026/
├── 01_Deliverables/ # final exports, thumbnails, .srt caption files
├── 02_Project_Archives/ # consolidated .prproj / .drp per video, media included
├── 03_Source_Media/ # original footage + audio, untouched
├── 04_Brand_Assets/ # logos, fonts, lower-third templates, LUTs
├── 05_Licenses/ # receipts + licence PDFs for music, stock, fonts
└── README.txt # app versions, plugins used, folder conventionsNothing exotic — it is the same video file management structure run all the way to the end instead of abandoned at delivery. The one step people skip is the one that matters: open the archive on a different machine before you accept it. An archive nobody has tested is a claim, not an asset, and the wrong moment to discover it is broken is the day your current editor stops replying.
For anyone whose videos have a long second life, this stops being housekeeping and becomes the whole ballgame. Course creators re-cut modules every time pricing, branding or a platform changes, and the ones who kept their archives update a lesson in an afternoon while the ones who did not re-shoot it.
The Bottom Line
Paying for a video buys you the video. The timeline, the source media and the third-party licences are three separate things that stay where they were made unless your agreement names them. Ask for a consolidated project archive rather than a project file, buy your music and stock licences on your own account, and test the handover on a second machine before the relationship ends — not after.
