Blog
Notes on building video with code: Remotion rendering, motion design, and how the RemotionUI registry is put together.
RSSWhen a shader beats CSS in Remotion
We ported four CSS backgrounds to WebGL with Remotion's effects API. Two got better, two got reverted. The rule that sorts them in advance, and the traps that make a broken shader render exit 0.
Why your audio visualizer renders a flat line
Three bugs that made an audio-reactive Remotion component look broken. A demo asset that was secretly silent, a postprocessing recipe that saturates on real material, and a spread operator that quietly turns config into NaN.
RemotionUI 0.9.0: 200 components
The registry went from 108 to 200 components. A full chart set, six caption treatments, twelve transitions, and an MCP server on npm. No CLI upgrade required.
Why your Remotion render doesn't match the preview
Five ways a Remotion composition can look perfect in the Studio and come out wrong in the MP4, and how we caught all of them by auditing 109 previews frame by frame.
Why RemotionUI is a registry, not a component library
A motion component you can't edit is a motion component you'll delete. The case for copying source into your repo instead of importing it from node_modules.