
Theo Brennan
Editor

To make a documentary YouTube video alone, you need a subject, a computer, a quiet room and a plan for what goes on screen. You don't need a crew, camera kit or paid software for the first one. This is the route, in the order that keeps you from abandoning the video halfway through the edit:
Pick a format you can finish alone. For most people that is narration over found visuals: archive footage, stock, photos and documents.
Narrow the topic to one story with a single central question.
Research against a list of 15 to 20 questions, then stop.
Write the script in two columns: what is said, and what is on screen beside it.
Find or make the visual for every line before you open the editor.
Record the narration somewhere soft and quiet, like a clothes closet, in short chunks.
Assemble the cut in passes. Do it by hand in a free editor, or paste the script into VidRush and finish the first cut it gives back.
Write a title and thumbnail, upload, and note where the hours went so video two is faster.
Budget roughly 35 to 75 hours for the first one. That is an estimate, added up stage by stage, so treat it as a planning range. Experience doesn't make it vanish either: Accented Cinema puts each of his film essays at about 80 hours over ten workdays, and he has made more than a hundred of them.
Most guides say the edit eats that time. After years in edit bays, I think the edit only pays a bill the script ran up. Every person, company, place or event the narration names is a picture somebody has to find.
This week we read the transcripts of 19 solo-made documentaries. The typical script named 19 of those things, and in 12 of the videos the narration never once told the viewer what to look at. Each of those named things is a picture somebody had to find. If you decide the picture while you write the line, the edit turns into assembly.
If you don't want to be on camera, you are in good company. None of those 19 videos had narration suggesting the creator ever appeared on screen. You don't need footage you shot yourself either. You need to know where each picture comes from before you press record.
I work at VidRush, which can take the assembly step off your hands. The route above still works from start to finish with free tools, and that is the path this page walks first.
Note: How we researched this. We coded the transcripts of 19 documentary-style videos. Each was 8 to 20 minutes long, published between January 2024 and November 2026, and came from a channel with at least five such uploads and no credited editor, researcher or narrator besides the creator. Transcripts show what the narration names and points at. They don't show what is on screen, and search pulled the sample toward business rise-and-fall stories. We also analysed 61,390 long-form videos from small-to-mid, mostly faceless channels to see how watch time changes with length. Finally, we read creators' first-person accounts of making a specific documentary, and 4 of them qualified with usable time figures.
Choose a format you can actually finish alone
Pick the format by asking where its hours land. A solo creator can realistically make three kinds of documentary, and each one moves the hard work to a different stage. Any of them can work, but one of them is the wrong first choice for most people.
Format | Gear you need | Where the hours go | What usually kills it | Best for |
|---|---|---|---|---|
Desktop narration | A computer, a mic or a decent phone, a quiet room | Finding a visual for every line of the script | A script that names more things than you can find pictures for | Companies, history, true crime: anything with real archive online |
Hybrid: narration plus short pieces to camera | The same, plus a phone or webcam and a window or one lamp | Still mostly finding visuals, with pieces to camera covering lines that have nothing to show | Pieces to camera recorded weeks apart that don't match | Topics with abstract ideas or thin archive |
Filmed: location or interviews | Camera, lights, a lav mic, travel | The shoot day, then finding the story in hours of footage | A shoot that doesn't give you the story you need | People and places you can physically get to |
Where the hours go in each solo format
What I would pick
I would pick desktop narration for video one. Keep the hybrid as a safety valve, in case a handful of lines turn out to have nothing to show and you can tolerate your own face. Desktop narration is the only format where all the risky decisions happen on paper, so changing your mind costs a sentence. If your subject is a place you can walk to and a person who will talk to you, ignore me and film.
Desktop narration moves the work into the visuals
Narrating over found material needs no gear beyond a computer and a quiet room. The hours don't disappear, though. They move into finding pictures. A creator on r/NewTubers described placing over three hundred assets in a twelve-minute documentary. Another said a minute of fitting footage can take hours to find.
I ran my aviation and maritime disaster channel in this format, and this page is built around it. You can go further with it than beginners expect. The Invisible Hand builds 15 to 25 minute economic investigations out of archive clips, highlighted documents and plain typography, with no camera anywhere in the chain.
Cheap pictures may also explain something odd we saw in search. Almost every solo documentary that came back was a company rise-and-fall story, and three different channels had covered the Wirecard scandal alone. My guess, and it is only a guess, is that sourcing drives it: companies leave logos, ads, store photos, annual reports and news footage everywhere, which a medieval siege never did.
The hybrid: cut to yourself when there is no clip
Some lines have no picture: an abstract idea, a transition, a moment nobody filmed. Troy (troyoboyo17) says that is the only reason he started filming himself. When a line has nothing to show, "you can just cut to yourself and just move on." Record those pieces at your desk in one sitting, with a phone and a window, and the edit keeps moving.
Your own face is the cheapest picture you will ever source, because you never have to search for it. It still costs something a voiceover doesn't. You can redo a voice line in thirty seconds, but a piece to camera means light, framing and the same shirt as last time. If the idea of being on screen will stop you finishing, skip it. Plenty of channels never show a face.
Filming puts the work on shoot day
In Robbie Sumantri's solo interview routine, one properly lit interview takes about two hours on site, with four lights and three lens setups. That is one person's system for high-end results, and the two hours don't include travel.
The bigger cost is in how the story gets made. In a filmed documentary, the story usually gets found afterwards, in the edit, from whatever you managed to capture. The edit is the most expensive place to discover that your story does not hold. I would only film a first video if the subject exists nowhere except on location.
Filming doesn't get rid of the per-line work either. You film for each line instead of searching for each line. Two of the creators whose accounts we read filmed their own visuals to match each point, and both still called the visuals the slow part.
If you do shoot, a few habits from cinematographer Jeven Dovey decide whether the clips cut together. Hold every shot still for five to ten seconds. Cover each scene wide, mid and tight. Lock exposure and white balance so the colour and brightness don't shift mid-shot.
Check the credits before you copy a channel
The format most beginners want to copy looks like a lone presenter with a map. In an interview with Jon Youshaei, Johnny Harris says a typical video involves a team of at least four people, with eight weeks of reporting behind it. Before you budget your evenings against a channel you admire, read its description and end credits.

