
An intro has one job: buy attention for the next thirty seconds. It is not a logo parade, and it is not an excuse to show off a render. Done well, an intro tells a viewer what kind of experience they just clicked into, sets a tone, and makes the rest of the video feel intentional rather than assembled.
What changed is the cost of iteration. A few years ago, producing three alternative openings meant three separate edit sessions, three music licenses, three rounds of feedback from stakeholders who could not visualize anything without seeing it. Today, a generator can produce a dozen plausible visual directions before lunch, and the bottleneck shifts from production to judgment. That is a better problem to have, but it is still a problem: more options means more ways to ship something generic.
This guide is a workflow, not a tour of features. It covers how to brief an intro, how to script it for machines that render literal descriptions, how to prompt video generators reliably, how to edit the output into something that feels authored, and how to catch the failure modes that make AI footage look like AI footage.
The most common mistake is opening a tool first. The second most common mistake is writing a brief so vague it cannot guide a decision. A useful brief for an intro fits on one page and answers questions a stranger could act on.
Counterintuitively, the more constraints you write down, the faster generation goes. "Make me something cool" produces slop. "A slow push through a rain-slicked alley at night, neon signage out of focus, anamorphic flare, no people, camera never stops moving" produces something you can use or reject on the merits.
Decide the duration before you generate. A fifteen-second intro and a forty-five-second intro are different projects, not different trims. Short intros need a single idea executed cleanly; long intros need a beat structure or they feel like padding.
Most intros that work follow a three-beat shape, even when they feel formless.
Keep a shot longer than 0.8 seconds unless the cut is deliberately percussive. Cut on musical phrases, not on arbitrary timestamps. Never place critical text during a camera move that makes it hard to read. If the first frame is a black screen or a slow fade-in, fix it: the first frame is also the thumbnail-adjacent frame viewers see when scrubbing.
Longer openings make sense when the video itself is long-form and the intro functions as a title sequence, or when the content is episodic and the intro is a ritual viewers expect. In both cases, the intro should be built from a repeatable template with swappable footage, so episode twelve costs minutes rather than days.
Video generators do not understand intent. They understand nouns, verbs, and visual adjectives. Rewrite your script with that in mind, or you will spend an afternoon regenerating a shot that was never describable in the first place.
| Time | Beat | Visual | Audio |
|---|---|---|---|
| 0-2s | Hook | Macro shot, liquid moving in slow motion, shallow depth of field | Low synth swell, single percussive hit |
| 2-6s | Context | Camera pulls back; surface resolves into a desk edge | Riser begins |
| 6-12s | Product | Clean push across a screen showing a dashboard, slight parallax | Music drops to a pulse |
| 12-18s | Human | Over-shoulder view, person typing at normal speed, no face detail | Typing foley, quiet |
| 18-22s | Signature | Logo resolves from the same light source, tagline fades in | Final hit, tail silence |
Notice that every row is something a camera could capture. That is the test to apply to your own script before you generate a single frame.
A prompt that produces consistent results is structured, not poetic. Build it from slots, and change one slot at a time when iterating.
[Shot type] + [subject] + [action] + [camera movement] + [lighting] + [lens/style] + [mood] + [negatives]
Example: "Medium close-up of a ceramic mug on a steel counter, steam rising and curling left, slow dolly in, warm side light with a hard shadow, 50mm look with shallow depth of field, calm morning mood, no people, no text."
Cinematic brand film. "Wide establishing shot of an empty glass corridor at dawn, light moving slowly across the floor, camera glides forward at walking pace, cool blue shadows with warm bounce from the right, anamorphic lens, restrained corporate mood, no people, no logos."
Kinetic social intro. "Overhead shot of paint swirling into clear water, ink blooming outward in sharp detail, camera locked off with slight rotation, bright even lighting, high-contrast macro style, energetic mood, no text, no hands."
Abstract explainer. "Slow-motion shot of geometric glass shapes assembling into a grid, shapes sliding into alignment, camera orbiting gently, soft studio lighting with subtle gradients, minimal product-render aesthetic, precise and technical mood, no characters, no captions."
Change one variable per generation round. If you alter camera movement and lighting at once and the result is wrong, you learn nothing. Keep a written log of what you changed and what improved. When you land on a shot you like, save the prompt and a reference frame; matching that look later is far easier when you kept the recipe.
Batch generously, review ruthlessly. Generate four to eight variants per shot, but delete anything that does not serve the brief within the first pass. A library of mediocre takes slows you down later.
Not every intro needs generation. The right route depends on how much brand fidelity you need and how much time you have.
A practical decision rule: if the intro must show a real product, a real person, or exact brand typography, generate the environment and design the rest. If the intro is about mood, generate everything.
Raw generations are raw material. The intro appears in the edit.
Lay the music bed first and cut to it, rather than cutting picture and hunting for a track that fits. Trim each clip to remove the first and last few frames, where motion usually wobbles or resolves awkwardly. Use speed ramps sparingly; a 100 to 110 percent change plus a clean cut often looks better than an obvious ramp.
Generated clips rarely share a color response. Apply a consistent grade across all shots: normalize white balance, match contrast, and unify saturation. A light film grain layer helps bind disparate sources together. If one shot is noticeably softer, reduce sharpening elsewhere rather than over-sharpening the soft clip.
Place text on a stable frame or on a very slow move. Keep the safe area in mind: leave margins so platform UI does not cover your tagline. Animate the logo in from the same motion direction as the preceding shot, so the transition feels continuous rather than pasted on.
Watch the intro three times before approving it: once at full attention, once muted, and once on a phone at arm's length.
Does the first frame work as a still? Does the last frame cut cleanly into the opening of the main video? Does the intro still make sense with the sound off, since a large share of viewers watch muted? Does anything in the imagery accidentally contradict the promise you wrote in the brief?
Confirm frame rate, resolution, and color space match the rest of the video. Verify captions or subtitles, if used, are legible against the busiest frame. Check that the export does not clip audio peaks.
How long should an AI-generated intro be?
Fifteen seconds is a safe default for most online video. Ten seconds works if the hook is strong. Anything over thirty seconds should either be a designed title sequence or justified by episodic repetition.
Can I use AI video for a client project?
Yes, but treat generated footage like stock: keep records of the prompts and source references, avoid generating recognizable people or protected characters, and disclose your process where the client expects it.
Why does my generated footage look slightly wrong even when the prompt is good?
Usually it is consistency, not quality. Each clip has its own lighting and color response. Grading all clips into one look and adding grain will fix more perceived issues than another round of generation.
Do I need a video editor, or can I finish inside the generation tool?
You can finish simple intros inside a generation tool, but sound design, timing, and typography are usually faster in an editor. The generation tool's job is to give you shots; the editor's job is to give them rhythm.
How do I keep a character consistent across shots?
Use reference images in every generation, keep the prompt skeleton identical, avoid changing camera distance drastically, and keep the character's face partially turned or in motion where possible.
What is the biggest quality lever?
Sound. Viewers forgive imperfect visuals far more readily than they forgive a jarring audio cut, a music bed that stops abruptly, or a mix that jumps in loudness between the intro and the main content.
Should the intro always match the video's visual style?
It should feel like the same production. A stylistically unrelated intro reads as an advertisement attached to the front of a video, and viewers respond to it accordingly.
How many generations should I budget per shot?
Plan for four to eight, and expect to use one. If you are rejecting everything past ten attempts, the prompt is describing something the model cannot show. Simplify the shot.
The first AI-assisted intro you build will take longer than expected. The second will take half as long, because you will have a brief template, a prompt log, a grade preset, and an audio bed you already know works. Treat the process as a small production system rather than a one-off favor to your channel.
Start with one fifteen-second intro. Write the five-line brief. Structure it in three beats. Write four prompts using the formula. Generate a batch, pick the best frames, grade them into one look, and cut to a track with a clear hit at the two-second mark. Run the quality control pass, then export a horizontal and a vertical version. When you are done, save everything: the prompts, the grade, the project file. That saved package is the actual asset, and it will pay for itself the next time someone asks you to make an intro.

Alexander
Vidu Q4 alternatives compared: Kling 4.0, Seedance 2.5, Wan 3.0, and Runway Gen-4 — 4K support, input modes, durations, audio, and what each costs in credits on Domer.
The top 4K AI image generators on Domer compared: Flux 3 Klein, Nano Banana 2.1, GPT Image 2.5, GPT Image 2, and Nano Banana Pro — 4K credit costs, reference limits, and speed.
Nano Banana 2.1 vs GPT Image 2.5 Flare compared: credit costs per resolution, aspect ratios, reference images, text rendering, and which tasks fit each model.