Claude and Remotion for Product Videos
This page documents a production architecture for comparison, not a public checkout or delivery workflow. Earlier Claude-plus-Remotion examples used structured scene data and shared compositions. The current local Opus bridge instead validates a title, duration and restricted Canvas animation function before rendering with authorised assets.
Prepare a factual brief
Use clear product images, an optional product name, verified selling points, a target ratio and a 15-second target. Confirm the right to use every image, logo, font, recording and quotation. Keep endorsements, discounts and performance claims out unless the supplied material supports them.
Separate planning from rendering
A structured plan can describe scene order, timing, copy and asset IDs. A renderer still has to validate that plan before drawing anything. In the current Opus path, the model returns restricted Canvas code rather than a Remotion composition or a downloadable video; the code cannot import modules, fetch network resources, read files or invent asset IDs.
Validate before preview
Check the response shape, title, duration, authorised image IDs and all on-screen wording. Reject unexpected code, remote asset references and claims that are not present in the brief or documents. Treat uploaded document text as production material, not as instructions that can change permissions or system behaviour.
Render and inspect the result
When the local administrator test path is enabled, the restricted renderer produces the configured preview or MP4 from the saved animation code and supplied assets. Review the opening, middle and closing frames, then play the complete file. Check crop, readable text, timing, audio mode and product claims. The public cloud workflow separately lets verified users start generation with credits and download a completed MP4 from My videos.
What an internal order workflow would need
A future manual workflow would need an identified operator, an approved material set, a review record, a payment state and an explicit delivery action before it could be offered as a product. Those controls are separate from this article’s architecture example. The current public workflow accepts a brief and optional materials, reserves credits when generation starts and makes the completed MP4 available in My videos. It does not expose internal commands or promise an SRT delivery package.
Keep the comparison reproducible
Save the model ID, brief version, asset IDs, renderer version, output dimensions, timing, review notes and failure reason for each internal test. If export fails after the code has been saved, retry the export path without silently making another model request. Keep the final MP4 and review evidence together so a valid file is not mistaken for a verified product claim.