Borrow the shape of a channel like that and leave its scale behind. A single person can keep up one recurring map style. Eight weeks of field reporting takes a newsroom.
Turn your topic into a story with one central question
A topic gives you a reason to start reading. What makes people stay is a specific event, someone or something with a lot to lose in it, and one question the video answers by the end. If all you have so far is a niche, say failed companies or true crime, the documentary channel ideas worth building a whole channel on are a separate decision. A single video needs a story.
Narrow it three times
Narrow the topic in three levels, the way director Darren Durlach does. His is the clearest version of this method I know:
The topic is the broad issue. His example: state-sponsored cybercrime.
The story is one event that carries it: the WannaCry ransomware attack.
The story inside the story is one person with something to lose: a heart patient whose surgery was postponed when the hospital network went down.
Nobody clicks on cybercrime statistics. Plenty of people will watch a piece of code get a surgery cancelled. There is also a practical gain: one patient or one company means fewer names in the script, so fewer pictures to find later.
From a desk, the person becomes a question
You probably can't interview your person with something to lose. The desk version of the same move is one investigative question that the whole video is built to answer. Fern's video on the Berlin aquarium that burst shows the flood in roughly the first 90 seconds. The rest of the video hangs on a single question: how could this have happened?

The question is what buys you the viewer's patience for the background. Johnny Harris's video on Saudi Arabia's trillion-dollar desert city runs past half an hour of resource economics and state finance, material almost nobody would click on by itself. People sit through it because a concrete question in the title promises a payoff. Disaster stories come with their question built in, which is a large part of why they suit solo channels.
Test it in two sentences
Write the pitch before you write a line of script. Luc Forsyth's test is a fill-in-the-blanks sentence: this is a story about X, who wants Y and has to overcome Z to get it. Add a second sentence that states your central question, and you have the whole video in two lines.
Then read it back. If getting through it took several characters, two institutions or a chain of "and" clauses, the story is too wide, so cut it down to one person or company and one obstacle. If nothing at the end is different from the start, you have a subject but no story yet. Fix that now, while it costs a sentence.
Join the beats with "but" and "therefore"
Under your pitch, sketch three to five beats, meaning the main turns of the story, then look at how each one leads to the next. Beginners link them with "and then": this happened, and then this, and then this. That gives you a timeline instead of a story. Scriptwriter Federico Bolanos replaces every "and then" with "therefore" or "but", so each beat is either caused by the last one or complicates it.
Cut anything that does not raise the stakes of the main conflict, however good it is. His example is a Rockefeller documentary that dropped the backstory of the business partner Henry Flagler because it slowed the story down. On a solo channel that cut saves you twice: once in the script, and again in every picture you no longer have to find.
Tip: Your finished pitch looks like this: "This is a story about [one person or company], who wants [one thing] and has to overcome [one obstacle] to get it. The video asks: [one question]." If you can't fill every bracket with a single item, keep narrowing.
Research against a question list, then stop
Treat research as a short sprint against a fixed list of questions. Scriptwriting coach Subscribr budgets two to four hours of research for a ten to fifteen minute video, and reads eight to ten hours with no draft as a sign the question list is missing. That is a practised writer's budget. The hours table at the end gives a first video six to twelve, and I would treat his figure as where you get to once the question list is a habit.
Use his eight-to-ten-hour mark as your alarm. If you have read for a full day and written nothing, the topic is too wide, and more reading will not fix it. Go back to your two-sentence pitch.
Write the questions before you open a browser
DecodingYT turns every topic into 15 to 20 questions built on who, what, when, where, why and how. Then it keeps asking "why" four or five times, until the answer is a cause rather than a symptom. This is how I would run it:
Write your central question at the top of a blank document.
Under it, write 15 to 20 who, what, when, where, why and how questions that the answer depends on.
For each "why" answer, ask why again, four or five times, until you reach a cause.
Answer only what is on the list, and park anything else in a separate file for video two.
Log each answer with its source, plus a timecode if the source is video or audio.
The parking file matters more than it looks. A fascinating detour like the Henry Flagler backstory will still be fascinating in a month, when it can be the next video.
Treat Wikipedia as an index of sources
Wikipedia is the fastest way to see who wrote what about your subject. Overly Sarcastic Productions skip straight to the references at the bottom of the main page and the related pages, then track down the books, records and original texts listed there. Read the primary source first and the commentary second. Put every fact, quote and page number in one notes document so you never have to reopen the originals while writing.
While you are reading the primary material, note anything you could show on screen: a document, a photo, a dated news clip. On the disaster channels I ran, I spent more nights sourcing archive than writing. The cheapest sourcing I ever did was the material I noticed while researching and logged on the spot.
Let AI tools find leads, then check the source
Use Perplexity or NotebookLM to find where to look. Never put a fact, date or quote from them into your script until you have opened the source it came from and read it there. These tools fail in predictable ways:
General chatbots invent citations, dates and quotes that read as perfectly plausible.
Grounded tools like NotebookLM start to lose nuance once you load them with dozens of files.
Summaries flatten the contradictions between sources, and those contradictions are often where your story is.
When to stop
Stop when every question on the list has an answer with a source next to it. Another sign is when new sources only tell you things you already have. At that point another evening of reading will not change the video, and writing will.
Write the script in two columns: what's said and what's on screen
Write every line of narration with its visual beside it, and don't record anything while a visual cell is still empty. This is the step where the hours from the opening get decided.
Set up the two columns
Johnny Harris works from a master document laid out as a table, as he explained to David Perell. Narration runs down the left in short rows of a sentence or two, and the visual for each row sits beside it on the right. Anything still to be found or checked is tagged in bold red until someone gathers it.
He has a team to do the gathering. You don't, so the red tags matter even more for you, because they are your to-do list.
Make a two-column table in Google Docs or Word, with the headings Narration and On screen.
Paste your research answers in as rows of one or two spoken sentences, never whole paragraphs.
Write the visual for each row on the right: the photo, clip, document, map or chart, plus where it comes from if you know.
Turn the visual red wherever you don't have it yet, or don't know if it exists.
Record nothing until a final pass down the right column finds no red left.

