What to agree with a YouTube editor before the first video
A YouTube editor contract should settle 11 points: deliverables and runtime, style references, file transfer, turnaround, revision rounds, feedback, music and asset licenses, thumbnails, payment, file ownership and how either side ends it. I settle these with every new channel (1,250 long-form videos tracked on YT Jobs); a shared doc both sides reply "agreed" to is enough.
What should a YouTube video editor contract include?
Agree on eleven things before the first edit: exact deliverables and runtime, style references, how files move, turnaround, how many revision rounds and what counts as one, how feedback is given, who licenses music and assets, whether thumbnails are included, when payment happens, who owns the files, and how either side can end things.
None of this needs a lawyer. A shared doc or a single email thread that both of you reply "agreed" to is enough for most channels. What matters is that it is written down before footage changes hands, because every one of these points is easy to settle when nobody is annoyed yet and hard to settle after a missed upload date.
Do I need a contract with my YouTube editor?
You need the terms in writing, not necessarily a lawyer. For most channels a shared doc or one email thread that both sides reply "agreed" to is enough, as long as it exists before footage changes hands. For large sums, sponsor contracts or rights to a catalogue of videos, have a lawyer check the final version. The fill-in agreement template further down covers all 11 points.
What exactly is the editor delivering?
"Edit my video" is not a deliverable. Write down what lands in your folder when the job is done:
- Runtime target. A range, not a number: "18–22 minutes". Say whether the editor may go shorter if the footage doesn't hold up. Most arguments about pacing are really arguments about length.
- Export specs. Resolution, frame rate and aspect ratio. If you upload in 4K, say so, or you will get a 1080p file.
- Extras. Chapter timestamps, a caption file (SRT), a clean version without music for sponsors, Shorts cut-downs, room for an end screen. Each of these is extra work, so each needs to be named, not assumed.
How do you show the editor the style you want?
Words like "fast", "clean" or "like the big channels" mean different things to every editor. Send two or three reference videos with timestamps and a note on what to take from each: "the zoom punch-ins at 2:14", "the way captions pop at 5:40". Add one of your own videos that you think worked, and a short "don't" list (no whoosh on every cut, no meme sound effects, no red text).
If you want a structure for this, the free YouTube editor brief template walks through the sections a brief should have.
How will files get to the editor, and back?
Pick one place and keep everything there: a Google Drive or Dropbox folder, or a review tool such as Frame.io. Agree on a simple folder layout (raw footage, audio, brand assets, exports) so nobody hunts through "Final_final_v3".
- Raw audio. If your mic records separately, send the separate track. It is usually cleaner than camera audio.
- Brand kit. Fonts, logo, colours, lower-third style, intro and outro files. Missing fonts are the most common reason a first draft "looks off".
- Project files. Decide now whether you want the editor's project files (Premiere Pro, DaVinci Resolve, After Effects) handed over. Many editors don't include them by default. If you do want them, ask for a collected project with all media copied into one folder; in Premiere Pro that is the Project Manager's "collect files" option. A bare project file without its media is close to useless, and a project generally opens only in the program it was made in, so check you have it: the guide to editing software for YouTubers and the Premiere vs DaVinci Resolve vs Final Cut vs CapCut comparison cover the main options.
- Retention. How long the editor keeps your raw footage after delivery, and when it gets deleted.
- Channel access. If the editor will upload, schedule or add end screens, give them a YouTube channel permission role instead of your Google password. How to give your editor access to your YouTube channel explains the roles.
How fast is turnaround, and when does the clock start?
Agree on two numbers: time to first draft and time per revision round. Then agree on when the clock starts. The honest answer is "when all files and the final brief have arrived", not "when you sent the first message". If a sponsor segment or a missing clip arrives on day two, the clock restarts. Say whether weekends count, and name your real publish date so the editor can tell you right away if it is tight.
How many revision rounds, and what counts as one?
This is the point that causes the most friction, so be precise. A good working definition: one revision round is one consolidated list of notes on one draft. Five separate messages over two days are still one round if you send them together; they become five rounds if the editor has to re-export after each one.
Then agree on what is not a revision:
- Fixing the editor's mistakes (a sync slip, a typo in a caption, a missing section from the brief) should never use up a round.
- New work is not a revision either: a rewritten script, re-recorded voiceover, new footage, or a change of direction after the draft ("actually, let's make it a top 10"). Agree up front that this is quoted separately.
For how many rounds is typical and why, see how many revisions a YouTube editor should include.
How should you give feedback on a draft?
Timestamped comments beat paragraphs. A review tool such as Frame.io lets you click on the exact frame and leave a note, so "the joke at 7:32 lands late, cut the pause" can't be misread. If you use Drive, a numbered list with timestamps does the same job.
Three rules make feedback cheap for both sides: one person gives the final notes (not you, your co-host and your manager separately), each note is marked must-fix or nice-to-have, and notes describe the problem rather than only the fix ("this drags" is more useful than "add a zoom here"). More on this in how to give editor feedback that gets results.
Who handles music, sound effects and other assets?
Music licensing is where a finished video can still get a copyright claim. Music subscriptions are generally licensed to the account holder and the channels registered on that account. If the editor uses their own subscription, check that it actually covers your channel; if it doesn't, the safer setup is that you hold the subscription and share access.
The same question applies to stock footage, sound effects, fonts and archival clips. Agree who pays for them, who keeps the license records, and what happens if a claim appears after upload (usually: the editor swaps the track and re-exports at no charge if they chose it).
Are thumbnails part of the job?
Say yes or no in writing. Thumbnail design is a different skill from editing, and many editors don't offer it, or offer it as a separate item. If the editor won't make them, ask for a handful of clean, high-resolution frame grabs of the key moments so your designer has material. The trade-offs are covered in do YouTube editors also make thumbnails?
When and how do you pay?
Agree on four things: per video or monthly, how much is due before work starts and how much on delivery, how many days you have to pay an invoice, and in what currency and method. It also helps to say what happens with a video that gets cancelled halfway (usually: you pay for the work done). The common arrangements and the red flags on both sides are in should I pay a YouTube editor up front or after delivery? If you work to a fixed monthly amount, the per-video math is in what $300 a month covers and what $1,000 a month covers.
Who owns the final video and the project files?
The normal arrangement is simple: once a video is paid for, you own the final export and can use it anywhere, including re-cuts and Shorts. Put two more lines in writing. First, whether the editor may show the video in a portfolio, and from when (after it is public is the usual answer). Second, whether the project files are yours too, or stay with the editor as their working material. If the video contains unreleased sponsor deals or announcements, add a line about confidentiality.
What happens if it doesn't work out?
Nobody likes writing this part, which is exactly why it should be written. Agree how much notice either side gives, that work already delivered is paid for, and that all raw footage and any files you paid for are handed back promptly. A first video or trial run is a good place to find out whether the fit is right before committing to a monthly schedule. The first 30 days of onboarding a new editor covers what to look for during that period. If it does end, how to end things with an editor without burning bridges covers the notice, the message and the handover.
The copy-ready checklist
Paste this into a doc, fill in each line, and have both of you reply "agreed". If you want the full written version, use the fill-in agreement template further down.
- Deliverables: runtime range, resolution and frame rate, and extras (chapters, SRT captions, Shorts, sponsor-clean version, end-screen space).
- Style: 2–3 reference videos with timestamps, one of your own videos that worked, and a "don't" list.
- File handoff: where files live, folder layout, separate audio, brand kit and fonts, and whether project files are handed over (collected with their media).
- Turnaround: time to first draft, time per revision round, when the clock starts, weekends yes/no, your publish date.
- Revisions: number of rounds, what one round is, and what counts as new work.
- Feedback: tool (Frame.io, Drive comments or a timestamped list), one decision-maker, must-fix vs nice-to-have.
- Music and assets: whose subscription, which channels it covers, who keeps license records, who fixes a claim.
- Thumbnails: included, separate, or not offered (and frame grabs if not).
- Payment: per video or monthly, split between start and delivery, invoice terms, currency and method, cancelled-video rule.
- Ownership: final export is yours on payment, portfolio permission, project files, confidentiality.
- Exit: notice period, payment for work done, files returned.
A short example brief
This is what a first-video brief can look like once the terms above are settled. The channel is made up; swap in your own details.
Video: "I spent 30 days learning to cook like my grandma"
Runtime: 16–20 min. Cut harder if the middle drags.
Export: 4K, 30 fps, 16:9. Plus chapters and an SRT file.
Files: Drive folder "EP14" (raw/, audio/, brand/, music/).
Use the lav track in audio/, not camera audio.
References:
- [link] 0:00-0:45, copy the cold open: result first, then "30 days ago..."
- [link] 6:10, copy the on-screen recipe cards.
Don't: no whoosh on every cut, no meme sounds, no red text.
Music: from my subscription (login shared), nothing from elsewhere.
Sponsor: 60-90 s read at ~2:30, script in brand/sponsor.pdf.
Thumbnail: not needed. Send 5 frame grabs of the final dish.
First draft by Thursday. Notes as timestamped comments, from me only.
Publish date: Sunday 10 am.
A fill-in agreement template you can copy
The checklist tells you what to talk about; this is the written version you both sign off on. It works with any editor, freelance or studio, for a single video or an ongoing series. Copy it into a doc or an email, replace every [bracket], delete the lines that don't apply, and have both sides reply "agreed". None of the brackets has a "right" answer: every editor sets these terms differently, so fill them in with what the two of you actually agree.
CREATOR–EDITOR AGREEMENT
Creator / channel: [name, channel link]
Editor: [name or studio, contact]
Covers: [one video / every video until either side ends it]
Date agreed: [date]
1. SCOPE
- Video: [working title or series name]
- Type: [e.g. vlog, gaming, documentary, tutorial]
- Runtime: [min]–[max] minutes. Editor may go shorter if the footage doesn't hold up: [yes / no]
- Included: [cut and pacing, on-screen text, sound mix, color, motion graphics, sponsor segment, ...]
- Not included unless added in writing: [thumbnails, Shorts, scripting, uploading, ...]
- Style: [2–3 reference links with timestamps]
- Don't: [things you never want to see]
2. DELIVERABLES
- Final file: [resolution], [frame rate], [aspect ratio], [format, e.g. H.264 .mp4]
- Delivered to: [Drive / Dropbox / Frame.io folder]
- Captions: [SRT file / burned in / none]
- Extras: [chapters] [sponsor-clean version] [Shorts cut-downs: how many] [end-screen space]
- Project files: [handed over, collected with media / not included]
3. TIMELINE
- The clock starts when every file and the final brief are in the shared folder.
- First draft: [number] days after the clock starts.
- Weekends count: [yes / no]
- Publish date: [date]. If files arrive late, the draft date moves by the same number of days.
4. REVISIONS
- Rounds included: [number / until approved]
- One round = one consolidated list of timestamped notes on one draft, sent by [decision-maker].
- Each round comes back within: [hours / days]
- Fixing the editor's own mistakes never uses a round.
- New work (new script, new footage, re-recorded voice, change of direction) is quoted separately.
5. RIGHTS AND OWNERSHIP
- Raw footage, audio and brand assets stay the creator's at all times.
- Once paid, the final export belongs to the creator for any use: re-cuts, Shorts, other platforms (music, stock and archival clips stay under their own licenses).
- Project files belong to: [creator / editor]
- Editor may show the video in a portfolio: [after it is public / never]
- Editor deletes the raw footage: [number] days after delivery.
6. MUSIC, STOCK AND LICENSES
- Music and sound effects from: [creator's subscription, shared / editor's subscription, confirmed to cover this channel / other: ...]
- Stock footage, fonts and archival clips paid for by: [creator / editor / included in the quote]
- License records kept by [name] in [folder].
- Copyright claim on an asset the editor chose: the editor replaces it and re-exports at no charge.
7. CONFIDENTIALITY
- Unreleased videos, scripts, sponsor deals and channel analytics stay private until the creator publishes.
- Channel access, if needed: a YouTube permission role [Editor / Manager], never the Google password.
8. PAYMENT
- Fee: [amount and currency] per [video / month]
- When: [part before work starts, rest on delivery / all on delivery / monthly invoice]
- Method: [PayPal / bank transfer / other]
- Invoices paid within: [number] days
- Video cancelled halfway: the creator pays for the work done so far, measured as [how].
9. IF THE EDIT DOESN'T WORK FOR YOU
- If the last included round still isn't right: [an extra round / pay only for work done / no charge for that video / other: ...]
- Either side can stop with [number] days' notice. Work already delivered is paid for.
- On exit, the editor sends back all raw files, plus project files if agreed, within [number] days.
Agreed (creator): ____________ Date: ________
Agreed (editor): ____________ Date: ________
Two tips for filling it in. Write things that can be checked, not adjectives: "first draft by Thursday if the files are in by Monday" settles a question, "fast turnaround" doesn't. And if a line feels awkward to write, section 9 usually, that is the line you most need. This is a plain-language agreement, not a lawyer-drafted contract.
How I set these terms with my own clients: a free 1-minute test edit first, no contract, a quote for each video, the first video in 1–5 days and each video after that in 1–2 days, revisions until you're happy, each round back in under 24 hours, and if after two revision rounds the edit still isn't right, you don't pay the second invoice; a video is booked with 50% or 100% up front, by PayPal or USDC, in USD. That is one editor's version, not a market standard: your terms with any editor can look completely different.
How this was written
This checklist comes from the points that actually come up when starting work with new channels, across 1,250 long-form videos tracked on YT Jobs. It contains no survey data or industry statistics; the advice is practical, not a legal template. For anything involving large sums, sponsor contracts or rights to a catalogue of videos, have a lawyer look at the final version.
Also worth reading: how to record gameplay so your editor can do more and a series style guide template.