Claude Code · Video Automation

How to Use Claude Code to Edit Videos With Remotion

The actual workflow, step by step — not the marketing version.

NULLFRAME · August 29, 2026 · 3 min read

Claude Code is a coding agent — it reads and writes code, runs commands, and iterates based on what it sees. Remotion is a framework for making videos out of React code. Combining them means asking Claude Code to write (or fill in) a Remotion composition, then render it.

The workflow that actually works

  1. Have a working Remotion project already set up — installed, at least one composition rendering successfully. Don't ask Claude Code to set up Remotion and build your first composition in the same session; debug the setup on its own first.
  2. Get a transcript with real word-level timestamps for your clip before involving Claude Code — this is a narrow, well-defined task Claude Code can do reliably, or you can do it separately with Whisper.
  3. Give Claude Code a specific, narrow task: not "edit my video," but "read this transcript, pick the three strongest lines, and write timing data for a callout component that already exists." The narrower the task, the more reliable the output.
  4. Render, watch the actual output, and iterate — don't trust the render succeeded just because the command didn't error. Extract a few frames and check them, or watch the full render.

Where this breaks down

The failure mode isn't Claude Code being unreliable at coding in general — it's asking it to write new structural Remotion code (sequences, audio wiring, animation curves) fresh for every video. That's the step where the same prompt produces a different bug each render. The fix is separating structure (built once, human-reviewed) from content (what Claude Code fills in per video).

A minimal example prompt that works well

Here is a transcript with word-level timestamps: [transcript.json] Here is an existing Remotion component called CalloutCard that takes a "text" prop and a "startFrame" prop. Pick the single strongest, most quotable line from this transcript. Write the CalloutCard usage with the correct text and startFrame (converted from the word's timestamp to frames at 30fps). Do not modify CalloutCard itself.

Notice what this prompt does not ask for: it doesn't ask Claude Code to design the callout, animate it, or decide how it should look. It asks for one specific decision (which line) and one specific calculation (the timing), against a component that already exists and is already tested.

The shortcut

This entire workflow — the tested structure, the narrow content task, the verification step — is what NULLFRAME's templates package up. You paste a clip and a prompt; the structure is already built and hardened.

See the templates

Common questions

Do I need to know React to do this?+
Enough to read what Claude Code writes and sanity-check it — you don't need to write Remotion components from scratch yourself if you're only asking it to fill in content against existing ones.
Can Claude Code cut my raw footage first?+
No — that's a separate, unrelated capability. Claude Code can write code that processes an already-cut clip; deciding what to cut from raw footage is still a manual or specialized-tool task.
Is Codex different from Claude Code for this workflow?+
The core pattern — narrow, well-defined content tasks against pre-built structure — applies to either. The specific prompting details can differ slightly between the two.