The red cells are your first honest look at how big the job is. Ten red rows on a ten-minute script is an afternoon of searching. Forty red rows means the script has promised more pictures than you can find. Rewriting a sentence now costs far less than filling a gap in the edit, so when a line has nothing you can show, change the line.
Write the body first and the opening last
In our own retention analysis of long-form videos, more viewers left during the opening than across the whole middle. It matches every retention graph I read on the channels I ran: the steepest drop was always at the start. That sounds like a reason to write the opening first, and it is actually the reason to write it last.
You don't know what your opening is promising until the body exists. Scriptwriter George Blackman drafts the whole body before the hook, the first few seconds meant to keep the viewer watching. Then he builds the opening from three things he can now see: who the story is for, what the viewer will understand by the end, and what was lost or at risk. Your two-sentence pitch already holds most of that. The body tells you which parts of it actually paid off.
Then open in the middle of something happening. Harris opened his history of the Mormon migration with "It started with the murder of their prophet in Illinois", over a gunshot and slow-motion pictures, instead of announcing what the video would explain. Never start with "In this video".
Make the first visual match what the thumbnail and title promised, so the click feels answered. None of this guarantees anyone stays, but an opening that delays gives them a reason to leave. Read more hook examples before you write yours.
Keep the middle from sagging
Blackman sees two reasons middles sag: each section opens like an announcement, or it gives away its answer in the first line. Write each section backwards. Put the payoff, the fact or turn that the section exists for, in its last sentence. Open the section with what is at stake, then build towards the payoff without giving it away early.
Compare "Next, let's look at the company's finances" with "The accounts said the money was in Asia. Nobody had checked." The first is a chapter title. The second raises a question the viewer now wants answered.
Link sections the way you linked your beats, with "but" and "therefore", and cut anything that does not push the story on. Weak links between sections are one of the commonest reasons a script feels generic. The script-level fixes for generic documentaries go through them one by one.
Size it to your length, then read it aloud
Work out the word count from your own speaking pace, not a generic pace. This script-length breakdown multiplies target minutes by your words per minute, then by 0.85. The 0.85 leaves room for the moments when a clip, a sound or the music carries the video and nobody is talking. Documentary narrators tend to run at 140 to 160 words a minute, so a ten-minute script lands at roughly 1,200 to 1,350 words.
Read 500 words of your draft aloud at a normal pace and time it.
Divide 500 by the minutes it took to get your words per minute.
Multiply your target minutes by that number, then by 0.85.
Cut or add rows until the left column roughly matches the result, give or take a few rows.
Then read the whole script aloud, start to finish, and mark every sentence where you run out of breath. Split those, and swap any word you would never say across a table. The channel Early Exit moved to drafting out loud for exactly this reason: its typed scripts sounded stiff once spoken.
If you decide to skip assembling the edit by hand, the locked left column is also what you paste into VidRush. The edit step below shows how that works.
Find a visual for every line, or give the names a home
Go down your right column and count the rows that name a person, place, company or event. That count is the size of the job, and each of those rows needs a picture before you open the editor.
Budget for finding a picture per line
Almost everything on screen in a desktop documentary is B-roll, the footage that plays while the narration runs. A-roll vs B-roll explains the difference with examples. In a faceless business story, the screen usually fills with the same kinds of material: logos, store exteriors, old adverts, headlines, share price charts and annual report pages. Lines with nothing better get generic stock of offices and city streets. Some of it takes a minute to find, while the one specific photo of the one meeting can take an evening and still not exist.
On my aviation channel, the lines that ate the nights were never about the crash itself. They were the quiet lines connecting one event to the next.
Plan for a separate picture per line as your default. Every creator whose hours we read and who said how they filled the screen was hunting a new picture for each line. The grind they described matches the 300-asset timeline mentioned in the format step.
Where to get it, cheapest first
Public-domain archives, starting with archive.org, for newsreels, government film and old photos.
Free stock sites for transitional shots: cities, offices, weather, hands.
One paid month of a stock library, bought only when you still have red rows the free routes can't fill.
Archive.org is free and full of historical material, but files often arrive in formats your editor won't open. Lilly's Tech Tips walks through it with 1957 Sputnik footage. Filter for public domain and download. If the file is .OGV, open VLC, go to Media > Convert/Save, and export it as an H.264 MP4. Convert the whole batch before you start editing, so you aren't stopped mid-cut.

