Remotion → CapCut
remotion-to-capcut converts a Remotion composition into a real CapCut draft, so the user can keep editing by hand
what you built in code. Windows + CapCut desktop only for now.
Export
Run from the Remotion project folder:
npx github:OybekWeb1/remotion-to-capcut doctor
Fix anything marked ✗ first (CapCut must be installed and opened once; Python 3.8+ must be on PATH).
npx github:OybekWeb1/remotion-to-capcut list
npx github:OybekWeb1/remotion-to-capcut <CompositionId> --name "<name shown in CapCut>"
- Takes roughly 1 minute per 6 seconds of video. Run it in the background for long videos.
- CapCut must be closed while the draft is written. If it is open the tool waits (
--wait <seconds>, default 600); ask the user to close CapCut — never kill it yourself (they may have unsaved work). If it times out, re-run with--skip-captureonce CapCut is closed; that reuses the capture and only takes seconds. - When it finishes, read
out/capcut/<CompositionId>/summary.txtand tell the user what became native texts and clips, then: open CapCut → Projects → the draft name. - Iterating on a slice:
--frames 0-299. Composition props:--props props.json.
Write Remotion code that converts well
The converter inspects the rendered DOM frame by frame. What it can turn into editable CapCut items:
| In Remotion | In CapCut |
|---|---|
Text in normal DOM elements (<div>, <span>, <h1>…) | Native text layer: font, size, colour, gradient, shadow, stroke, letter/line spacing |
transform (translate / scale / rotate) and opacity on text or footage | Position / scale / rotation / opacity keyframes |
<OffthreadVideo> / <Video> with a file from public/ | The raw clip, trimmed where Remotion trimmed it, with speed |
<Audio> from public/ | Separate audio clips with volume curve |
| Everything else (cards, shapes, logos, images, SVG, light leaks) | One transparent "graphics (alpha)" video layer above the footage |
Rules of thumb:
- Keep text as real text. No text inside SVG, canvas or images. One text block per element; style runs inside
it (
<span>with another colour/weight) are fine. - Use Google Fonts (
@remotion/google-fonts). The matching TTF is downloaded automatically; other fonts fall back to CapCut's default font. - Animate with transform + opacity. Blur-in, clip-path reveals and per-letter effects do not exist as CapCut keyframes: the text will just move/fade. Counting numbers show their final value.
- Footage and audio must be local files in
public/referenced withstaticFile(). Remote URLs are not supported. - Do not blur footage with CSS if the user should be able to swap it: clips with
filter: blur()over 1.5px stay baked into the graphics layer. - Put the background footage as one gap-free sequence (CapCut's main track is magnetic); extra clips go on upper tracks.
- To deliberately keep something as pixels (a complex animated title, say), wrap it:
<div data-capcut="bake">…</div>.
Tell the user the limits
- Graphics are one flat layer: if they lengthen a text, the card behind it does not grow.
- Transition frames and blurred backgrounds are baked into the graphics layer.
- Text metrics were calibrated on CapCut 9.7; other versions may be a few pixels off.
- The CapCut draft format is undocumented; a CapCut update can break this.