Render HTML Video

Read shared execution guidance once per task before using tools. It covers existing authorization, model discovery, optional cost checks, imports, and recovery.

render_html_video sends an HTML composition to a HyperFrames renderer and returns a queued video job. This is an explicit-only route. Do not select it for ordinary AI video generation, or merely because a video needs text; use creativeclaw-generate-video unless the user asks for HTML/HyperFrames/code-driven rendering or explicitly accepts that method.

Good uses

• Put precise, animated text, captions, lower thirds, labels, or calls to action over an existing video.
• Make deterministic title cards, logo stings, charts, UI motion, intros, or outros.
• Preserve exact copy, fonts, colors, logo placement, and timing that a generative video model may change.
• Build procedural canvas graphics, WebGL/shader backgrounds, and deterministic 3D product motion.

It is not the right tool for photorealistic scene invention, character motion, or cinematic generative footage.

Choose the source method

• Single HTML (default): use html for basic, short videos and self-contained motion. An HTML catalog example returns the actual document; adapt it and submit its contents.
• Full project ZIP: use project_url for an unchanged project available at a public HTTPS URL, including a ZIP example returned by get_example. Use project_asset_id for an uploaded, private, or locally modified project. Full projects are for advanced videos only when using a ZIP example selected from search_examples, or when the user already has a full HyperFrames project. Ordinary zip and dedicated project assets both work for uploaded projects. Read project packaging for editing and packaging. Complexity alone is not a reason to start a new ZIP project.