Free stock is fine for city skylines but thin on anything historical or specific. Search for a particular event and you get unrelated results or nothing at all. Our list of where to find B-roll goes through the free and paid sites one by one.
If you do pay, pay for one month. Envato Elements sells a single month for $39, with video, music and sound effects included. Storyblocks bills annually only, starting at $252 up front. That makes sense once you upload regularly, but not for a first video. Download everything on your red list in that month, then cancel.

Before you rely on anything you downloaded, read YouTube's current rules on footage and AI. We keep that page up to date.
Give place-heavy names a recurring map
One recurring map can stand in for dozens of pictures. Unknown Frequencies' explainer on the entire history of the First World War named 65 distinct things, the most of any script we coded. Its narration kept coming back to one map of Europe, so countries, alliances and fronts all shared a single picture. It was the only video of the 19 built that way.
Johnny Harris shows the same idea at a higher budget in How I Make My Maps. He uses one base map, re-zoomed and re-labelled, for story after story, without a new clip hunt for each place.

I can't tell you that a map saves time, and I want to be straight about that. We went looking for creators who had built a video around a map or template and reported their hours. None of the 4 accounts that qualified had done so.
My read from cutting history pieces is that a flat map screenshot with a moving highlight is cheap and pays for itself on a script with lots of places. A hand-animated globe is a style project, and it can eat whatever it saves. If your script only names three places, skip the map.
The test takes a few minutes. Go down your right column and mark every row a map could cover. If that comes to a third of the script, build the map.
When a line has no footage at all
Work down a fixed order instead of searching forever. This is the order I'd use, pieced together from what Harris and Lilly's Tech Tips show in their workflows:
A document callout if anything was written down, such as a headline, letter, court filing or balance sheet, with the key words highlighted.
A slow push on a still photo, from 100% to about 108% over four to six seconds, with a little sound under it.
A map if the line names a place or a journey.
A metaphor shot if the line is pure idea: an empty boardroom, a ticking clock, hands on paperwork.
A few seconds of you to camera, if you are making the hybrid format.
Build callouts from a template, never by hand. Editor Joe Vanz shows a reusable DaVinci Resolve macro that turns a news screenshot into a highlighted callout in about two minutes, compared with one to two hours of animating it by hand. Thirty callouts by hand is a week of evenings, and nobody watching will see the difference.
That order also answers whether a documentary can run mostly on still photos. It can, as long as every still moves slightly, has sound under it, and is cut against documents and maps so the eye keeps getting something new. A run of identical slow zooms reads as a slideshow, because the viewer notices the pattern before they hear the story.
Pull your picks into a selects timeline
Before you assemble anything, go through every clip once and keep only the best five seconds. Documentary cinematographer Luc Forsyth strings those picks onto a separate timeline, called a selects timeline, with coloured markers for each group. That way the edit is spent choosing between good clips instead of scrubbing through raw files. He puts it at one to two hours up front. I'd add one thing: name each file with its script row number, so row 34 in your right column is clip 34 in the folder.
Write down how long sourcing took, separately from editing. Almost none of the creators whose hours we read split the two, so none of them could say which part was actually slow. On video two you'll want to know.
Record narration that sounds clear in an ordinary room
Fix the room before you think about a microphone. A phone recording into a wardrobe full of clothes sounds better than a good mic in a bare bedroom. Home narration sounds amateur mostly because of echo off flat walls, and soft things kill echo for free.
A $3,600 studio mic sounds hollow in an untreated room. A $100 mic sounds isolated when it sits close to the mouth with blankets draped around it. Audio educator Curtis Judd demonstrates both in his six rules for any microphone.
Set up in ten minutes
Record facing into an open wardrobe, or hang duvets and blankets over the hard surfaces around your desk.
Put the mic or phone four to eight inches from your mouth. A spread hand, thumb to little finger, is about the right distance.
Angle it 45 degrees to the side, aimed at the corner of your mouth, so the puffs of air on "p" and "b" miss it.
Set the level so your loudest words peak around -12 to -18 dBFS. That leaves room for emphasis without distorting.
Record a short test and play it back on headphones. If you can hear the room, move something soft closer.
A USB mic is an upgrade, and you don't need one for video one. A cardioid like the Samson Q2U, $99.99 as a recording pack, picks up less of the room behind it and gives you a gain dial. It will still sound hollow in a bare room. Buy one for video three if you are still going.
Read in short chunks and never stop the recorder
Don't try to get a whole script in one take. Voiceover creator Nate Curtiss leaves the recorder running the whole time and reads two to four sentences at a time. When he stumbles, he stays silent for two or three seconds and then reads the line again. Stopping and restarting the software on every mistake is what turns narration into an all-day job.
The pause is what makes this work. A gap, or a clap, is easy to spot on the waveform, so in the editor you can find every flub without listening to the whole file and cut them all in one pass. Record everything in one sitting with the same setup. A line re-recorded a week later in a different spot won't match, and viewers hear the room change before they hear the words.
An AI voice still needs directing
A synthetic voice means you never hear yourself, and a line fixed later matches the rest. Delivery is still yours to direct. Generate in short runs of two or three sentences rather than the whole script in a single pass, because long passes can come out flat. The other habits worth keeping:
Make two or three versions of each line and keep the best one on the timeline.
Use an ellipsis to force a pause and capitals to force stress on a word.
Pick a voice that suits the niche rather than the first default you try.
On a 15-minute script that means a long run of small generations, then an evening of picking the best takes. ElevenLabs' Starter plan costs $5 a month billed annually or $6 monthly, and the free plan does not cover commercial use. Choosing the voice and directing it line by line is most of what goes into an AI voiceover that sounds deliberate.
For a first video I would record your own voice in the wardrobe. It costs nothing and it gets better with every video. If you'd rather not narrate, pick a voice suited to your niche from VidRush's library and judge it against your script; whether it suits your story is your call. If you do record, the same file can go into VidRush as a Custom Voiceover, as an MP3 or WAV between 6 and 60 minutes long.
Edit in passes, not from second one
Build the cut in layers across the whole video, never one finished scene at a time. I have watched a lot of first-timers open a blank timeline at 0:00, try to make the first ten seconds perfect, and stall with two polished minutes and eighteen untouched ones. In the order below, each pass covers the entire timeline before the next one starts.
The seven passes
Pass | What you do | Leave for later |
|---|---|---|
Narration spine | Import the voice track, cut the flubs and dead air | Every visual |
Music bed | Lay a track per chapter and mark where the music drops out | Levels and mixing |
Version zero | Put a visual on every line from your selects, by script row number | Trimming to the frame |
Fine cut | Cut whatever doesn't serve the central question; set the pace | Effects and text |
Motion | Slow pushes on stills, document highlights, on-screen text | Sound effects |
Sound | Quiet effects, music ducked under the voice, final loudness | Colour |
Colour and export | One correction so mismatched sources sit together, then export | n/a |
Each pass touches the whole timeline before the next begins
Version zero is the pass that saves the project. It will run long, clips will be the wrong length, and some rows will still have placeholders, which doesn't matter. Its only job is to make the video exist from start to finish, so every later pass improves something instead of building it from nothing. Documentaries get finished on momentum.
Where the hours go by hand
By hand, the edit is the biggest row in the hours table at the end: 15 to 30-plus hours for a first video, on top of research and writing. Most of that goes on version zero and the fine cut, placing a picture against each line and trimming it to fit. Those two passes are how a timeline like that 300-asset one gets built.
With your right column filled in and your selects named by row, version zero means placing clips rather than searching for them. That difference is most of the reason to do the earlier steps properly. Keep timing yourself pass by pass, the same way you timed sourcing.
Pace and sound, the passes beginners rush
Vary the pace on purpose. Run quick cuts through the company's rise, then hold a single photo for eight seconds when the story turns. If every cut is the same length for twenty minutes, the viewer stops feeling where the turns are.
Sound needs more care than most beginners give it. Nobody leaves because a photo is slightly soft, but people do leave when they can't hear the narration over the music. For the sound pass:
Lower the music 18 to 24 dB under the voice whenever anyone is speaking (this is called ducking).
Change the track at chapter turns, and drop the music out completely for the big moment.
Keep sound effects barely audible: paper, clicks, a shutter, never cartoon whooshes.
Master the final mix to around -14 LUFS so it plays as loud as everything else in the feed.
Pick a free editor by your laptop
Editor | Free version gives you | Needs | Paid tier adds |
|---|---|---|---|
DaVinci Resolve | Watermark-free export up to 4K 60fps, the Fairlight audio mixer, colour grading | 16 to 32 GB RAM and a dedicated graphics card | Transcription, text-based editing, voice isolation (Studio, $295 one-off) |
CapCut Desktop | Watermark-free export at 1080p and 4K 60fps | Runs on a light laptop | Automatic silence and filler removal, full auto-captions (Pro, $19.99 a month) |
Both are enough for a first documentary without paying for anything
Use DaVinci Resolve if your computer can run it. Ducking and loudness happen in pass six, and the free version includes a proper audio mixer for that job.
On a light laptop, use CapCut instead. A timeline that stutters every time you scrub will make you quit faster than any missing feature. You don't need the paid tier of either one for video one.
Hand the assembly to VidRush
Version zero, matching a clip to hundreds of lines, is the part you can hand off if it's where you know you'll stall. This is the step VidRush is built for:
Open Custom Script and paste only your narration column. The box asks for complete sentences, no abbreviations and no headers or stage directions, so leave out the right column and any labels. If you already recorded, upload the narration instead as an MP3 or WAV of 6 to 60 minutes.
Check the plan before any credits are spent. VidRush reads the length from your script, anywhere from 6 to 60 minutes, and shows the format, duration, voice and estimated credits for you to confirm.
Let it render in the browser. You can close the tab, and most videos finish within an hour.
Open the cut in the editor and work down your right column, swapping clips that miss, retiming shots and fixing captions.
Render and export.
What comes back is a 16:9, 1080p cut with stock and archive footage matched to each line, plus music and captions. Treat it as version zero done for you, then make your own fine-cut pass on it.

