Core1
HyperFrames
Use it as the core video capability for an HTML, CSS, JavaScript, UI and browser-rendered production route.
Focused child workflow1
Website-to-HyperFrames
Use this HyperFrames child workflow for turning an existing website, SaaS page or landing page into a promo video.
Optional2
ImageGen
Add it only when the website does not provide enough illustrations, backgrounds or scene assets.
Generative Polish
Add it after the main visuals are complete when the final atmosphere or visual texture needs improvement.
Usually skip1
HeyGen
A website promo without an avatar-presenter requirement usually does not need this route.
Where do the tools overlap?
Identify overlapping routes before deciding whether both tools need to stay.
FUNCTION OVERLAP
HyperFrames and Website-to-HyperFrames are a parent-child pair
SharedWebsite and UI motion · Browser-rendered video workflow
DifferenceHyperFrames is the parent capability; Website-to-HyperFrames is its focused workflow for turning an existing website into a promo.
Treat them as a core plus a specialized workflow, not as two peer video frameworks competing for the same role.FUNCTION OVERLAP
ImageGen vs Generative Polish
SharedBoth can support the visual quality of a promo
DifferenceImageGen creates missing image assets; Generative Polish refines visuals that already exist.
Add only the capability that addresses the actual gap at the current production stage.What are you trying to make?
This setup is for someone who already has a website, SaaS product page or landing page and wants to turn it into a product promo. The goal is not to assemble a broad video toolkit. It is to build one clear presentation workflow around the site that already exists.
Keep the parent-child relationship clear
HyperFrames is the core video capability. Website-to-HyperFrames is its focused child workflow for turning an existing website into a promo. They are not two independent peer frameworks, and you do not need to shop for a separate replacement for each one.
That relationship matters when you count tools: this is one core route with a specialized workflow, not two competing video systems.
Add assets and finishing only when needed
Consider ImageGen only when the website itself does not provide enough illustrations, backgrounds or scene assets for the final video. Consider Generative Polish after the main motion is complete when the result still needs a more deliberate atmosphere, lighting or visual texture.
If the promo does not include an avatar presenter, HeyGen is usually unnecessary.
What should you usually skip?
Do not add an avatar-video route just because the output is a video. Do not add image generation when the website already contains sufficient visual material, and do not add a finishing capability before the core website-to-promo sequence works.
Installation order and cleanup
First produce a minimal promo with HyperFrames and the Website-to-HyperFrames workflow. Then identify whether the project truly lacks an asset or a finishing pass. Add one supporting capability at a time and remove it when the production no longer needs the role it serves.
Website-to-HyperFrames, ImageGen and Generative Polish now have reviewed detail pages. Their links are available, but each capability remains optional unless it solves a specific gap in the promo workflow.
Related terms
Continue with these published explanations.
Sources & last checked
Sources supplied by the reviewed editorial pack. The check date records our pack cross-check, not a new live verification of these websites. Examples illustrate the concepts.
Official documentation
01Last checked: September 4, 2026