How to make a game trailer: show what the player actually does
Show the action, its consequence and the reason to care. A practical trailer workflow for small indie teams, with an example and a new-viewer check.
Here is how to make a game trailer for your Steam page: choose the player action you need to explain, capture a clear example of it, and build the edit around what happens because of that action. Then show the cut to someone who does not already know your game. Ask what they understood before you explain it yourself.
A trailer can look polished and still leave me wondering what I would actually do. The useful question is whether a prospective player can follow the game you are showing, including the part that makes it interesting. That gives you something concrete to work on before elaborate transitions or a cinematic introduction.
This guide is for solo developers and small indie teams making a gameplay-led store trailer. A story teaser or an announcement for an established audience may need a different approach. None of the steps below promises wishlists or sales.
In this guide: Choose the target audience and creative direction · Plan the gameplay footage before collecting impressive shots · A step by step process for the trailer structure · Capture gameplay footage people can read · Choose video editing software you can maintain · Trailer editing: build a rough cut around understanding · Give audio the same attention as the picture · Test the new trailer with unfamiliar viewers · Check the final version and its Steam presentation
Choose the target audience and creative direction
Before opening your video editor, finish this sentence: “After watching, someone should understand that they can…”
Use a player action. Move light to reveal a path. Redirect a train before it reaches a broken bridge. Bargain with a customer who remembers a previous deal. “Explore a beautiful world” may describe the mood, but it leaves the interaction vague.
Your creative direction is the experience you want the trailer to communicate: a tense decision, a comic interaction, a satisfying solution or another specific part of play. Choose the target audience before deciding how much explanation that experience needs. Keep the intended viewer in mind. Someone finding the game for the first time needs enough context to interpret an impressive moment. Existing players watching an update trailer may already know the basic controls and want to see what changed. Decide which viewer this cut serves.
Valve recommends a primarily gameplay first trailer, showing the game from the player's perspective. It also points out that a helpful HUD can make the game easier to understand and that people may watch without sound. These are useful priorities for a Steam store trailer; they do not prescribe the entire creative treatment.
The wider page has its own job. Use the Steam store page guide for the relationship between the trailer, screenshots, description and other store information. Here I am focusing on making the video itself understandable.
Plan the gameplay footage before collecting impressive shots
Trailer editor Derek Lieu starts an outline with what the player does. For a gameplay-led trailer, this is a useful way to decide what belongs before selecting scenery, enemies or effects.
Write a small capture list:
| What the player needs to understand | Footage to capture | What to keep visible |
|---|---|---|
| The basic action | An uncomplicated use of the main mechanic | The player, the relevant object and the result |
| A meaningful choice | The same situation with another possible response | Enough context to distinguish the choices |
| A consequence | Success, failure or a changed game state | The connection between action and outcome |
| An interesting complication | A familiar action under a new constraint | The rule the viewer already learned |
This is a planning aid, not a requirement to put every row into every game trailer. A narrative game might need a character decision and its consequence. A tactics game might need a readable turn. Pick the evidence that fits the game you actually have.
Mark anything that still needs capturing. A promising clip with a bug, an obscured interaction or an unfinished feature is not automatically usable footage. Recapture a clearer example when you can. Avoid editing separate moments together in a way that implies an interaction the current build cannot perform.
A step by step process for the trailer structure
The following game, Lantern Ferry, is fictional. It is an example for this guide, not a project I have tested. Imagine a top-down puzzle game in which moving a lantern reveals routes across a flooded village.
| Sequence | What happens on screen | What the viewer should learn |
|---|---|---|
| Establish the action | A character moves a lantern beside a ferry; a route appears across the water | Moving light changes where the player can go |
| Complete the action | The player follows the visible route to a dock | The route is usable, with a clear destination |
| Show the choice | Moving another lantern reveals a different route while the first disappears | The light creates a navigation decision |
| Add a complication | A moving obstruction interrupts a route already explained | A familiar rule becomes a new puzzle |
| Close the trailer | The game title and a real next step appear | The interested viewer knows where to go |
There is no real store page for this fictional game. For your own trailer, the destination must exist and match what you are offering. “Play the demo” is useful only when the demo is actually available. If the game is coming soon, make that status clear.
The sequence connects action and consequence. A montage of lanterns, splashing water and village scenery might communicate atmosphere, but it would not necessarily explain the puzzle. That is a distinction to check with viewers, rather than an improvement to claim without testing.
Capture gameplay footage people can read
A dramatic moment can become an unclear shot when several things compete for attention. Keep the relevant action visible long enough to connect it with its result. Cut away after the important information is legible, rather than simply when the music changes.
Lieu's game capture guide considers clarity, composition, staging and execution. I would use those as questions while reviewing raw footage: where should I look, what happens, and can I tell why it matters?
For the fictional lantern example, a crowded night scene with overlapping effects may hide the path change. A quieter scene could teach the rule first. You can then show the richer scene once the viewer has a way to interpret it.
Keep the interface that explains the action
Keep useful interface information. A health bar, turn indicator or inventory change may explain a consequence that would otherwise be invisible. Remove accidental recording overlays and debug information. There is no general reason to strip out every HUD element just because the frame looks cleaner without it.
Choose video editing software you can maintain
Use an editor in which you can trim clips, arrange footage, adjust audio levels, add readable text and export a clean video. Try those tasks with your own gameplay footage before committing to a new workflow. A familiar editing tool can be enough; an expensive package does not decide whether the action is understandable.
Keep the capture files, narration, music and sound effects organised separately in the project. Give useful clips descriptive names, such as the mechanic and the result they show, so you can find them again. Save a copy of the rough cut before making a substantial revision. When a viewer flags a confusing moment, you can compare the change with the previous version.
This guide does not rank software or teach a particular editing interface. The point is to choose tools that let you concentrate on the game rather than rebuilding your process for each new trailer.
Trailer editing: build a rough cut around understanding
Start with a simple arrangement of your selected clips. Watch the sequence before polishing it. Does each shot introduce something useful, explain the previous action or add a complication the viewer can follow?
Set the pacing around what the viewer needs to see
Remove repeated evidence unless it adds a real distinction. Showing several enemies may communicate variety; showing the same attack from several angles may only repeat information. You do not need to demonstrate the complete feature list to explain why this game might interest someone.
Text can supply context the footage cannot carry alone. In Lieu's tell, show, repeat approach, a title card introduces an idea and the following gameplay demonstrates it. Keep that relationship honest: if a card promises a choice, show the choice.
For our fictional example, “Move the light. Reveal your route.” could introduce the action. Putting the line over the crucial path change might instead make the viewer choose between reading and watching. Try the placement at a realistic viewing size and check what people miss.
How long should a game trailer be?
Long enough to explain its particular idea without repeating itself. That is an editing decision, not a universal duration formula.
Kert Gartner's trailer-making advice favours a focused promotional cut. Lieu's minimal Steam trailer guide allows a longer gameplay sequence for first-time developers whose visitors need to inspect the game. They are discussing different contexts, so combining their preferred lengths into one rule would lose the useful part of the advice.
If a section adds no new understanding, try removing it. If the action becomes incomprehensible after a cut, restore the context it needs. A fast edit is not automatically an engaging one.
Give audio the same attention as the picture
From my experience receiving games at Crit Pick, a voiceover needs to sound good. Thin, tinny audio puts me off. That is my editorial reaction, not a measured rule about how every player responds.
If you use narration, read the script aloud before recording the final performance. A sentence can read well on the page and still feel awkward to say. Rewrite the difficult turn of phrase, record another take, and listen to how the line fits the footage. Repeatedly trying to perform a sentence that does not flow can waste the recording session.
A voice actor is an option when narration is important to the trailer. I would audition the actual lines and agree on the intended use, deliverables and revision scope before committing. A marketplace listing alone does not establish the quality, final cost or permissions of a recording. You can also choose a gameplay-led trailer without narration if speech adds little to the explanation.
Balance the voiceover, music and sound effects
Keep meaningful game sounds audible. Lieu's sound-effects discussion explains how effects can communicate the feel of an interaction. Listen for music covering a useful impact, a quiet spoken line or a clue the viewer needs.
Check the visuals and captions without sound
Then watch without sound. Important spoken information needs a readable alternative, and the basic gameplay should still make sense. Captions must be legible and timed to the speech; avoid placing them over the action they explain. A muted viewing check is useful, but it is not a complete accessibility assessment.
Test the new trailer with unfamiliar viewers
Before showing the cut, privately write down what you want someone to understand. Let a person unfamiliar with the project watch without a spoken introduction. Where possible, choose people interested in the kind of game you are making.
Ask open questions:
- What would you do in this game?
- What changed because of the player's action?
- What seemed interesting or different?
- Where were you unsure what was happening?
Turn a confusing moment into a specific revision
Record their words and the confusing moment. If you need to explain the main mechanic afterwards, that is useful information about this version of the trailer. It does not prove the game is unappealing.
| Intended meaning | What the viewer said | Possible revision |
|---|---|---|
| Moving the lantern changes the route | Record the actual response here | Show the route before and after the move in one readable shot |
| The route disappears when the light moves | Record the actual response here | Let the consequence remain visible before cutting |
| The game is playable now | Record the actual response here | Check the closing line and destination against actual availability |
This is a proposed qualitative check, not a validated scoring system. Keep sound-on and muted observations separate, and note viewing order: someone watching for a second time already knows more. Fresh viewers can help check a revised cut without that learning effect. None of this measures market demand or predicts sales.
Check the final version and its Steam presentation
Review the exported video, not only the editing timeline
Watch the exported file all the way through. Look for stray frames, broken text, debug overlays, incorrect availability, unreadable captions and credits you forgot to update. Listen for abrupt edits, clipping and dialogue masked by music. Lieu's quality-control checklist is a useful practical companion.
Check Valve's current upload instructions before exporting the final delivery version. Steam creates a short microtrailer from the first visible video; its current documentation describes automatic sampling without a custom editing option. Inspect the generated result rather than assuming your favourite shot will appear. After an upload, check the processed trailer as well as the local file.
You do not have to solve the entire marketing campaign in this edit. Make the main action understandable, give the interesting part room to land, and provide a truthful next step. Your next useful task is to pick the gameplay sequence that can demonstrate that action clearly.