Plans start at $99 a month, and there is no free tier. Weigh that against what the assembly costs you now: the 15 to 30-plus hours on the edit row, or the fee for hiring an editor to do the same pass.
VidRush makes widescreen videos from 6 to 60 minutes. It isn't the tool for vertical clips, anything shorter, or interviews with several speakers. If you're making the hybrid, with narration plus pieces to camera, upload up to five to-camera clips along with the voiceover they were cut from. VidRush uses them exactly as supplied and fills the gaps with B-roll. That mode takes English speech only. Topics with very little real footage online come back with thin, repetitive matches, so search for your subject before you count on it.
My lean: if you have more evenings than money, cut the first one by hand, because you learn what a cut needs by making one. If evenings are what you're short of, and your topic has plenty of real footage online, paste your narration column into the AI documentary maker and judge the first cut against your right column.

Give it a title and thumbnail that do different jobs
Let the thumbnail show one thing and let the title say what is at stake. A thumbnail reading "WIRECARD" over a title that also starts with Wirecard uses two slots to say one thing. On the disaster channels I ran, the thumbnails that tried to tell the whole story at once were the ones I ended up replacing.
Your central question is usually most of your title already. Fern's "Why the World's Biggest Aquarium Broke" and Johnny Harris's "Why Saudi Arabia is Building a $1 Trillion City in the Desert" work the same way: a question, with the answer promised.
If your question won't make a title, it probably isn't sharp enough. On the next video, test a working title alongside your two-sentence pitch before you write. Refine the wording after the rough cut, once you know what the video actually delivers.
For the thumbnail, use one subject or one piece of evidence: the burst tank, the court filing, the founder's face, the logo on a boarded-up store. Add three words of text at most, or none. On a phone, a thumbnail shows up a couple of centimetres wide, and anything busier becomes a smudge. Make sure the opening seconds show what the thumbnail showed, as covered in the scripting step, so the click feels answered.
Check it at phone size
Never judge a thumbnail full screen in your editor. Drop it into a free tool that previews your thumbnail in the feed next to real videos, with your title under it, and look at the mobile view. If you can't tell what it shows in a second, simplify it.
If you can't design, the thumbnail generator gives you up to six variations to run through the same preview, so you reach the phone-size test without opening a design app. In VidRush, make that pick before the render, because a skipped step locks in the thumbnail VidRush chose.
How long your first documentary takes, what it costs, and what to change next time
Plan on 35 to 75 hours for a first documentary between ten and twenty minutes long. The edit is the biggest block and the likeliest to run over. This is the same stage-by-stage estimate from the top of the page, broken out below, and your own stages will split differently.
Where the hours go
Stage | Estimated hours, first video |
|---|---|
Research against your question list | 6 to 12 |
Two-column script, with two revisions | 6 to 10 |
Narration recording and cleanup | 2 to 4 |
Finding visuals | 6 to 15 |
Editing, sound and pacing | 15 to 30+ |
Title, thumbnail, subtitles, upload | 2 to 4 |
Total | 35 to 75+ |
An estimate for a first narrated documentary made alone, from research to upload
The "+" on the edit row matters. The only hard figure for the edit alone in the creator accounts we read came from someone on r/premiere who said an 18-minute documentary took "15 days, working 6-7 hours everyday". That comes to about 97.5 hours of editing, roughly 5.4 hours per finished minute. It is one person's account. His visual approach isn't visible in the post, and he was posting to ask whether he was slow.
I'd still show you that number, as a ceiling and never as a target. An edit heading past 60 hours usually means a script that left visual cells empty, and the red rows show you that before the clock does.
Keep the sourcing log from the visuals step open through the edit. By the end of your first video it shows which row ate the most evenings, and that is the row to attack on the second. The bigger version of this problem, and what shrinks it, is in why faceless videos take so long.
What it costs in money
You can make the whole thing for $0, using your computer, a wardrobe to record in, a free editor, archive.org and free stock. What free costs you is hours, mostly in the visuals row of that table. The first money worth spending is the single $39 stock month from the visuals step, and only if you have red rows the free routes couldn't fill. A microphone comes after that, and only if the wardrobe still sounds like a room.
Don't let the money question slow down video one: whether a channel ever earns back even that $39 depends on the niche far more than the format, so settle it when you're choosing between documentary channel ideas, not halfway through your first edit.
Pick the length by your hours, not by retention
Most beginners worry that a long video will lose people, so they plan to keep it short. I expected our data to back that up, with watch time flattening out somewhere past the quarter-hour mark. It didn't. We analysed 61,390 long-form videos, and median minutes watched per view kept rising almost in a straight line with length, right up to the longest band we measured.

