YouTube Shorts hooks: 5 patterns for the first 3 seconds

On a long YouTube video, the thumbnail and title do the selling before anyone presses play. In the swipe-through Shorts feed (and in Reels) there is no click to win: the video plays as soon as it appears. (Shorts in search and on your channel page still show a thumbnail, so set one, but the feed is where a viewer decides in an instant.) You have about three seconds, and they split into three jobs: frame 0 (the very first frame the viewer sees) has to show a situation, the first caption line has to state the hook, and motion has to start at once. Here are five patterns that do all three, for fiction and non-fiction, then the rules that make them work.

5 YouTube Shorts hook patterns (with examples)

1. Start at the consequence. The viewer stays to learn how it happened. Fiction: Frame 0, a door hanging off its hinges, the room behind it dark. Caption: “It got in at 3:12 AM.” Non-fiction: Frame 0, the finished dish. Caption: “This took four minutes, not forty.” Template: “This took [short time], not [long time].”
2. Let the picture ask the question. Show something that does not make sense yet. Fiction: Frame 0, a phone screen with three missed calls, all from my own number. Caption: “I was holding my phone the whole time.” Non-fiction: Frame 0, a laptop with every key taped over. Caption: “Why I coded like this for a week.” Template: “Why I [strange thing] for [time].”
3. State a rule, then break it. Viewers stay to see what happens. Fiction: Frame 0, an intercom light blinking in a dark corridor. Caption: “Never answer the intercom after 2 AM.” Non-fiction: Frame 0, a terminal showing a failed deploy, the clock reading Fri 17:58. Caption: “Never push to main on a Friday. I did.” Template: “Never [rule]. I did.”
4. Put a clock or a stake on screen. A visible countdown makes every second count. Fiction: Frame 0, an empty platform, the board counting down LAST TRAIN 00:59. Caption: “Someone is still on the platform.” Non-fiction: Frame 0, a timer at 60 seconds. Caption: “Deploying an app before this hits zero.” Template: “[Hard task] before this timer hits zero.”
5. Make a specific, checkable promise, and keep it. Name the payoff precisely and deliver it before the end; a vague or broken promise trains people to swipe your next one. Fiction: Frame 0, a sealed envelope marked OPEN AT 3 AM. Caption: “By the end, you will know what is inside.” Non-fiction: Frame 0, the same clip split in two, one half soft and one half crisp. Caption: “Three export settings make the right half.” Template: “By the end, you will [specific result].”

Each pattern works without a face on camera, which is why they suit faceless and animated channels. More on that in our guide to hooks that work without a face.

How long should a Shorts hook be?

Three seconds, front-loaded: frame 0 and the caption must land within the first second, before a thumb moves, and the question the video will answer must be clear by second three. Anything that needs explaining belongs after that, when the viewer has already decided to stay.

Write the Shorts hook before the story

Most weak openings come from writing the story in order and hoping the start is interesting. Reverse it. Write frame 0 as a single still and one caption line first. Then ask what the viewer now wants to know, and build the beats that answer it, raising a new question each time. The ending pays off the hook, ideally with a final image that flows back into frame 0, so the loop invites a second watch.

Shorts hook text: the first caption line

• Short: three to six words read in about a second; ten words is the most, and takes two to three seconds.
• Readable with the volume off. The caption alone should carry the hook.
• Inside the safe area. Keep text out of the top band (search and menu icons), the bottom band (title, channel name, description) and the right edge (the buttons). Check on a real phone, not only in the editor.
• No greeting, no channel name, no “in this video”. They spend the only second you have.

Add motion in the first second

A still opening reads as a slideshow, and slideshows get swiped. Motion should start on frame 0 and be visible within the first second: a slow push-in, a light that slowly pulses, a shape crossing the frame. Keep any flashing to no more than three flashes per second (the WCAG threshold for viewers sensitive to flicker). Skip logo stings and fade-ins from black. If the story needs a quiet moment, put it later, after the viewer is invested.

A quick hook test: before you render and before you post

Export frame 0 with its caption as an image. Show it to someone who knows nothing about the video, or to a fresh AI session with no context, and ask one question: “What do you think is about to happen, and why would you keep watching?” If they cannot say what is at stake, rewrite the opening. It takes a minute and saves a render. Then, before you post, check the finished cut:

• Frame 0 shows a situation, not a title card.
• The first caption line carries the hook on its own, inside the safe area.
• Motion starts within the first second.
• The viewer can name the question the video will answer.
• The ending answers it, and the last frame leads back into the first.

How to measure a Shorts hook: viewed vs. swiped away

Open a Short in YouTube Studio, go to its analytics and look for viewed vs. swiped away: the share of people in the feed who watched rather than swiping past. It is the clearest measure of your opening, and it appears once a Short has had enough feed views. Compare it across Shorts of similar topic and length, change one element of the opening from one Short to the next, and keep what raises it. Small samples are noisy, so judge a change over several Shorts, not one.

Make it repeatable with Claude Code

Hook writing gets better with volume: ten openings per video, then the best one. Put the patterns and the checklist in a Claude Code skill, and Claude can draft ten openings from your episode spec (a one-page brief: premise, beats, ending) and score each against the first two checklist items and the question test. The safe area is then checked on the frame 0 export, and motion on the first second of the render. How to write a SKILL.md shows how to structure such a skill, and the AI horror Shorts workflow shows where the hook sits in a full production. If you make fiction, horror in particular, the skill below packages this hook-first method for Claude Code.