Claude Code + Remotion = FREE Motion Graphics Tutorial (No Subscription)
A no-code tutorial for producing professional motion graphics — lower thirds, subscribe animations, transitions, overlays — by having Claude Code write animation code that Remotion renders into video files usable in Final Cut Pro, Premiere, or CapCut, even on a free Claude account.
Pouya EtiWatchTranscript found
Quick learning frame
Read this before watching.
Coding-agent workflow is the loop of inspect, plan, edit, verify, summarize, and route the next task to the right tool.
New playlist item from Pouya Eti; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Skill you build: The ability to run a Claude Code + Remotion pipeline for motion graphics: setting up the project with a starter prompt, previewing and editing renders in the local Remotion app, and iterating with reference images and specific fix requests.
Watch for the shift from claim to mechanism. The learning value is the point where the transcript reveals a repeatable action, tool boundary, context move, review habit, or artifact.
Concept diagram
Where this video fits.
01Inspect
02Plan
03Edit
04Verify
05Review
06Route
Deep lesson
Turn this video into working knowledge.
2,540 cleaned transcript words reviewed across 715 timed caption segments.
Thesis
Claude Code + Remotion = FREE Motion Graphics Tutorial (No Subscription) teaches a practical codex + claude workflows move: A no-code tutorial for producing professional motion graphics — lower thirds, subscribe animations, transitions, overlays — by having Claude Code write animation code that Remotion renders into video files usable in Final Cut Pro, Premiere, or CapCut, even on a free Claude account.
The goal is not to remember the video. The goal is to extract the operating principle, tie it to timestamped evidence, test how far the claim transfers, and make something reusable.
1:48
Claude codes, Remotion renders
“your Claude account. Even with free Claude account, you can use it, but the limits will be less, so you can create less motion graphics, and you have to wait for it to restart. So, when you download...”
Claude itself cannot create videos — it writes code for animated designs, and Remotion converts that code into video files you drop into any editor; the workflow starts by downloading the Claude desktop app, opening Claude Code, and pointing it at a fresh folder (e.g. 'motion graphic' on your desktop), and it works even on a free account with tighter limits. Install the Claude desktop app, open Claude Code, and create a dedicated motion-graphics folder as your project workspace before writing any prompt.
4:45
Setup prompt to studio
“So, for example, right now we have this title, and I can play and this is how it is, how it appears, and if I want to change it, I can come here and change the title, and...”
Pasting the creator's single setup prompt makes Claude Code install Remotion, scaffold folders including an 'out' directory for rendered files, and open a local Remotion app in the browser where you can play, edit titles, and re-render; overlays render with transparent backgrounds (shown as black) so they composite over footage in Final Cut Pro, and a custom request — like a purple-violet lower third with particles asking viewers to like — takes about 3 to 4 minutes to generate. Run the setup prompt, then request one lower third in your brand colors with specific animation and particle requirements, and drag the rendered file onto a real timeline to check the transparency.
11:04
Iterate with images
“another cool trick that you can use for motion graphics. You can come on Pinterest and find something you like, some style, some um design that you like, and then use that uh by copy-pasting the image inside...”
You can paste a Pinterest reference image into Claude Code and ask for a motion graphic in that style, feed it your own assets (like a channel avatar used inside a subscribe notification), request sound effects from a folder you provide, generate in any language including Farsi, and fix flaws by naming them precisely ('the add-a-note color is too close to the background, the gear icon is deformed') — and Claude remembers past graphics so you can return later and ask for changes. Find one reference design on Pinterest, paste it into Claude Code with a request to animate it, then send two specific visual corrections and compare the revision.
01
Inspect
Start with this video's job: A no-code tutorial for producing professional motion graphics — lower thirds, subscribe animations, transitions, overlays — by having Claude Code write animation code that Remotion renders into video files usable in Final Cut Pro, Premiere, or CapCut, even on a free Claude account. Treat "Inspect" as the outcome you are trying to make visible, not a topic label. Anchor it to 1:48, where the video says: “your Claude account. Even with free Claude account, you can use it, but the limits will be less, so you can create less motion graphics, and you have to wait for it to restart. So, when you download...”
02
Plan
Use "Plan" to locate the part of the codex + claude workflows workflow the video is demonstrating. Ask what changes in your real setup if this claim is true. Anchor it to 4:45, where the video says: “So, for example, right now we have this title, and I can play and this is how it is, how it appears, and if I want to change it, I can come here and change the title, and...”
03
Edit
Turn "Edit" into the reusable artifact for this lesson: A routing matrix for when to use Codex, Claude, browser checks, or manual review. This is where watching becomes something you can inspect and reuse.
04
Verify
Use "Verify" as the application surface. Decide whether the idea touches a browser flow, a local file, a model choice, a source document, a UI, or a review step.
05
Review
Use "Review" to prove the lesson. The evidence should connect back to the video title, transcript anchors, and a concrete output, not a generic best-practice claim.
06
Route
Use "Route" to carry the idea forward: save the prompt, checklist, diagram, or operating rule that would make the next agent run better.
Example
Source-backed work packet
Convert the video into a scoped task that includes the transcript claim, target workflow, acceptance criteria, and proof. The output should be a routing matrix for when to use codex, claude, browser checks, or manual review..
Example
Claim vs. demo brief
Separate what the speaker claims, what the demo actually proves, and what still needs outside verification before you adopt the workflow.
Example
Teach-back module
Transform the lesson into a definition, a mechanism diagram, one misconception, one practice exercise, and a check-for-understanding question.
Do not learn it wrong
Treating the title as the lesson without checking what the transcript actually says.
Letting the prompt drift into generic advice that could apply to any video in the playlist.
Copying the tool setup without identifying the operating principle that transfers to your own stack.
Skipping the artifact, which means the learning never becomes operational or inspectable.
Do not count this as learned until these are true.
01
State the transcript-backed claim in your own words: A no-code tutorial for producing professional motion graphics — lower thirds, subscribe animations, transitions, overlays — by having Claude Code write animation code that Remotion renders into video files usable in Final Cut Pro, Premiere, or CapCut, even on a free Claude account.
02
Explain the practical stakes without hype: New playlist item from Pouya Eti; queued for transcript-backed review, topic mapping, and a practical learning artifact.
03
Map the idea onto the Inspect -> Plan -> Edit -> Verify -> Review -> Route sequence and name the weakest link.
04
Produce the artifact and include the evidence that proves it: A routing matrix for when to use Codex, Claude, browser checks, or manual review.
Put it into practice
Give this grounded prompt to Codex or Claude after watching.
You are helping me turn one specific YouTube video into real, durable learning.
Source video:
- Title: Claude Code + Remotion = FREE Motion Graphics Tutorial (No Subscription)
- URL: https://www.youtube.com/watch?v=kXmY6yQa5q4
- Topic: Codex + Claude Workflows
- My current learning frame: Set up the Claude Code + Remotion pipeline from scratch and produce one finished lower third for your own channel — brand colors, particles, a sound effect, and a transparency check inside your video editor.
- Why this matters: New playlist item from Pouya Eti; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Transcript anchors from this exact video:
- 1:48 / Evidence 1: "your Claude account. Even with free Claude account, you can use it, but the limits will be less, so you can create less motion graphics, and you have to wait for it to restart. So, when you download..."
- 4:45 / Evidence 2: "So, for example, right now we have this title, and I can play and this is how it is, how it appears, and if I want to change it, I can come here and change the title, and..."
- 6:28 / Evidence 3: "will process my request and it will start to create a new motion graphic. So, I'm going to fast forward until the result is ready. All right, it is done and it took about 3 to 4 minutes."
- 8:58 / Evidence 4: "app link. So, the link is down in the description. This is a new one. You can use it. Or, for example, transition. You can even create transitions with it. We want to go to the next video..."
- 11:04 / Evidence 5: "another cool trick that you can use for motion graphics. You can come on Pinterest and find something you like, some style, some um design that you like, and then use that uh by copy-pasting the image inside..."
- 13:05 / Evidence 6: "and just paste it for Claude code and said, "Okay, make a cool motion graphic for this image." And it made this as a calendar. Now, you can I can just keep going and modify this. For example,..."
- 14:35 / Evidence 7: "new motion graphics, you can just come and mention that, "Do you remember this motion graphic here? You made it. Now make these changes for it." and it will make the changes for you. So, again to set..."
Your task:
1. Use the transcript anchors above as the primary source packet. If you add outside context, label it clearly as outside context and keep it secondary.
2. Create a source-check table with columns: timestamp, claim, what the demo proves, confidence, and what still needs verification.
3. Extract the actual teachable claims from the video. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A routing matrix for when to use Codex, Claude, browser checks, or manual review.
5. Include:
- a plain-English definition of the core idea
- a diagram or structured model using this sequence: Inspect -> Plan -> Edit -> Verify -> Review -> Route
- 3 concrete examples that apply the video idea to real agentic work
- 2 failure modes the video helps prevent
- a checklist I can use the next time I run Codex or Claude
- one practical exercise with a clear done signal
6. Add a "learning transfer" section: what changes in my workflow tomorrow if I actually learned this?
7. Add a "source check" section that cites which transcript anchor supports each major takeaway.
Quality bar:
- Make this specific to "Claude Code + Remotion = FREE Motion Graphics Tutorial (No Subscription)", not a generic Codex + Claude Workflows essay.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- If evidence is weak, say what transcript segment or timestamp needs review instead of guessing.
- Finish with a concise artifact I could paste into my learning app.
Misconceptions
What to stop believing.
One agent should do every task.
Different tools have different strengths. Routing is part of the workflow.
More context is always better.
Relevant context helps; stale context causes drift and cost.
Practice studio
Learning only counts when you make something.
01
Transcript evidence map
Separate what the video actually says from what you already believe about the topic.
3 source-backed takeaways with timestamps, confidence, and a transfer note.02
One useful artifact
Apply the video to a real workflow and produce a routing matrix for when to use codex, claude, browser checks, or manual review..
A reusable artifact with a done signal and one verification step.03
Teach-back card
Explain the lesson to someone who has not watched the video yet.
A 90-second explanation, one diagram, one example, and one misconception to avoid.
Recall check
Answer first, then reveal — without rewatching.
Why is Remotion needed if Claude is doing the creative work?
What does the one-time setup prompt make Claude Code do?
How can you steer the style of a motion graphic beyond text prompts?
Source shelf
Use the video as a doorway, then verify with primary sources.