Videos of 12 to 18 minutes held a median of 4.95 minutes per view, 25 to 35 minute videos held 9.25, and videos in the longest band, from 35 minutes up, held 12.42. Each extra minute of video added roughly 0.27 to 0.31 minutes of watch time across those bands, and the pattern held for the smallest channels as well as the largest. These were small-to-mid, mostly faceless channels, not documentaries specifically, so read it as the shape of the curve and not a promise that longer wins. A long video with a weak middle is still a weak video.
In that sample, longer videos earned more total minutes per view, and the share of the video people watched dropped only slightly as length went up. So length is an hours decision, not a retention one. Halving the runtime roughly halves the time it takes to make. For a first documentary I'd aim for about a dozen minutes, because a video you finish teaches you more than one you abandon halfway through the edit.
Reading the first week
Expect almost nothing. New creators on r/NewTubers keep posting the same launch story, a first upload that got a few dozen views: a handful of impressions, then days of nothing. That is how a brand-new channel starts, and it says nothing about the video yet.
At that scale, click-through rate (CTR) swings wildly on a single click and tells you nothing. Editing educator Tim Runia ignores views and CTR for the first week and looks at three things instead:
The first 30 seconds of the retention graph. His rule of thumb: if more than 40% of viewers are gone by then, the hook was too slow or didn't match the thumbnail.
Any sudden drop later in the curve. Note the timestamp and find that row in your two-column script, which might be a static shot, a stretch of jargon or a line with nothing at stake.
Where the few impressions came from. Search means your title matched what someone typed, and Browse or Suggested means YouTube is trying the video on new viewers.
The two-column script pays off a second time here. A drop at 5:30 becomes a row you can open and read, with the line and the shot side by side, instead of a vague feeling that the middle dragged.
What to change on video two
This is the checklist I'd hand anyone starting their second documentary. Every item is something you've already met on this page. The difference on video two is doing each one properly instead of half-way:
Write narration and visuals together, with no red cells left before recording.
Halve the scope: one event, one conflict, one question, not a whole company's history.
Gather every image, clip and music track into folders before you open the timeline.
Record narration in short chunks with pauses, so the visuals have room to breathe.
Compare your stage timings with video one and attack the biggest row first.
If your log says the edit is the row you can't afford again, hand version zero to VidRush on video two, using the route from the edit step. Either way, the decision for video two comes from your own log, not from anyone's range, including mine. Finish the first one, write down where the hours went, and cut from the biggest number.
Frequently asked questions
Can a documentary work without showing my face?
Yes. In the 19 solo documentaries we coded, none had narration suggesting the creator ever appeared on screen. Your voice and a clear central question do the job a presenter does. A few seconds of you to camera is only worth adding for lines that have nothing else to show.
Can I make a documentary YouTube video without filming anything?
Yes, and for a first video it is the format I'd pick. Archive footage, public-domain film, stock, photos, documents and a simple map can cover every line, as long as you decide the visual for each line in the script before you record.
Can I build a documentary mostly from still photos?
Yes, if the stills move and are cut against other material. A slow push on each photo, a little sound under it, and documents and maps in between keep it from reading as a slideshow. Identical zooms one after another are what make it feel static.
Won't an AI tool just produce generic slop?
Not if the script is yours and specific. Generic documentaries usually fail at the script, in vague lines that could be about anything, before any tool touches them. VidRush doesn't generate clips: it matches real stock and archive footage, images and motion graphics to each line of your script. What comes back is a first cut you finish in its editor, not a final video.


