Same script, same footage: a creator rebuilt his talking-head graphics in Remotion and HyperFrames, then retired Remotion
Guney Topcu had Claude Code build motion graphics for one talking-head video twice. Remotion got his months-refined workflow; HyperFrames got the script, the voice track and no revisions. He liked the HyperFrames cut more and says why, and HyperFrames itself moved house today.
The test. In a video posted this morning (7:25 AM MDT), Guney Topcu describes giving Claude Code the same script and the same recorded footage twice. The Remotion version used a workflow he'd refined for months, with his styles and preferences baked in. For HyperFrames he gave Claude only the script and voice recording, asked for a storyboard timed to his speech, didn't review it, and had everything built and rendered in one go with no revisions. It's one creator, one video and his own taste, not a benchmark. He even published the Remotion cut because it finished rendering first.
What he saw. His examples: Remotion opened with the word 'Argon' appearing behind him and a purple panel sliding in. HyperFrames opened dark, moved a light in and lit up the word with a grainy, futuristic look. Where Remotion showed a progress bar for a '1 million tokens' line, HyperFrames rolled the digits like a slot machine and pulled the camera back across glass-like blocks. He then had Claude compare the two renders frame by frame. By that count, the Remotion cut had about 54 seconds with nothing moving and the HyperFrames cut about 18.
The prompt technique is the reusable part. When Claude looked inside the HyperFrames project, it found motion rules it had written for itself before building, including 'the camera never stops' and 'nothing waits empty'. Guney says he never asked for those. He doesn't know whether Remotion would close the gap if given the same rules, and says so. His working loop now: script plus voice recording, ask for a storyboard first, give a broad direction ('visually engaging', 'premium', 'lots of motion') rather than per-element instructions, then carry the pieces he likes into a house style for the next video. He's giving away his kit (backgrounds, text styles, sound effects, a frame-check step, a DaVinci Resolve handoff) through his community page linked in the video. We haven't reviewed it.
HyperFrames news from today. HeyGen's HyperFrames Studio, which it calls 'the video editor built for agents', moved from hyperframes.dev to hyperframes.studio on Oct 27, and old links 301 to the new domain (desktop sign-in still goes through hyperframes.dev). A change merged on main this afternoon adds render --prores-profile, so MOV exports can pick ProRes 4444 (the default, with alpha), HQ, 422, LT or Proxy. That isn't in a tagged release yet; the latest is v0.8.209. HyperFrames is also on GitHub's TypeScript trending list again today.
Our take: if you run Remotion with heavy per-shot direction, try one piece the way Guney did: write the motion rules ('camera never stops', 'nothing waits empty') into the brief yourself and let the agent storyboard from your voice track. That costs little and tells you whether the tool or the brief is doing the work.
Skills & repos in our directory
- HyperFrames skills · Skill, Code-to-video engine
- Remotion · Repo, Code-to-video engine
- claude-motion-explainer · Skill, Motion graphics
- papercut-explainer · Skill, Motion graphics
- heditor · Skill, Motion graphics
- lemo-opuscar · Skill, Motion graphics
More from the Lab
- 'One prompt' motion graphics is mostly a myth. Here's what the good ones actually did
- Code-video engines this week: Remotion adds shatter() and curves(), HyperFrames gets GIF export and a Windows app
- huashu-motion: an open skill that writes the launch film, scores it, and lets you point at the frame to fix it
- HyperFrames: HeyGen's bet that agents should write video as HTML
Topics: HyperFrames · Remotion · Audio, voice & music · Motion graphics skills