9 YouTube Hook Formulas: Choose an Opening That Fits Your Video

Choose a YouTube hook formula by the job your video does for its viewer. A quick how-to can give the answer immediately. A comparison can begin with the decision. A story can introduce a real obstacle. The useful opening makes the promised subject clear and gives the next scene somewhere to go.

A formula supplies sentence structure, not evidence. Before using any of the nine below, write down what the title promises, what the viewer already knows, and what your footage can establish. YouTube advises using titles that accurately represent the video; its retention guidance also suggests checking whether the opening matches expectations created by the title and thumbnail. Title guidance, opening guidance.

Pick the structure before polishing the sentence

Complete these three lines in your script notes:

Viewer task: After watching, the viewer wants to understand or do ______.

Starting knowledge: They already know ______, but may need ______ explained.

Available evidence: I can show, demonstrate, or verify ______.

For a video about choosing a camera bag for a train commute, the task is a buying decision under specific conditions. A beginner may need to see the packed kit before hearing storage terminology. A comparison opening fits if you can pack both bags with the same equipment. A sweeping claim about the best bag for everyone does not.

These options overlap. Start with the clearest one instead of trying to squeeze several formulas into the same opening.

Nine hook formulas with scripts and tradeoffs

All examples below are invented writing exercises. They are not customer results, product tests, or claims of improved retention. Use them only with details and evidence that your own video can support.

1. Direct answer

Pattern: “To [complete the task], [first useful action or answer]. Here's [a limit or the next step].”

Example: “To keep the project easy to move, put the footage and audio in one project folder. I'll show the folder layout, then check what happens when a file is missing.”

Why it fits: the viewer gets an answer without an extra promise paragraph. The demonstration gives them a reason to continue.

Watch for: treating a simple answer as a secret. If the instruction depends on a specific application or version, name that condition and verify its behavior. A generic file-management example does not establish how every editor handles media.

2. Problem and diagnosis

Pattern: “If [visible symptom], check [specific possibility]. We'll compare [evidence] before changing [the setup].”

Example: “If you can't find yesterday's footage, check where the camera-card copy went. We'll trace one clip through the folders before moving anything.”

Why it fits: viewers can recognize the symptom and see what the investigation will examine.

Watch for: turning a possibility into the only cause. A missing clip may never have copied, may have a different name, or may be stored elsewhere. Preserve the originals while investigating.

3. Result and process

Pattern: “Here's [finished result]. I'll show [how it was made], including [a relevant limit].”

Example: “Here's the desk shot with the cables out of view. I'll show the camera position and the part of the room that still needs to stay outside the frame.”

Why it fits: revealing the result helps the viewer judge whether the process is useful to them. It does not spoil a tutorial whose value is learning how.

Watch for: showing a result you cannot reproduce or hiding cleanup work. If the result is the story's main reveal, consider showing an obstacle instead. The cold-open guide covers planning a scene before the usual setup.

4. Comparison

Pattern: “For [use case], the difference between [A] and [B] is [decision to examine]. Let's compare them under [condition].”

Example: “For filming at a small desk, these two tripods take up different amounts of space. We'll fit the camera in the same position and see what room is left for the keyboard.”

Why it fits: the viewer knows what will determine the decision, rather than hearing a list of specifications without context.

Watch for: a test condition that favors one option unfairly. Show relevant tradeoffs, and do not turn one setup into a universal winner.

5. Qualified misconception

Pattern: “[Common advice] can fail when [specific condition]. Here's [evidence or explanation] and what to check instead.”

Example: “Cropping closer makes the button easier to see, but it can hide the panel you need to find it. I'll compare the tight crop with a view that keeps the panel heading visible.”

Why it fits: it names a real tradeoff and supplies a testable alternative.

Watch for: replacing “can fail here” with “everyone is wrong.” You need evidence for the condition, not a dramatic disagreement with an invented consensus.

6. Constraint challenge

Pattern: “Can I [task] while keeping [real limit]? Here's [starting condition], and we'll check [success criterion].”

Example: “Can I film this overhead shot without a stand beside the desk? Here's the space available. We'll check the frame before deciding whether this setup is usable.”

