Skip to main content
The last page pointed a workflow at a website. This one drops the site. Your text is the whole input. Every visual is invented, not captured.

​
Your first win

Paste your text into one prompt to /faceless-explainer. That is enough for a finished explainer. No site, no footage, no design decisions yet. Verified, from the examples page — a ~60-second vertical explainer from pasted text:
/faceless-explainer Turn this into a ~60-second 1080x1920 vertical explainer: [paste your text]. One idea per scene, big typography, diagrams over stock footage, brand color #FF5533 on off-black. Male TTS voice, calm. Embedded captions, keywords highlighted in the brand color.
Rendered from the prompt above, unedited. Note the ~. When you supply a script, the runtime follows the spoken words. So ask for about a minute, not exactly one. See the anatomy for the rest of the skeleton.

​
What this makes

A faceless explainer. Your text becomes a narrated video — an article, notes, a topic, a brief. Every visual is invented per scene: typography, abstract graphics, diagrams, data-viz. The /faceless-explainer workflow does four things. It picks a design system. It reshapes your text into a teaching story. It generates its own TTS narration. Then it builds the video frame by frame. Faceless means there is nothing to capture. No site, no footage, no asset inventory. The visuals are designed downstream. Pick a different workflow when you do have something to show:

​
The knobs that matter

You can steer all of these from the prompt, before you have learned any technique.
Scene density is the single biggest quality lever here. “One idea per scene” turns a dense paragraph into a paced sequence. The workflow reorders and compresses your text to hit it. That is what makes an explainer teach instead of recite.

​
Variants

/faceless-explainer Make a ~30-second 1920x1080 explainer on how HTTPS keeps a request private, for a non-technical audience — the takeaway: your data is sealed before it leaves the browser. Concept angle: one idea per scene, big geometric type, a simple lock-and-key diagram as the centerpiece (swap the metaphor with the topic). Near-black ink on off-white with a deep-blue accent. Female TTS voice, warm and clear. Embedded captions, key terms highlighted in the accent color.
Shorter runtime, landscape for YouTube or an embed. Fewer scenes means the topic has to compress. Naming the takeaway tells the workflow what to keep.Rendered from this prompt with the topic swapped to HTTP caching (cache diagram as the metaphor), unedited — 26s, because the narration sets the length.
/faceless-explainer Make a ~45-second 1080x1920 listicle: “5 habits of fast-shipping teams”. Listicle angle — one habit per scene, each with a big number and a one-line label, escalating energy toward #1. Off-black with a lime accent. Male TTS voice, upbeat. Embedded captions, the habit label highlighted each scene.
The listicle angle gives each item its own scene. Every scene reuses the same number-and-label shape. The result reads as a countdown, not a wall of points.
/faceless-explainer Make a ~60-second 1920x1080 how-to on setting up a CI pipeline, for developers. How-to angle: one step per scene, each built around a simple node-and-arrow diagram that draws on as the narration explains it. Charcoal with a teal accent. Calm male TTS voice. Embedded captions, the step name highlighted.
A how-to leans on diagrams as the load-bearing visual. Describe the diagram shape per step — “node-and-arrow”, or “a pipeline that fills left to right”. Let the workflow invent the specifics.

​
Common failure modes

“60 seconds” instead of “~60 seconds”. Same rule as on the product launch page. It bites harder here, because the script is the whole video. You cannot know a supplied script’s spoken duration until the TTS renders.
  • ❌ a 60-second explainer from this text: ...
  • ✅ a ~60-second explainer from this text: ...
Cramming ideas into a scene. Every faceless visual is invented around a single focal. Overload the scene and there is no clear thing to animate.
  • ❌ explain all five caching layers in one scene
  • ✅ one idea per scene — one caching layer at a time
Asking it to capture or pull real imagery. There is no capture step. A faceless explainer invents its visuals.
  • ❌ pull screenshots from the site and explain the feature
  • ✅ that’s a site or product video — use /product-launch-video
Leaving the look unspecified when you care. There is no brand to read, so the preset picks the palette. If you have colors, name them.
  • ❌ make it look on-brand
  • ✅ brand color #FF5533 on off-black
The workflow this level rides is documented at Faceless explainer — what it takes as input, what it asks you before it builds, and what it returns. Next: Code changes and PRs — point a workflow at a merged GitHub PR instead of a blank page.