How to Edit a YouTube Video With Claude Code (Beginner's Step-by-Step Setup)
You do not need to be a developer or a video editor for this. If you can install two apps and paste a few commands, you can take a raw recording all the way to a finished YouTube video. This page is the exact setup for claude-youtube-editor, my free open-source project, written for someone who has never opened Claude Code. Every new word gets explained the first time it shows up. The repo is free. Some of the services it calls are paid, and I mark those clearly so nothing surprises you.
- VS Code and Claude Code installed and running on your machine
- The free claude-youtube-editor project set up and ready
- Your API keys in the right place, paid ones marked, skippable ones called out
- Your first raw video dropped in, and Claude cutting it for you
Ok, let's start.
This is the hands-on setup. If you want the tour first, what each step does and why it works the way it does, that is the companion guide: Claude Code Video Editing, from raw recording to published video. This page is the how. That page is the why.
Watch it run first
Before you install anything, here is the result. The video below was made with this project, end to end. The cut, the animations, the on-screen recordings, the voice cleanup, the sound effects, and the thumbnail. All of it built by Claude Code.
That is what you are setting up. Now let's get it on your machine.
What is Claude Code, and what is a skill?
Two words show up on every step below, so let's define them once.
Claude Code is an AI assistant that works in your terminal. The terminal is the plain text window where you type commands to your computer instead of clicking buttons. You talk to Claude Code in normal English, and it reads your files, runs commands, and edits code for you. You are the director. It does the typing.
A skill is a folder with an instructions file inside it. Think of it as a playbook: someone writes down how to do one job well, once, and Claude follows that playbook every time you ask for that job. You never open these files. You say what you want in plain English, and Claude picks the right playbook on its own.
This whole project is eight of those playbooks, lined up in order. That is the entire trick. You do not learn video editing. You ask, and each skill does its part.
🧭 Where this leads. If writing your own skills and shipping a real product on this pattern is the part that pulls you in, that is what I teach in Build With AI 1.0. You do not need it for any of this, the repo stands on its own, but that is the next step if you want it.
What you need first
Here is the full list before the steps. Nothing is exotic, and every tool is free.
Programs to install, and I walk each one below:
- VS Code, a free code editor. Your workspace.
- Claude Code, the assistant that does the work.
- Python 3.10 or newer. The project runs small Python programs (the cut, the upload, the thumbnails).
- Node 18 or newer. One part, the animation engine called Remotion, is a Node project. Install the current LTS version and you are covered.
- ffmpeg. The free program that actually cuts and encodes video. Everything leans on it.
⚠️ Install Python, Node, and ffmpeg before the setup step, not during it. If they are missing, the setup stops with an error like ModuleNotFoundError or 'npm' is not recognized. That is not a bug in the project. It means one of these three is not installed yet, or not on your PATH. PATH is just the list of places your computer looks for programs.
You also need a few free accounts for API keys. An API key is a long password that lets the project use a paid online service as you. You paste your keys into one file and the project reads them from there. I show where each one comes from in Step 6. The good news for trying it: you can run the first step, the cut, on AssemblyAI's free tier, and skip the paid keys until you want the later steps.
Step 1: Install VS Code
VS Code, short for Visual Studio Code, is a free code editor from Microsoft. For this guide, think of it as one window that holds two things: your project files on the left, and a terminal at the bottom where Claude Code runs.
- Go to code.visualstudio.com.
- Download the build for your system (Windows, Mac, or Linux). The site usually detects it for you.
- Install it like any app, and open it once so you know it works.
That is the whole step. If you already have VS Code, skip ahead.
Step 2: Install Claude Code
There are two ways to get Claude Code. Pick one. I use the terminal version, because the project runs a lot of terminal commands anyway, and it keeps everything in one place.
The terminal version (what I use)
Open a terminal. On Windows, the simplest is PowerShell: press Start, type PowerShell, and open it. Then paste one line.
On Windows:
irm https://claude.ai/install.ps1 | iex
On Mac or Linux, paste this instead:
curl -fsSL https://claude.ai/install.sh | bash
This installer keeps itself updated, so you install it once and forget it. When it finishes, check it worked:
claude --version
If that prints a version number, you are done. If it says the command is not found, close the terminal, open a new one, and try again. A fresh terminal is the fix nine times out of ten.
The VS Code extension (the click version)
Prefer buttons over commands? In VS Code, click the Extensions icon in the left bar (or press Ctrl+Shift+X), search Claude Code, and install the one published by Anthropic. It adds a chat panel right inside VS Code.
Either way, the first time you start Claude Code it opens your browser to sign in. Claude Code needs a Claude account, and there is no free tier, the cheapest is Claude Pro at about $20 a month. I put the full cost picture near the end.
Step 3: Get the project
Now you download the project itself. Two ways, and the second one needs no extra tools.
Option A: clone with git (the normal way)
If you have git installed, this path is cleaner because updates are one command later. In your terminal, go to wherever you keep projects, then:
git clone https://github.com/hassancs91/claude-youtube-editor cd claude-youtube-editor
cd means change directory. It walks you into the project folder. Every command after this runs from inside that folder.
Option B: download the ZIP (no git needed)
No git? No problem. Open the repo page at github.com/hassancs91/claude-youtube-editor, click the green Code button, choose Download ZIP, and unzip it somewhere you will remember. That folder is your project. Done.
Step 4: Open the folder and start Claude Code
Open VS Code. Choose File, then Open Folder, and pick the claude-youtube-editor folder you just made. Your files show up on the left.
Now open the built-in terminal: from the top menu, Terminal, then New Terminal. A panel opens at the bottom, already sitting inside your project folder. This is where everything happens.
Start Claude Code by typing one word and pressing Enter:
claude
The first time, it opens your browser to sign in to your Claude account. Sign in, come back to the terminal, and you are talking to Claude Code. From now on it remembers you for this project.
One nice thing you get for free: this project ships its eight skills inside a .claude/skills/ folder. Claude Code finds them automatically the moment you open the folder. You do not install or turn on anything. They are just there, ready. (If you chose the VS Code extension instead, click the Claude Code icon in the top right or the status bar to open the chat panel.)
VS Code with the claude-youtube-editor project open (file tree on the left) and Claude Code running in the integrated terminal at the bottom.
Step 5: The one-time setup
This part looks like the scary part. It is not. You are pasting four commands, once, and then never again for this project. Run them in the same terminal, from inside the project folder.
First, a virtual environment. A virtual environment, or venv, is a private box for this project's Python tools so they do not collide with anything else on your computer. You make it once.
python -m venv venv venv/Scripts/python -m pip install -r requirements.txt
On Mac or Linux the second line is ./venv/bin/python -m pip install -r requirements.txt. That line reads requirements.txt, the project's shopping list of Python tools, and installs all of them into the box. It takes a minute.
Next, the animation engine. Remotion is the Node project that draws every on-screen visual. Set it up:
cd remotion npm install npm run gen cd ..
npm install pulls in Remotion's own parts. npm run gen builds the list of example shots so the studio can find them. cd .. walks you back up to the project root, where the rest of the work happens.
💡 Two things that save beginners ten minutes. Run every command from the project root, the top folder, because the tools look for your files starting from where you are standing. And if Python ever says ModuleNotFoundError, you are not in the venv, so start the command with venv/Scripts/python instead of a bare python, and the error goes away.
Want proof it worked? See the example first, with no footage and no recording:
cd remotion && npm run studio
That opens Remotion Studio in your browser with 37 real shots from a video I already published. Click any one and it plays. This is the fastest way to see what the project makes before you shoot a single frame.
Remotion Studio open in the browser: the example shots listed down the left sidebar, one selected, and the finished shot rendering in the preview canvas.
Close the studio with Ctrl+C in the terminal, and cd .. back to the root when you are done looking.
Step 6: Add your API keys
The project reads your keys from one file. You make that file by copying the example:
copy .env.example .env
On Mac or Linux that is cp .env.example .env. The .env file is a plain text file for your secret keys. It is git-ignored, which means it never gets uploaded anywhere. Open it in VS Code and paste your keys in.
| Key | What it does | Where to get it | Need it to start? |
|---|---|---|---|
ASSEMBLYAI_API_KEY |
Transcribes your video so Claude can read it and cut it | assemblyai.com | Yes, but the free tier is enough to try the cut |
ELEVENLABS_API_KEY |
Cleans your voice and makes the sound effects and music | elevenlabs.io | Optional to start. Paid. Free local option below |
GEMINI_API_KEY |
Draws your thumbnails | ai.google.dev | Optional. Only needed when you render thumbnails |
Two things keep your first run cheap. The voice cleanup step has a free method that runs on your own computer, called RNNoise, no key and no cost. ElevenLabs is the better result on hard noise, but RNNoise is often enough. And YouTube is different from the three keys above: it does not use a key here, it uses a one-time browser sign-in called OAuth, set up when you are ready to upload (the steps are in the repo's tools/yt_upload_SETUP.md).
So the honest minimum to try the whole idea is one free AssemblyAI key. That is it.
Step 7: Drop in your raw video
The project ships with an empty videos/ folder. That is on purpose. Your camera files are yours, so they do not come in the box.
Make a folder for your first video and put your recording in it:
videos/video-1/your-recording.mp4
You do not need to build any of the other folders. The skills create what they need as they go. One raw file in one folder is the whole job here.
And remember what you are recording: yourself, talking. That is the entire shot list. Every other thing on screen gets built by the project, not filmed by you.
Step 8: Ask Claude to cut it, then walk the pipeline
Now the fun part. Go back to your terminal where Claude Code is running, and just ask, in plain English:
clean cut videos/video-1
That is it. Claude picks the cut skill on its own, transcribes your video, reads what you actually said, and removes the silences, the filler words, and the bad takes. You review, it renders a clean version. No menus, no timeline, no editor.
From there you walk down the line, one plain sentence at a time:
clean cut videos/video-1for the cutadd TSX beats to video-1for the animations and on-screen visualsclean the audio for video-1to isolate your voicesuggest sfx for video-1for sound effects on the exact wordpackage this videofor one title and three thumbnails- then upload it as a private draft
Each step hands its work to the next, in this order: cut, visuals, voice, sound, packaging, upload. You approve as you go.
🧩 New here? You just directed six tools with six sentences and never touched a video editor. Going from running someone else's skills to building and shipping your own product on the same pattern is what Build With AI 1.0 is for.
Want the frame-by-frame tour of what each step actually does, why AssemblyAI over Whisper, how the fake screen recordings get built, why the sound lands on the exact word? Read the companion guide: Claude Code Video Editing, from raw recording to published video. This page got you set up. That one goes deep on each step.
The 8 skills, one line each
You will hear these names as you work. Here is every skill in the project, one line each, in the order you meet them.
| Skill | What it does |
|---|---|
clean-cut |
Step 1. Cuts your raw footage into a clean master and writes down when every word happens. |
make-tsx |
Step 2. Builds the on-screen visuals as code, synced to the words you said. |
fake-screencast |
Part of Step 2. Turns plain screenshots into a screen recording that never happened, cursor and clicks and all. |
clean-audio |
Step 3. Removes the room from your voice and keeps your levels. |
suggest-sfx |
Step 4. Lands sound effects on the exact word, from a library that grows every video. |
packaging |
Step 5. One locked title and three thumbnail bets for YouTube's own test, rendered as real images. |
vidtsx-2d-generator |
The rulebook. The low-level rules that keep an animation from crashing. You never call it directly; the visual steps lean on it. |
brand-setup |
The one to run first. Makes everything look like your channel instead of mine. |
Make it your channel
The project ships with a house look, a calm indigo style. It is real and you can keep it. But if you change nothing, your videos will carry someone else's brand. So run this once, before your first video:
/brand-setup
It asks you about your colors, fonts, wordmark, and the feel you want, then sets it all up and shows you a preview card so you see your brand before you build a video in it.
What it costs
The project is free and open source, MIT licensed. The services it calls are not, and I would rather tell you now than let you find out later.
| Service | For | Cost note |
|---|---|---|
| Claude Code | Driving everything | Paid, Claude Pro is about $20 a month, no free tier |
| AssemblyAI | The cut (Step 1) | Free tier is enough to try it |
| ElevenLabs | Voice and sound (Steps 3 and 4) | Paid; the voice step has a free local option |
| Gemini | Thumbnails (Step 5) | Paid, and only if you render thumbnails |
| YouTube | Upload (Step 6) | Free, browser sign-in |
These are your own keys on your own accounts. Nothing here is a subscription to me. Prices move, so check each provider before you plan a big batch around any number.
FAQ
Do I need to know how to code?
No. You type plain English sentences and review what comes back. The one time you touch a file directly is pasting your keys into .env, and that is copy and paste. You never write code or edit video yourself.
Is it really free?
The project is free and MIT licensed, so you can clone it, change it, and sell what you make with it. The services it calls are paid, on your own keys. The cheapest way to try the whole idea is one free AssemblyAI key plus the free local voice cleanup, so your first run can cost close to nothing beyond your Claude Code plan.
What is the smallest set of keys I need to start?
One. A free AssemblyAI key runs Step 1, the cut, which is the heart of it. Add ElevenLabs and Gemini later, when you want the voice, sound, and thumbnails.
Does Claude Code cost money?
Yes. Claude Code has no free tier. The cheapest plan is Claude Pro at about $20 a month, which is plenty for this. There are bigger plans and a pay-per-use API option too, but Pro is the beginner answer.
Does this work on Mac and Linux?
It should. Claude Code, Python, Node, and ffmpeg all run on the three systems. I build on Windows 11, so that is what I have actually tested and what the screenshots show. If you hit a platform bug, open an issue on the repo and I will fix it.
A command said "not recognized" or "ModuleNotFoundError". What do I do?
That almost always means a tool is missing or not on your PATH, or you are not in the venv. If npm or python is "not recognized", it is not installed yet, so go back to What you need first. If Python says ModuleNotFoundError, start the command with venv/Scripts/python instead of a bare python. And always run from the project root.
Do I still need to record my screen?
No. Every on-screen moment is built as code and placed over your cut. You record your face and nothing else. Diagrams, UI walkthroughs, terminal mockups, and title cards are all generated, not filmed.
What this is part of
Strip the video away and this guide taught one habit: you do not do the hard job yourself, you point a set of small, sharp tools at it and direct them. Here the job was a YouTube video. In a real product it is your app, your data, your deploy, wired the same way.
That is the thing I actually teach. Build With AI 1.0 is a full course that walks you from an empty folder to a deployed AI product:
- Building a real AI app with Python and Django, start to finish
- Wiring AI models into real features, the same pattern this project uses
- Directing AI with skills and playbooks instead of copy-paste-and-hope
- Auth, payments, and shipping to real users
Course
Want the full system?
Related
Get the free Vibe Engineering Blocks guide
The exact building blocks I use to ship real products with AI — yours as a free PDF.
Questions & Discussion
Ask a question about this guide →Have a question? Ask it in the community — it's tagged #guide and linked back here. Reading is open to everyone; posting needs a free account.
Loading questions…