Why it fits: the limit gives the project a specific question. The footage can show the choices made along the way.

Watch for: inventing a budget, deadline, or restriction because the formula needs stakes. State the actual constraint. Never remove required precautions to make a challenge more exciting.

7. Decision and consequence

Pattern: “[Something happened]. I had to choose between [real options]. Here's [what shaped the decision].”

Example: “The interview recording was usable, but the room noise was obvious. I had to choose between keeping the original answer and asking for another take. Here's what I listened for before deciding.”

Why it fits: the opening gives a story a concrete decision. Background can arrive when it helps explain that choice.

Watch for: presenting a staged problem as a spontaneous event or quoting someone out of context. The decision needs to belong to the real story.

8. Test question

Pattern: “Does [specific change] affect [observable thing] under [condition]? We'll keep [relevant factors] consistent and compare [evidence].”

Example: “Can this bag hold the camera kit shown here and still close without forcing the zip? We'll pack each piece, then check what is pressing against the lid.”

Why it fits: the question identifies what the test can answer before claiming a result.

Watch for: describing a casual comparison as a controlled study. Document what changed, show the limitations, and narrow the conclusion if other conditions shifted. A negative or unclear result can still answer a useful question.

9. Use-case filter

Pattern: “If you [specific situation], check [relevant requirement] before choosing [option]. Here's [the comparison or walkthrough].”

Example: “If you film while traveling by train, check whether you can reach the camera without unpacking the whole bag. I'll show the opening, the packed kit, and what blocks access.”

Why it fits: it tells a particular viewer why the review matters without pretending the product suits everyone.

Watch for: shaming people into an identity, such as “serious creators always buy this.” A use case should help someone make a decision, including deciding the video or product is not for them.

Write different hooks for the same video

Imagine a tutorial titled “Organize Filming Receipts Before Your Next Expense Report.” The planned footage uses invented sample receipts, named folders, and a simple index for finding them. The examples below are alternative drafts, not tested winners.

The first draft identifies a beginner's problem. The second suits someone who recognizes it and wants the process. The third begins the task immediately. Choose by the intended viewer's knowledge and what the first scene can show, not by which line sounds most dramatic.

If the index points to the wrong file, fix the demonstration before claiming the opener is ready. Say what remains unknown about the unlabelled receipt; do not invent its project to complete the example. This is a file-organization exercise, not accounting or tax advice. The words should follow the evidence.

Test clarity with the opening and first scene together

Record a rough version at your natural delivery pace. Include the shot, label, or comparison the words rely on, plus the first scene that follows. Read-aloud timing matters more than forcing every version into eight seconds.

Ask someone close to the intended audience, unfamiliar with the draft:

• What do you expect the video to help you do or understand?
• Which words or visuals were unclear?
• What claim would you want evidence for?
• Does the next scene begin doing what the opening promised?

Write down their answers before explaining your intention. If they expect a different video, revise the promise or context. If the task is clear but the next scene starts another introduction, repair that transition.

This is a clarity rehearsal. A few listeners do not establish which hook will retain more viewers. Use the promise-and-payoff worksheet when a draft keeps teasing an answer without showing progress toward it.

Review the published opening without a universal pass mark

YouTube's intro metric reports the percentage of viewers still watching after 30 seconds. It is a checkpoint for reviewing the opening, not a requirement that the hook last that long. The report offers comparisons with similar-length videos and, where available, audience segments. YouTube's retention-report documentation.

Inspect the footage around an early decline and consider more than one explanation. A title mismatch, unclear demonstration, audio problem, or different audience mix may contribute. Seventy percent is not a universal passing score in this workflow, and a curve cannot identify a winning formula by itself.

Keep the opening wording, chosen structure, footage notes, reporting window, and proposed next edit in your production log. A comparison between different uploads can inform your next draft, but changes in topic, packaging, and audience prevent it from isolating the hook's effect. Use the first-30-seconds review for that investigation.

Before filming, review your hook and first scene with RetentionYT for feedback on the written script. Check each suggestion against the footage you can produce. Script feedback does not inspect actual viewer exits or predict a retention curve.