Who it is forA developer or marketer who needs a quick branded title or intro card and already works in a Node.js project.
The problemMaking a simple animated title card in a desktop editor takes manual timeline work for every version.
The outcomeAn MP4 file at output/hero.mp4 that you can regenerate by running the script again after editing text or colors.
What you need first
- Node.js 22 or newer
- pnpm, to run `pnpm add framefields`
- A GPU with WebGPU support (macOS Metal, Linux Vulkan, or Windows D3D12)
- A coding agent such as Claude Code, Cursor, or Codex, if you want the agent to write the composition
Steps
- Confirm Node.js 22 or newer is installed and that your machine has a WebGPU-capable GPU.
- Run
pnpm add framefields - Create a script that builds a Composition with width 1920, height 1080, fps 60, and a Layer.box with Layer.text children, following the README quickstart.
- Add a LayerAnimation with fadeIn and fromTo entries, then call comp.renderVideo with outputPath set to output/hero.mp4 and quality set to high.
- Run the saved script with Node.js, for example
node render-hero.mjs, then open output/hero.mp4 and check the text, colors, and entrance motion. (inferred, check the README)
Prompt for your agent
Using the framefields repo, write a TypeScript script that builds a 1920x1080, 60 fps composition with a title card reading <title text>, renders it with renderVideo to output/<file name>.mp4, and runs it. Expected output: an MP4 at that path. Verify the file exists and that the printed Rendered to path matches it.
Caveat. The README quickstart is the only confirmed code path, so test the render on a short composition first to confirm your GPU and Node.js setup works before building longer videos.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page