Explainer Video
Turn a product or concept into a 60 to 90 second explainer with a script timed to shots, so the visuals carry what the words cannot.
Write and shot-list an explainer video. What we are explaining: [PRODUCT, FEATURE, OR CONCEPT] Who is watching and what they already know: [AUDIENCE + BASELINE] The one thing they should understand afterward: [THE SINGLE TAKEAWAY] What they should do next: [THE ACTION] Length: [60 / 90 / 120 seconds] Visual style: [SCREEN RECORDING / MOTION GRAPHICS / LIVE ACTION / MIXED] Voice: [VOICEOVER / ON-CAMERA PRESENTER / TEXT ONLY] Structure the script in five movements, with a target word count for each based on 140 spoken words per minute: 1. **The problem (0 to 10 seconds)**: the viewer's situation in their own words, specific enough that they recognize themselves. No company introduction, no logo, no "in today's world". 2. **The stakes (10 to 20 seconds)**: what it costs them to keep doing it that way. One concrete consequence. 3. **The idea (20 to 40 seconds)**: what the thing is and the one mechanism that makes it work. Not a feature list. If a viewer can only remember one sentence, this is it. 4. **The proof (40 to 70 seconds)**: show it working on a real task, start to finish. This is where the visuals do the explaining and the words step back. 5. **The next step (last 10 seconds)**: one action, stated plainly. Deliver it as a table with a row per beat: | Time | Voiceover or on-screen text | What is on screen | Why this visual | Rules: - The visual carries the explanation and the words carry the meaning. Never narrate what is already visible on screen; that pairing wastes both channels. - One idea per beat. A beat trying to say two things says neither. - Concrete language. Every abstraction gets replaced with a specific thing the viewer can picture. - Write for the ear: short sentences, the important word last, no clauses inside clauses. - Assume it plays silently first. Every essential point must be readable from the visuals and on-screen text alone. Then give me: the first 5 seconds written three different ways, and the one sentence to cut if this needs to be 15 seconds shorter.
How to use
Never narrating the visuals separates a good explainer from a slideshow with a voiceover: when the words describe what the viewer is already seeing, two channels are doing one job. Treat the silent-playback requirement as mandatory for social distribution, where most views start muted and the first seconds decide whether sound gets turned on at all.
More video prompts
[Attach your first frame image, and the last frame image if your tool supports it, then use this prompt:] Animate from the first image to the last image. What changes between them: [THE ONE TRANSFORMATION, e.g. "the closed box opens and the product rises out of it" / "the empty street fills with morning light" / "the character turns fro
First and Last Frame Control
Direct a video model between two fixed images so the motion, timing, and transition land exactly where you need them for an edit.
Generate a sequence of shots featuring the same character. **Step 1: write the character lock.** This exact text goes into every shot prompt, word for word, before anything else. Never paraphrase it. CHARACTER LOCK: "[NAME], a [AGE] year old [DESCRIPTION: build, height impression], with [HAIR: exact length, color, texture, and how it is
Multi-Shot Character Consistency
Keep one character looking like the same person across separately generated shots using a locked description block and fixed style spine.
A repeatable pipeline for a faceless channel. Run each step, check the output, then paste it into the next. **Step 1: The script.** ``` Write a [60 / 90 / 180] second script about [TOPIC] for a [NICHE] channel. Audience: [WHO WATCHES AND WHY] Channel voice: [e.g. "calm and factual" / "fast and irreverent"] Format: [top-list / single st
Faceless Channel Pipeline
A four-step chain from topic to finished faceless video: script, shot list, generation prompts, and the metadata to publish it.