> ## Documentation Index
> Fetch the complete documentation index at: https://hyperframes-codex-docs-human-first-refactor.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# Create a product or website video
> Turn a product URL or launch brief into a promo, product tour, or social video.
Use this workflow when the video should market or explain a product, company, app, or website.
Give the agent the real URL when the site’s interface, language, or visual identity should appear in the result. You can also begin from a written brief or script when no site capture is needed.
Use a [faceless explainer](/guides/faceless-explainer) instead when there is no product to show and the visuals should be invented from an idea or text.
## Start the request
```text theme={null}
/hyperframes Create a 45-second product launch video for https://example.com.
The audience is independent designers. Show the real workflow, focus on
how quickly they can share a first result, and end with “Try it free.”
```
The `/hyperframes` router selects the Product Launch Video workflow.
## Approve the direction
Before the build, confirm:
* the audience and single main promise;
* whether the real site should be captured;
* the most important product state or task to show;
* the intended format and length;
* claims, screens, and words that must be exact;
* the final action for the viewer.
## Decide what kind of product video you need
| Goal | Useful direction |
| ------------------------------ | ------------------------------------------------------------------------- |
| Launch or announce the product | Lead with the change and why it matters. |
| Show how the product works | Use the real interface and a clear beginning-to-end task. |
| Create a short social promo | Focus on one message and one action rather than the complete product. |
| Tour a website | Use captured screens as evidence, not as a slow scrolling recording. |
| Work from a script | Tell the agent not to capture a website and provide the approved wording. |
## Review captured product material
When the workflow uses a website, check that:
* the important screens were captured;
* private or irrelevant information is absent;
* the product state is realistic;
* the design feels like the real brand;
* the video is showing evidence, not merely repeating marketing copy.
The agent may reconstruct product interactions as live visual scenes rather than playing a raw screen recording.
## Keep the story narrow
A short product video rarely has room for every feature.
Choose:
1. one audience;
2. one main problem;
3. one product promise;
4. two or three pieces of proof;
5. one final action.
Ask for another version when you need a different audience or message rather than forcing everything into one crowded edit.
## Review in Studio
Use the [Storyboard](/studio/storyboard) to check the message and scene sequence.
Use the [canvas](/studio/canvas) and [timeline](/studio/timeline) to refine the product screens, text, pacing, and transitions.
Before export, confirm that claims shown in the video are current and supported by the product.
## Common problems
| Problem | Better direction |
| ------------------------------------------ | -------------------------------------------------------------------- |
| The video lists every feature | Choose one audience, one promise, and two or three pieces of proof. |
| It looks like a scrolling screen recording | Reconstruct the useful interaction and use captures as evidence. |
| The opening is generic | Show the product or its result earlier. |
| The UI is too small to understand | Focus each scene on one product area and crop deliberately. |
| The brand feels copied incorrectly | Supply the correct fonts, colors, logo, and approved product states. |
Check the complete story, refine visible details, and export versions.
Return to the source-and-outcome chooser.