Game cinematics and cutscenes do a lot of heavy lifting. They introduce characters, deliver story beats, and set the tone for the next level. Done well, they feel like a reward. Done poorly, they pull players out of the experience or feel like a budget compromise.
You do not need a Hollywood pipeline to ship effective cinematics. With a clear process from idea to final frame, you can create cutscenes that support your narrative and stay within scope. This guide walks you through that process from storyboard to delivery, whether you are working in-engine or with pre-rendered video.
What counts as a game cinematic
For this article, a cinematic is any non-interactive (or lightly interactive) sequence that advances story or mood. That includes:
- In-engine cutscenes – Real-time in your game engine (Unity, Unreal, Godot), with your game’s assets and lighting.
- Pre-rendered video – Exported video files (e.g. MP4) played back at key moments, often higher fidelity but fixed at export time.
- Hybrid – In-engine with pre-rendered inserts (e.g. key story moments as video, rest in-engine).
Each approach has trade-offs. In-engine keeps file size down, supports multiple resolutions and aspect ratios, and can react to player progress or choices. Pre-rendered gives you full control over every pixel and can hide engine limitations. Your choice depends on team size, target platforms, and how much you want to lean on narrative.
Step 1 – Define the goal of the sequence
Before drawing a single frame, answer:
- What must the player know or feel after this sequence? (e.g. “Understand that the villain has the artifact.”)
- Where does it sit in the game? (Opening, act break, before boss, ending.)
- What is the tone? (Tension, relief, mystery, triumph.)
Write a short brief (a few sentences). Share it with anyone involved in writing, art, or implementation. That brief is the yardstick for every later decision: if a shot or line does not serve that goal, cut it or simplify it.
Step 2 – Write a simple beat outline
Turn the goal into a short list of story beats. One line per beat is enough.
Example for a mid-game reveal:
- Player reaches the vault.
- Empty pedestal – artifact is gone.
- Villain appears on screen (hologram or flashback).
- Villain states they have the artifact and taunts the player.
- Screen goes dark; next level name or objective appears.
This is not a script yet. It is the order of events. It helps you see pacing and spot redundant beats. Once the beats feel right, you can add dialogue and action details.
Step 3 – Storyboard the sequence
Storyboards do not need to be pretty. They need to show framing, action, and cuts.
For each beat, draw (or sketch) key frames. Indicate:
- Framing – Wide, medium, close-up, over-shoulder.
- Subject – Who or what is in frame.
- Action – What happens in that moment.
- Cut – Where you transition to the next shot.
You can do this on paper, in a tool like Storyboarder, or in a doc with stick figures. The point is to lock the flow of the sequence before anyone spends time in the engine or in an animatic.
Pro tip: Limit the number of shots. Fewer, stronger shots read better and are cheaper to produce. If you can convey the same beat in one shot instead of three, do it.
Step 4 – Choose in-engine vs pre-rendered
Use this as a rule of thumb:
- In-engine – Default for most indie and mid-size projects. Use your engine’s timeline (Unity Timeline, Unreal Sequencer, Godot AnimationPlayer or custom). Keeps iteration fast and file size low. Best when your game already looks good in real time.
- Pre-rendered – Consider when you need effects or fidelity the engine cannot deliver in real time, or when the sequence is short and critical (e.g. opening or ending). Be aware of resolution and aspect-ratio choices (e.g. ultrawide, different quality tiers).
If you go pre-rendered, export at a high enough resolution and test playback on your minimum-spec machine. Large video files can cause long loads or stutter if not streamed carefully.
Step 5 – Block the sequence in the engine
With storyboards in hand, block the sequence in your engine.
- Place cameras for each shot. Match your storyboard framing as closely as possible.
- Place characters and props. Do not worry about animation yet; use T-poses or simple holds.
- Set shot length. Use your engine’s timeline or cutscene system to set in and out points for each camera.
Play through the blocked version. Check that the story beats read clearly and that cuts feel right. Adjust camera positions and timings until the flow matches your intent. This is the stage where you fix pacing and framing cheaply.
Step 6 – Add performance and animation
Once blocking is approved, add the real performance.
- Dialogue – Record or source voice lines. Sync lip-sync or subtitle timing to the timeline.
- Character animation – Use keyframe animation, motion capture, or pre-made clips. Keep animations consistent with your game’s style.
- Camera animation – Add slow pushes, pans, or handheld-style movement if it helps the mood. Avoid unnecessary motion that distracts from the story.
If you use pre-rendered, this is the stage where you export high-quality frames or video from the same blocked layout (often from a separate “cinematic” level or scene).
Step 7 – Add audio and polish
- Music – Bring in the track that matches the tone. Fade in/out or cut to hit story beats.
- Sound design – Foley, impacts, and ambience. Even simple layers make a big difference.
- Mix – Balance dialogue, music, and effects so dialogue is clear and the mix feels intentional.
For in-engine cutscenes, ensure that when the sequence ends, the game’s normal audio state resumes correctly (no stuck music or muted SFX).
Step 8 – Integrate into the game
- Trigger – How does the cinematic start? (Door open, trigger volume, scripted moment.)
- Skip – Decide whether the player can skip (often yes, after first view or after a short delay).
- Transition – How do you hand control back to the player? Fade, cut to gameplay camera, or a short “take control” moment.
Test the transition on different hardware and with different settings (e.g. resolution, windowed vs fullscreen) to avoid black frames or desync.
Common mistakes to avoid
- Too long – If the sequence drags, trim. Respect the player’s time.
- Too many cuts – Rapid cutting can feel restless. Let important moments breathe.
- Ignoring the brief – If a shot does not support the goal of the sequence, remove it.
- No skip or long unskippable – Many players will want to skip on repeat playthroughs. Plan for it.
- Audio bugs – Stuck or missing audio after a cinematic is common. Always test “play cinematic then return to gameplay” as one flow.
When to outsource
If your team has no animators or narrative designers, you can outsource:
- Storyboard and beat design – A narrative designer or storyboard artist can own the outline and boards.
- Animation and rigging – Freelance animators or studios can deliver clips you plug into the timeline.
- Full pre-rendered cinematics – External studios can take your boards and produce video; you integrate the files.
Keep the brief and beat outline in-house so the vision stays clear; outsource execution where it makes sense.
Recap and next steps
Game cinematics do not require a film-sized team. Start with a clear goal and a beat outline, storyboard the key shots, then block in-engine (or plan pre-rendered) and add performance and audio. Keep sequences tight and test the full loop from trigger to return to gameplay.
For more on structuring narrative and dialogue in games, see our guides on game narrative design and creating game trailers. If you are implementing in Unity, the Unity Timeline documentation is a solid reference for in-engine cutscenes.
Found this useful? Bookmark it for your next narrative-heavy project and share it with your team when you plan your next cinematic.