On this page
Twenty-nine videos, 142 minutes, 2.07 gigabytes, produced without opening an editor. The timeline is a file, the graphics are components, and the render is a command. Licence cost: nothing.
That sounds like the obvious answer, so here is the part that gets left out of posts like this: it cost about three days, two of which were spent on problems that have nothing to do with video.
What are the three ways to not pay monthly?
| Route | Cost | Suits |
|---|---|---|
| Free tier of a mainstream editor | €0, with limits | most short-form work |
| One-time purchase | €50–100 once | steady output, manual editing |
| Render from code | €0 in licences, days in setup | batches that share a structure |
The third only makes sense on the last column. For one video it is an absurd amount of work. The crossover is roughly where you would otherwise be repeating the same edit by hand for the fifth time.
What does rendering from code actually mean?
The video is a program. Text, graphics and timing are described in markup, the framework draws each frame, and a renderer writes the file.
The consequence that matters: a change applies to all of them. When the subtitle layout turned out to be wrong, fixing it was one edit to one component and a re-render of the affected videos. In a timeline editor that is twenty-nine files opened by hand.
The second consequence: the content is data. Each video here is a script plus a list of cues — this graphic at this moment — so the words and the design are separate things. Rewriting a sentence does not disturb the layout.
The whole list
67 tools, what each costs and when you actually need it. Updated twice a year.
What did it actually cost?
Three days, and the breakdown is instructive because almost none of it was editing.
| What | Why |
|---|---|
| Building the template | the actual work, one time |
| Rebuilding the subtitle layout | the first eight videos had text overlapping wrapped lines |
| Replacing a media probe tool | the bundled one needed a newer operating system than the machine had |
| Fixing graphics that collided | two full-screen elements could occupy the same seconds |
Only the first of those four is the job. The other three are the tax, and they are the reason "it is free" is an incomplete sentence.
The subtitle one is worth dwelling on. The first eight videos were rendered, looked wrong, and had to be redone — not because of a bug, but because a layout that worked for short lines broke on long ones. In an editor you would have seen it immediately on video one. In a pipeline you see it after eight, because you were not watching.
That is the genuine trade: you exchange per-video attention for batch leverage, and batch leverage means batch mistakes.
When should you absolutely not do this?
- One video. Open an editor.
- Videos that differ from each other. The leverage comes from sameness. If every piece has its own structure, the template is an obstacle.
- Anything where the editing is the craft. Pacing decisions made by feel do not survive being expressed as timings in a file.
- If you do not already write code. This is a programming project that produces video, not a video project.
So what should most people use?
The free tier of the editor already on their phone.
It does captions and vertical cuts quickly, the free tier is genuinely usable, and the paid tier is around €10 rather than €30. For short-form that is the whole answer, and reaching for anything more elaborate before you have published a few things is the mistake don't buy a content tool yet is about.
The one thing worth checking before committing to any subscription editor: what the export costs. Several are cheap monthly and then restrict resolution, add a watermark, or cap exports on the lower tiers. That bill arrives at the moment you finish, which is the worst moment to discover it.
What about the one-time purchase option?
Underrated, and the right answer for a lot of people.
A perpetual licence at €50–100 with no monthly line is less fashionable than it was and still perfectly serviceable. It suits steady manual output where you want control, do not want a template, and would rather own the thing than rent it.
The catch is updates: a one-time licence eventually stops receiving them, and format support ages. Budget for replacing it every few years rather than assuming it is permanent.
Where these numbers came from
The 29 videos, 142 minutes and 2.07 GB are measured from this project's own output on 22 October 2026. The three-day figure is my own, and it is honest rather than flattering — a second project with the same template would take hours.
Software prices and free-tier limits change constantly. The structural point does not: rendering from code is cheap in licences and expensive in attention, and it only pays back across a batch.
The AI Persona Playbook covers the production pipeline for a channel in more depth.
Tools in this piece
| Tool | What it does | Price |
|---|---|---|
| CapCut | Fast shorts and vertical editing, with captions. | Free, Pro ~€10/mo |
| Movavi | Desktop video and photo editing, sold as software rather than a cloud subscription. | From ~$19.95/mo |
| Descript | Edit video by editing the transcript. | Free tier, then ~$15–30/mo |
| OBS Studio | Screen recording. Free, open source, and good enough for everything. | Free |
Every tool has its own page with the price, who should skip it and what to check before paying. Some links are affiliate links.
Questions people ask
Can you edit video without paying a monthly fee?
Yes, in three ways: a free editor tier, a one-time purchase, or rendering from code. The third has no licence cost at all but trades money for engineering time, which is only a good trade above a certain number of videos.
When is rendering from code worth it?
When the videos share a structure and there are enough of them. For one video it is absurd. For 29 that differ only in their content, the template is written once and every change applies to all of them at once.
What does a code-based video pipeline actually cost?
Nothing in licences and several days in setup. On this project the real costs were a graphics layout that had to be rebuilt after the first eight videos overlapped text, and a media tool that would not run on an older operating system.
Is a free editor tier good enough?
For most short-form work, yes. The editor most people already have does captions and vertical cuts quickly, and its free tier is genuinely usable. Start there and only leave when something specific breaks.
What is the hidden cost of a subscription editor?
Export. Several tools are cheap monthly and restrict resolution, watermarks or export counts on lower tiers, so the real price appears at the moment you finish rather than when you sign up.
Does rendering from code look worse?
It looks different. You get perfect consistency across every video and no manual flourishes. For explainer content with repeating graphics that is an advantage; for anything that benefits from hand-feel it is not.