---
title: "Create a faceless explainer"
sidebarTitle: "Faceless explainer"
description: "Turn notes, an article, or a difficult idea into a visual explanation without product footage."
---

Start from a topic, article, or notes. HyperFrames invents the typography, diagrams, abstract graphics, and data visualization that teach it.

<Frame caption="A short preview from a SpaceX valuation explainer. Every visual was invented from the question and numbers.">
  <video
    className="aspect-video w-full object-cover bg-zinc-100 dark:bg-zinc-900"
    src="https://static.heygen.ai/hyperframes-oss/docs/images/showcase/wfv2-explainer.mp4"
    poster="https://static.heygen.ai/hyperframes-oss/docs/images/showcase/wfv2-explainer.jpg"
    autoPlay
    muted
    loop
    playsInline
    preload="metadata"
  />
</Frame>

## Make the request

Attach or paste the source material:

```text
Using /hyperframes, turn these notes into a short visual explainer for a
general audience: [paste notes]
```

The agent proposes the teaching angle and asks about information that must stay
exact. A topic alone is enough to begin; a script is useful only when its words
are already approved.

## How should the idea land?

- **Understand one idea** — open with a useful question, then reveal the mechanism one layer at a time.
- **Follow a process** — keep one visual stage and show each step in the order the viewer needs it.
- **Remember three points** — make the ideas parallel, concrete, and visually distinct enough to recall later.
- **Learn through a story** — use one case to move from setup and tension to a general lesson.

If you supply an approved script, say whether HyperFrames may restructure it or
must keep every word.

Use a [product and website video](/guides/product-launch-video) when the real interface should provide the proof. Use [captions or designed overlays](/guides/captions-and-recuts) when existing footage should remain underneath.

## From information to understanding

HyperFrames does not turn each paragraph into a scene. It finds the teaching spine, removes asides, and builds a sequence around the one idea the viewer should retain.

The visuals share one coherent language and develop with the explanation. A diagram should reveal a mechanism; a chart should prove a claim; motion should show what changes.

## Review whether it teaches

- The opening creates a question, tension, or surprise.
- The main idea is clear by the second scene.
- Each body scene advances one mechanism, step, example, or implication.
- Numbers and factual claims match the source.
- The ending lands the sentence you wanted the viewer to remember.

Ask the agent when the teaching sequence or evidence must change. Use
[Storyboard](/studio/storyboard) to inspect the sequence directly, or Studio
for a precise visual, timing, or animation correction.

<Card title="Finish and share" icon="circle-check" href="/guides/export-and-share">
  Check the final project, render through your preferred surface, and review the file.
</Card>

## Related topics

- [Prompt for explainers](/prompting/explainers)
- [Review the storyboard](/studio/storyboard)
- [Create a product video from real screens](/guides/product-launch-video)