Build a cinematic year-in-review TikTok with AI: plan the story, gather assets, prompt shots, edit fast, and export a vertical video people finish.
A year-in-review video is not a photo dump with a trending song glued on top. It is a short film about twelve months of your life, squeezed into 45 seconds that a stranger will actually finish watching. The good news: you do not need keyframes, color wheels, or an audio waveform you can read. You need a story skeleton, a folder of raw material, and a workflow where shots come from written prompts instead of hours of timeline surgery.
Below is a complete path from "I have 300 photos and no plan" to a finished vertical video — how to pick the beats, collect assets, write prompts that produce cinematic shots, edit for retention, and export something that still looks sharp after the platform recompresses it.
Why reflective recaps keep earning attention
Recap content has a structural advantage most formats lack: it arrives with a beginning, middle, and end built in. January to December is a narrative arc whether you plan it or not, and that arc gives viewers a reason to stay until the last frame — the strongest signal short-form platforms measure.
Three things make a recap work:
- Recognition. Viewers compare your year to theirs. A specific detail ("the 6 a.m. bus that smelled like rain") beats a generic highlight reel every time.
- Momentum. A recap promises change. If the first three seconds suggest transformation, people wait for the payoff.
- A clean ending. Most short videos fumble the last two seconds. A recap can land a line, a title card, or a callback to the opening shot instead.
The trap is treating the format as an archive. Nobody wants a chronological inventory. They want a curated feeling — the version of the year you would tell a friend about in a lift.
Build the story before you open any tool
Story first, footage second. This is the step creators skip, and it is why so many recaps feel like a slideshow with a beat drop.
The three-act skeleton for a 45-second recap
- Act one, 0–5 seconds: the hook. One line of text, one striking image, one promise. No logos, no "hi guys."
- Act two, 5–35 seconds: three to five beats. Not twelve. Pick the moments that changed direction: a move, a job, a loss, a person, a skill you finally learned.
- Act three, 35–45 seconds: the turn. What the year taught you, and what you are walking into next. End on the most visually interesting shot, not the most recent one.
Write the beats as plain sentences on a note before you write a single prompt. "I moved to a city where I knew nobody." "I learned to cook because I was broke." "I stopped waiting for a message that never came." Those sentences are your shot list; everything after that is execution.
The hook is a promise, not a greeting
Compare "My year in review" with "I deleted the plan I made in January." The second creates a question the viewer wants answered. Strong hooks usually do one of four things:
- Contrast — "The best day and the worst day happened in the same week."
- Confession — "I quit something I was good at."
- Numbers — "Three cities, two jobs, one cat."
- Setup and payoff — show the final shot of the year first, then rewind.
Keep the hook under nine words on screen. Anything longer gets skipped while it loads.
Gather raw material into one folder
You cannot build a film out of a camera roll you have never sorted. Spend twenty minutes consolidating, not editing.
Asset checklist
- Phone clips, even shaky vertical ones — they often carry the most emotion.
- Photos, screenshots, ticket stubs, receipts, chat screenshots (blur names).
- Voice notes and short audio snippets of your own voice describing a moment.
- Screen recordings: playlists, maps, workout stats, travel routes.
- One or two lines you actually wrote at the time — journal fragments make excellent captions.
Name files by beat rather than by date-stamp. You want to reach for "beat-03-move" while editing, not scroll through IMG_4821 until you lose the thread of the story.
What to do if you barely filmed anything
Most people did not film their year. That is fine; a recap is a reconstruction, not a documentary. You have four reliable options:
- Turn strong stills into moving shots with image-to-video.
- Rebuild a memory as a stylized scene: the kitchen at 2 a.m., the empty platform, the desk with the resignation letter on it.
- Use detail shots — hands, shoes, a cup, a door — instead of faces.
- Lean on typography and sound. A text-led recap with three cinematic inserts outperforms twenty mediocre clips.
Stylized reconstruction is honest as long as it feels intentional. Grain, slow motion, and a consistent palette read as "memory," not as fake footage.
Turn your beats into a shot list of prompts
Here is where most people get stuck: they open a generator, type "year in review cinematic," and get something generic. Vague prompts produce vague video. A shot list fixes that.
Describe motion, light, and camera
Weak: "Travel scene, cinematic." Better: "Handheld close-up of a train window at dawn, condensation on glass, pale blue light, camera slowly racks focus from reflection to passing fields, 35mm grain."
The second prompt contains four controllable variables:
- Motion — what moves, and how the camera behaves (push in, drift, pan, static tripod).
- Light — time of day, direction, color temperature.
- Lens and framing — close-up, wide, macro, over-the-shoulder.
- Texture — grain, haze, halation, film-stock feel.
Write one prompt per beat, not one prompt for the whole video. Five to eight shots is plenty for 45 seconds.
Keep a consistent look
Nothing breaks the illusion faster than five shots that look like five different films. Create a short "look block" — three or four phrases — and paste it at the end of every prompt:
vertical 9:16, soft window light, muted teal and warm amber palette, 35mm grain, shallow depth of field
Consistency of palette, grain, and lens does more for perceived quality than resolution does. It also makes transitions feel invisible, which means you can cut harder without the viewer noticing the seams.
Generate and iterate inside one workspace
With the shot list written, generation becomes a fast loop instead of a creative block. In the AI video generator, start from text for reconstructed moments and from image-to-video for real photos you want to animate. Browse the prompt library when a beat is hard to describe; the phrasing patterns there are easy to adapt to your own look block.
A practical rhythm:
- Generate two variations per shot. Not ten. Two.
- Watch each at full screen on a phone, not on your monitor. If it reads at phone size, it reads anywhere.
- Keep the take that communicates the beat in under two seconds. Discard beautiful shots that need explaining.
- Regenerate only the shots that fail on motion or framing — leave the rest alone.
If you would rather start from a structure, video templates can supply pacing and typography so you only swap in your own footage and lines.
Edit for retention, not for perfection
Editing a recap is mostly subtraction. The finished video should feel slightly too fast when you preview it; that is the correct speed for short-form.
Cut every 1.5 to 2 seconds
Match cuts to the pulse of the music for the first ten seconds, then let a single shot breathe for three or four seconds at the emotional peak. That contrast is what makes a slow shot feel intentional instead of lazy.
Captions and safe zones
Assume the video is watched on mute, in a queue, at 30% brightness. Put the essential line of each beat on screen, keep text inside the middle 80% of the frame, and leave the bottom 15% clear for interface elements. Sans-serif, high contrast, no more than two lines per card.
Sound design is half the film
Three layers do most of the work: a track with a clear emotional turn, one ambient bed (rain, crowd, train, room tone), and two or three small foley hits on your hardest cuts. If you recorded voice notes during the year, drop two of them in. Real audio makes a reconstruction feel true.
Export settings and upload checklist
Export settings are boring until your footage turns to mush after upload. Give the platform a clean master.
- Resolution and frame rate: 1080x1920 at 30 fps unless your source is 60 fps and motion-heavy. Match frame rate across all clips.
- Bitrate: aim high — a 15–20 Mbps H.264 export holds detail through recompression far better than a small file.
- Length: 30–50 seconds is the sweet spot. If yours runs long, cut a beat instead of speeding everything up.
- Cover frame: choose a frame with a face or a strong shape, and place title text where the interface will not cover it.
- Caption: one sentence of context plus the emotional hook. Skip the hashtag wall; three relevant tags beat fifteen.
Before publishing, watch the final export once on a phone with the sound off, then once with headphones. If both pass, upload.
Mistakes that make a recap feel amateur
- Chronological inventory. A calendar is not a story. Group beats by theme, not by month.
- One-note energy. If every shot is a sunset or a party, nothing stands out. Contrast a quiet frame against a loud one.
- Mismatched visuals. Mixed grain, mixed color temperature, mixed aspect ratios. Lock the look block.
- Text overload. If the viewer is reading a paragraph, they are not watching.
- Overlong intro. Six seconds of logo and greeting is six seconds of audience lost.
- No ending. A recap without a final turn leaves the viewer with nothing to feel.
- Ignoring the first frame. The thumbnail is a decision point; treat it as part of the edit.
A two-evening production plan
Evening one — decisions (90 minutes). Write the hook and the three to five beats. Sort assets into one folder. Write one prompt per beat, each ending with the same look block. Generate two takes per shot and pick the winners before you stop for the night.
Evening two — assembly (two to three hours). Lay the audio track first, then place shots against the beat map. Add captions, layer ambience and two foley hits, export, and review on a phone. Fix only what is visibly broken; do not restart the edit at midnight.
The second recap you make will take half the time, because your look block and prompt patterns already exist.
FAQ
How long should a year-in-review video be? 30 to 50 seconds. Long enough for three to five beats and a turn, short enough that completion rate stays high.
Do I need footage from the actual year? No. Stills, screen recordings, and reconstructed shots work as long as palette and grain are consistent enough to read as one memory.
How many AI-generated shots is too many? If more than half the video is generated, anchor it with at least two real artifacts — a photo, a voice note, a screenshot — so the recap still feels personal.
Can I make a recap without showing my face? Yes. Use hands, objects, environments, and text. Faceless recaps often perform better because viewers project themselves onto the shots.
What if my year was quiet? Quiet years make strong recaps when you narrow the frame: one skill, one room, one relationship, one habit. Small and specific beats big and vague.
Should the music be trending? Use a track that carries an emotional shift, trending or not. A slightly less popular song that matches your turn will outperform a hit that fights your edit.
Make the recap only you could make
Your year does not need to look expensive. It needs to look deliberate: a hook that creates a question, five beats that answer it, a consistent visual world, and an ending that lands. That is a directorial job, not a technical one — and it is exactly the work Orelon is built for, turning written beats into cinematic shots you can assemble in a single evening.
Start with the video creator, borrow a look block from the prompt library, and keep the blog open for pacing ideas. Then write your first line, generate your first shot, and publish the recap while the feeling is still fresh.

