How to write a hook for a faceless video, and score it before you publish
Four properties separate an opening line that holds viewers from one that loses them, and all four are checkable in the eight words you have.
The first three seconds of a faceless video are the whole negotiation. A viewer who scrolls at second two costs you nothing to produce and teaches you nothing either, because you will never learn which part they rejected.
"Is my hook good?" is a question you cannot answer before production. The question that helps: "which properties of this line can I check before anything gets produced?" There are four, and all four fit inside about eight words.
What a hook has to do in a faceless video#
A hook has one job: create an obligation to stay. Concretely, it puts a claim in the room that the viewer wants to check. A question about their experience asks permission instead, and permission can be refused: they answer "no" internally and the thumb keeps moving.
The format tightens the requirement. The viewer sees no face speaking for you and does not know your channel. The decision about your opening line happens on that line alone, inside the first three seconds.
The eight-word rule#
Writing a hook means running four checks on the opening line: the opener, the claim, the length and the number. All four fit inside the eight words a line has before the curiosity gap closes.
1. Do not open with a question about the viewer#
"Have you ever wondered why…", "Did you know that…", "Ever had this happen to you?"
We rated 63 hooks across three benchmark runs. The ones that opened this way averaged 2.77 out of 5. The ones that did not averaged 3.81. That is a full point of difference decided by the first two words.
Greetings are the same failure with less content. "Hey guys, welcome back" spends the only three seconds that matter on nothing at all.
2. Make it a claim, not a question#
In the same benchmark data, statements outscored questions by 0.79 points. This is the rule people resist most, usually with a counter-example: "Why Rome's concrete outlasts ours" starts with an interrogative and is obviously a strong hook.
It is a strong example because it opens a claim. It has no question mark, and nothing in it can be answered "no". A leading "why" or "how" that introduces a claim is fine. A line ending in "?" is the thing that loses people, because it hands the viewer a decision at the exact moment you want them to have none.
3. Eight words#
Past roughly eight words, the curiosity gap has already closed: you have explained enough that staying is optional. Eight works as a ceiling, and the ceiling forces a choice about which single idea survives.
The practical test is brutal and fast. Read the line aloud. If you take a breath in the middle, it is too long.
4. Put a number in it#
"This saves you loads of time" and "This saves you 6 hours a week" are the same claim at different resolutions. Only one of them creates an obligation to stay: a viewer who wants to know whether 6 hours is real has to watch.
A digit, a year, a percentage or a count all work. A vague intensifier does not: "massively faster" is a feeling and 6 is a fact that can be checked.
Five hooks, scored#
Everything above can be graded before the first frame renders. Unfaced runs the same four checks on every opening you type in the studio: 30 points for the opener, 25 for the length, 25 for the claim, 20 for the number. That is 100 in total, and the same line always produces the same number. Each score below grades the opening line; where an example carries a second sentence, that sentence is the evidence which follows the line.
Four hooks, rewritten#
| Before | After | What changed |
|---|---|---|
| Have you ever wondered why the Titanic sank so fast? | The Titanic sank in 2 hours 40 minutes. It should have taken days. | Opener, question, number |
| Let's talk about the deep ocean | 6 people have been to the Mariana Trench. 12 have walked on the moon. | Greeting removed, specificity added |
| Did you know Rome had concrete better than ours? | Roman concrete gets stronger for 2,000 years. Ours cracks in 50. | Claim instead of question |
| This trick will massively improve your retention | Moving the hook 3 seconds later lost this channel 40% of its viewers. | Intensifier replaced with a figure |
Five finished lines with their scores (opening line, 0 to 100):
| Opening line | Score | What the check sees |
|---|---|---|
| The Titanic sank in 2 hours 40 minutes. | 100 | all four checks passed |
| 6 people have been to the Mariana Trench. | 100 | all four checks passed |
| Roman concrete gets stronger for 2,000 years. | 100 | all four checks passed |
| Moving the hook 3 seconds later lost this channel 40% of its viewers. | 75 | 13 words: the 25 length points drop away |
| Why Rome's concrete outlasts ours | 80 | no number: the 20 specificity points are missing |
The fourth line loses only the length points. It carries two figures, and the check needs one; the other belongs in the evidence after the line. The "why" line from rule 2 loses only the 20 points for the number, and that number is what turns interest into an obligation to stay.
Check the hook before you publish#
The check before publishing takes less time than the production it saves. Three steps are enough: read the line aloud, run the four checks, and confirm the evidence in the first seconds pays off the promise of the line. A strong hook promises something concrete and delivers the evidence right after it.
For the rest of the script after the line: the 15 beats of a high-retention faceless script.
The difference between a score and a measurement#
Everything above is a writing aid. It is deterministic: the same line always produces the same number, which is exactly why it can update while you type. The number is a rule you apply while typing, and it says nothing about your audience yet.
That is not the same thing as knowing. A measured hook score needs a real retention curve behind it: the share of viewers still watching at the opening, weighted at 0.7, plus the average percentage of the video watched, weighted at 0.3. That number does not exist below roughly 100 views, and a tool that shows you one earlier is showing you a guess wearing a measurement's clothes.
Both are useful. Confusing the two leads a creator to optimise a score and lose the audience out of view.
What this is actually for#
The point of a checkable hook is to stop putting production time into lines that were disqualified before the first frame rendered. A perfect score is not required for that.
Write six openings for the same video. Score them in the ten seconds it takes. Throw away the four that open with a question or run past eight words, then argue about the remaining two with a human. Those two are the only lines worth the argument.
Four tools pair well with this. Our hook generator writes openings against these rules if a blank line blocks you, and the title analyzer applies the same specificity test to the title that sits above them. The script timer converts the eight-word rule into seconds at your narrator's pace, and the retention risk checker reads the rest of the script around the winning line. Once a hook is written, how to read a retention graph is the other half of the job: it is how you find out whether the line actually held anyone.