Game studios produce a video genre most film teams never touch: footage captured from a build that changes under the editor's feet, cut into announcement trailers, gameplay reveals, launch spots, and per-platform store cutdowns - each passing through internal review, publisher sign-off, and platform certification before anyone outside the studio sees a frame. The review loop is the actual production method here: trailer capture professionals describe a workflow that runs WIP build, playthrough notes, script approval by the publisher, capture, edit, client notes, recapture, then picture lock - meaning the review rounds happen on footage that costs real studio time to produce again. This guide maps the loop, the reviewer lanes, and the platform gates, and shows where a review tool earns its seat.
The game-video pipeline is a capture pipeline
Unlike film, the footage source is the game itself. Engines ship dedicated capture tooling for this: Unreal Engine's Movie Render Queue - documented by Epic as the engine's "image sequence and movie rendering solution, built for high-quality rendered images" - and Unity's Recorder package, which Unity's docs describe as capturing "gameplay or a cinematic" and saving it as MP4 during play mode. Trailer teams also capture through debug cameras and freecams inside WIP builds; industry coverage of the role (a 2025 Aftermath interview with a professional "game capture director") describes the job as getting the exact footage a trailer script needs, shot by shot, from builds that are still changing. The practical consequence for review: every capture pass has a cost, and imprecise feedback directly converts into recapture sessions.
The review rounds, mapped
The capture-director workflow that industry interviews describe maps cleanly onto a version ladder, and it is worth naming each round because each one has a different reviewer judging a different thing:
| Round | What is reviewed | Who decides |
|---|---|---|
| Script / concept pick | Trailer scripts or treatment options; beats, reveals, tone | Publisher or studio marketing - the client picks the script before capture starts |
| Capture pass review | The raw captured takes: did the freecam pass nail the moment | Capture director + editor; unusable takes get flagged frame-precisely so recapture is targeted |
| Cut v1 → v2 | Pacing, music sync, reveal timing on the edited cut | Creative director, producer; publisher watches at v1 or v2 |
| Lock | Final frame check - supers, logo timings, mnemonic slots | Explicit sign-off before platform packaging starts |
Two properties of this loop matter when you pick tooling. First, notes land mid-timeline constantly - "hold the reveal two beats longer" is a frame-count note, which is why frame-accurate review is not a luxury feature in this genre. Second, the most expensive failure is a vague note on a capture pass: "the dodge feels off somewhere around the second combat bit" sends a capture team back into a build for an afternoon; a timestamped comment pinning the exact frames sends them back for five minutes.
One master, many platform cuts
Every trailer spawns cutdowns, and platforms publish real specs for them. The two publicly documented examples (Sony and Nintendo keep their portals gated):
| Target | Documented requirements (as of Nov 2026) | Review implication |
|---|---|---|
| Steam store page | Trailers up to 1080p H.264+AAC at 30/60 fps, 16:9 preferred, 5,000+ Kbps recommended; screenshots at 1920×1080 minimum that "must show actual gameplay" | The gameplay-screenshot rule means capture quality review extends to stills, not just cuts |
| Xbox Partner Center | 1920×1080, MOV (ProRes) or MP4 (H.264 50 Mbps), max 15 trailers per product, under 30 minutes, under 10 GB, WebVTT captions, required intro and end mnemonics; trailers must pass certification before publishing | Mnemonic head/tail frames, caption files, and the certification pass all become checklist items tied to a specific version |
| Social cutdowns (9:16) | Not platform-certified - owned by the studio's own brand rules | Vertical cuts review like any social edit; the vertical review workflow applies as-is |
This is the version-per-target problem: an announcement trailer, a gameplay trailer, a launch trailer, and their 15/30/60-second cutdowns and verticals are all versions of a campaign, not loose files. Studios that manage them as a version stack keep review history per cut; studios that manage them as folders named "FINAL_v3_REAL" are the reason naming conventions exist.
The security angle: everything is unannounced
Game video review has a threat model film mostly avoids: every cut contains unannounced content - characters, maps, story beats, release dates. A leaked trailer is a marketing plan invalidated. Publisher and platform reviewers are external parties who legitimately need to watch cuts, which makes the review-link controls the security boundary: password-protected links, expiry dates, watermarks, and downloads off are the four controls that matter, and the review-link security guide covers the threat model behind each. Studios sharing raw capture passes internally have the same exposure - a WIP build's footage leaks dates and features no trailer ever would.
Where a review tool fits - and where it does not
The honest boundary: capture happens in engine tools (Movie Render Queue, Unity Recorder, debug cameras) and platform compliance happens in the partner portals and their certification passes. A review tool is not for either of those jobs. It owns the human loop between them:
- Capture pass review - timestamped, frame-precise flags on raw takes so recapture is targeted instead of exploratory.
- Trailer cut rounds - versions stacked (announcement → gameplay → launch, v1 → v2), comments carrying across rounds, explicit approval at lock.
- External review without seats - publishers, platform partners, and PR agencies watch and comment on links without accounts or licenses; no-account review links exist precisely for this.
- Security controls per link - password, expiry, watermark, downloads off - on every unannounced cut.
What a review tool will not do: render in-engine footage, generate mnemonics, or submit to Partner Center. Those stay with the engine and the portals. Teams shopping for the review layer can compare candidates on the reviewer-experience factors in how to choose video review software; teams specifically comparing against Adobe's platform can start at the Frame.io alternatives comparison.
The seat math for studio rosters
Game teams are seat-dense on paper and thin on actual editors: capture directors, capture techs, editors, producers, creative directors, marketing, QA, plus publisher reviewers. Per-seat tools bill the roster; tools that bill only internal members while reviewers stay free (Frooty's model - our pricing, disclosed as always, and the pattern the unlimited-reviewers comparison maps across the category) keep the external publisher side free. Run the math on your actual roster: a 12-person internal team with 6 external reviewers is a very different invoice depending on which side the seats land on.
FAQ
How do game studios review trailer cuts before release?
Through the same round ladder film uses, adapted to capture: script or treatment picked by the publisher, capture passes reviewed take by take, edited cuts through v1/v2 rounds with creative director and publisher notes, then an explicit lock before platform packaging. Industry interviews with trailer capture teams describe exactly this loop - client notes and recapture between every stage.
What specs do Steam and Xbox store trailers need?
Publicly documented as of November 2026: Steam accepts H.264+AAC up to 1080p at 30/60 fps with 5,000+ Kbps recommended, and requires screenshots that show actual gameplay. Xbox Partner Center requires 1920×1080 trailers (ProRes MOV or H.264 MP4 at 50 Mbps), max 15 per product, under 30 minutes and 10 GB, with WebVTT captions and branded intro/end mnemonics, passing certification before publishing.
How do you keep unannounced game footage secure during review?
Share review links, not files, and use the four controls: password protection, expiry dates, watermarks, and downloads disabled - applied to internal capture passes as well as publisher-facing cuts. Every unannounced frame in a review link is leak exposure until the trailer goes public.
What is a game capture director?
A specialized role that captures in-engine footage for trailers - working from WIP builds with debug cameras and freecams, executing a shot list from the approved script, and iterating with the editor until picture lock. Dedicated capture roles and toolchains are a documented part of the game-trailer industry, though not every studio uses the same setup.
Do publishers review trailers before they go out?
Typically yes - the capture-director workflow interviews describe the publisher (or client) picking the trailer script before capture starts and returning notes on cuts afterward. Platform partners additionally review marketing assets during certification for store submission, which is why the lock round happens before packaging.