
evaluate hardware, software and web applications for playing a finished video, choose a codec, container and bitrate suited to each delivery, and export versions of your trailer for a game store, a vertical social format and a high-quality master, following official platform specifications.
Instruction
Finishing is a design decision. A trailer that looks right in your editor can still fail where people watch it: the file will not play, the sound drifts, the text is unreadable on a phone, or the upload is rejected. Professional teams check playback on many devices and export several versions, each made for one outlet. In this lesson you evaluate playback, choose codecs and bitrates on purpose, and export three versions: a 16:9 store and web trailer, a vertical social cut and a high-quality master to keep.
Evaluating where video plays (MM.VID.9). Every playback source is a mix of hardware (a computer, phone, tablet or TV, some with a chip that decodes certain codecs), software (the operating system’s player, a media player, your editor) and web applications (a browser playing a video on a page, or a platform that re-encodes uploads). MDN’s web video codec guide shows why this matters. H.264 (AVC) plays in every major browser. HEVC support depends on the device: Chrome uses it where the hardware supports it on Windows, and Firefox on Windows (from version 134) uses hardware decoding or a paid extension. AV1 plays in Safari only on devices with a hardware decoder, such as M3 MacBooks and later, the iPhone 15 Pro and the iPhone 16 and later. Platforms re-process uploads: Steam says it can transcode many formats and filters audio down to regular stereo. So test each export in at least three places, such as two browsers on the computer, the computer’s own player and a phone, and record whether it plays, stays in sync, keeps text readable at phone size and works muted for the first ten seconds.
Codecs, containers and compression (MM.VID.10). A codec compresses video for storage and decompresses it to play; a container (MP4, MOV, MKV, WebM) holds the video stream, audio stream and timing together. MDN explains that most video codecs are lossy, and the more compression you achieve, the more detail is lost. Fast motion and fine detail, which gameplay has plenty of, are the hardest to compress, and artifacts such as blocks, posterized gradients and ringing round sharp edges appear first. The four codecs in your export menus compare like this, according to MDN: H.264 is the most broadly compatible but is patented; HEVC (H.265) can in theory produce files about half the size of H.264 at comparable quality, but it is patented and unevenly supported; VP9 is open and royalty-free, with quality comparable to HEVC at similar bitrates; AV1 is royalty-free and can compress up to 50% better than H.264. Bitrate is the data per second, and file size = bitrate × duration ÷ 8. A 75-second trailer at YouTube’s recommended 8 Mbps for 1080p at standard frame rates, plus 384 kbps stereo audio, is (8 + 0.384) × 75 ÷ 8 = 78.6 MB. Uncompressed 1080p video needs at least 1.5 Gbps, MDN notes, so the same 75 seconds would be about 14.06 GB, roughly 179 times larger.
Exporting for different outlets (MM.VID.11). Match each export to an official spec. Store trailer: Steamworks asks for the highest resolution you have up to 1920 × 1080, 30/29.97 or 60/59.94 fps, a high bitrate (5,000+ kbps), an .mov, .wmv or .mp4 file, H.264 video with AAC audio preferred, 16:9 preferred (4:3 accepted) and a 44 or 48 kHz audio sample rate; Valve’s own encoder preset uses H.264 at 20 Mbps with AAC stereo at 192 kbps, which makes a 75-second file about 189.3 MB. Web upload: YouTube recommends MP4 with the moov atom at the front (Fast Start), H.264 High Profile, progressive scan, AAC-LC or Opus audio at 48 kHz, and the frame rate you recorded. For your own web page, MDN suggests WebM with AV1 and Opus plus an MP4 with H.264 and AAC as a fallback. Vertical social cut: YouTube’s player adapts to vertical video, YouTube describes Shorts as short-form videos up to 3 minutes long, and Shorts are uploaded at up to 1080p, so a 1080 × 1920 cut of about 30 seconds at 8 Mbps is about 31.44 MB. Shotcut’s Reframe (in Export > Video, version 24.09 and later) crops a 16:9 project to 9:16; Kdenlive’s render Aspect Ratio option crops too, but reframe each shot so the action and text stay in the tall frame. Master: keep the highest-quality copy. Shotcut’s FAQ suggests DNxHR HQ or ProRes 422 for a file going to another tool, and Kdenlive lists Lossless/HQ presets. Keep the project file and the source folder with it, backed up.
Sharing, permission and credits. You do not create any account for this course. Posting a trailer anywhere happens only with a parent’s permission, on an account a parent already controls. YouTube notes that the default privacy for creators aged 13-17 is private. Credit every sound or asset you did not make, and use only music you made or that is CC0 or CC BY. Steam requires a trailer before a game can be released there; you prepare yours to that spec as practice, without uploading it.
📖 Read for this lesson
The reading opens over the lesson; close it to come back to exactly where you were. The checks below draw on it.
Build: Three Exports and a Playback Test
Question. Can you export your trailer in three versions matched to the Steam store spec, a vertical social format and a high-quality master, predict each file’s size from its bitrate, and prove from testing where each one plays well?
Materials
- A computer with Shotcut or Kdenlive and your finished trailer project from Lesson 5.2
- At least two web browsers on the computer, the computer’s built-in video player, and a phone or tablet if you have one
- A USB drive or a parent-approved folder for the master and its backup
- This lesson’s reading (spec table for each outlet, export recipes for both editors, a file-size calculator and the playback test log)
- A calculator
- Do not create an account on any site, and upload nothing without a parent’s permission; this lab tests files on your own devices.
- Before you copy a file to a phone, ask a parent; delete test copies from shared devices afterwards.
- Keep headphone volume moderate and take a screen break at least every 30 minutes.
Procedure
- Fill in the spec table in the reading for the three outlets (store trailer, vertical social cut, master): resolution, frame rate, container, video and audio codec, bitrate and where each spec comes from.
- Predict each file’s size with size = (video Mbps + audio Mbps) × seconds ÷ 8, using your trailer’s real length; for the store trailer use 20 Mbps video and 0.192 Mbps audio.
- Export the store trailer: 1920 × 1080, your recorded frame rate (30 or 60), MP4, H.264 with AAC, a bitrate of at least 5,000 kbps (Shotcut: Advanced mode, Codec and rate control; Kdenlive: MP4-H264/AAC with Custom Quality).
- Make the vertical social cut: duplicate the project, set a 1080 × 1920 vertical video mode or use Reframe (Shotcut) or the render Aspect Ratio option (Kdenlive), shorten it to about 20-30 seconds, move or enlarge text so it fits the tall frame, and export as MP4 with H.264 and AAC.
- Export the master at the highest quality your editor offers (Shotcut: ProRes 422 or DNxHR HQ, or H.264 at a very high quality; Kdenlive: a Lossless/HQ preset), then copy the master, project file and source folder to your backup drive.
- Compare predicted and actual file sizes, then play each export in at least three places (two browsers, the computer’s player, a phone or tablet if possible), and fill in the playback test log: plays, audio in sync, text readable, first ten seconds work muted.
- Fix the worst problem you found, export again, and retest that version.
Data
| Version | Resolution and fps | Container and codecs | Bitrate | Predicted size (MB) | Actual size (MB) | Plays in (browser 1 / browser 2 / player / phone) |
|---|---|---|---|---|---|---|
| Store trailer | 1920 × 1080 | MP4, H.264 + AAC | 20 + 0.192 Mbps | |||
| Vertical cut | 1080 × 1920 | MP4, H.264 + AAC | ||||
| Master |
Check: a 75-second store trailer at 20 + 0.192 Mbps is (20.192 × 75) ÷ 8 = 189.3 MB.
Analysis
- Which version was furthest from your predicted size, and what in your trailer (motion, detail, rate-control setting) explains the difference?
- Which playback source caused a problem, and was it the hardware, the software or the web application? Use the codec information from MDN to explain it.
- Why does each outlet get its own export instead of one file for all three? Use one specific requirement from the Steamworks or YouTube pages in your answer.
If you cannot do this build in person: If your computer is slow to export, export the store trailer and the vertical cut at 1280 × 720 (a common resolution Steam names) and keep the project file as your master instead of a large master file. If you have only one device, test in two browsers and the built-in player, and use the browser’s window size to check text readability at phone width. If the editor will not export one of the codecs, record that as a playback-source finding and use H.264 with AAC.
Formative check
Work through these before moving on. They are not graded — they tell you whether the standard below has landed yet.
Missouri standard: MM.VID.10
A 75-second trailer at 8 Mbps video plus 0.384 Mbps audio is (8.384 × 75) ÷ 8 = MB; at Valve’s 20 Mbps plus 0.192 Mbps preset the same trailer is MB.
Missouri standard: MM.VID.10
You need one file that will play in every major browser and be accepted by Steam. Which codec choice fits best?
Missouri standard: MM.VID.9
If an AV1 export plays in your browser on one computer, it will play in Safari on every Apple device.
Missouri standard: MM.VID.11
Which export settings match the Steamworks trailer guidance?
Missouri standard: MM.VID.11, MM.VID.9
You turn your 16:9 trailer into a 9:16 vertical cut with Reframe and watch it on a phone. The game’s score and your caption are cut off at the sides. What is the best fix?
Missouri standard: MM.VID.9, MM.VID.10, MM.VID.11
Write a one-page delivery memo for your trailer. For each of the three versions, give the outlet, resolution, frame rate, container, codecs and bitrate, the official spec it follows (cite Steamworks, YouTube Help or MDN), and your predicted and actual file size. Then report your playback test: which hardware, software and web applications you tested, what failed and why, and what you changed. End with the posting plan you would ask a parent to approve, including credits for any assets you did not make.
How confident are you that you can evaluate where a video will play, choose a codec and bitrate for the delivery, and export versions of a trailer for a store, social media and archive?
Practice
Work these on paper or in your notebook, then open Check your answer. Aim for all of Fluency and Application; try at least one Challenge.
Printable version: this unit’s practice workbook (PDF)
Fluency
Build speed and accuracy with the core skill.
- Define codec and container, and give two examples of each.
Check your answer
Answer: A codec compresses video for storage and decompresses it to play (H.264, HEVC, VP9, AV1). A container holds video, audio and timing together (MP4, MOV, MKV, WebM).Most video codecs are lossy: more compression means more lost detail. - From MDN’s comparison in the lesson, give one strength and one limitation of H.264, HEVC and AV1.
Check your answer
Answer: H.264: most broadly compatible, but patented. HEVC: in theory about half the size of H.264 at comparable quality, but patented and unevenly supported. AV1: royalty-free and up to 50% better compression than H.264, but in Safari it plays only on devices with a hardware decoder.VP9 is open and royalty-free, with quality comparable to HEVC at similar bitrates. - List the Steamworks trailer guidance from the lesson: resolution, frame rates, bitrate, file types, codecs, aspect ratio, audio sample rate.
Check your answer
Answer: Up to 1920 × 1080; 30/29.97 or 60/59.94 fps; 5,000+ kbps; .mov, .wmv or .mp4; H.264 video with AAC audio preferred; 16:9 preferred (4:3 accepted); 44 or 48 kHz audio.Valve’s own preset uses H.264 at 20 Mbps with AAC stereo at 192 kbps.
Application
Use the skill in context. Show your reasoning.
- Use size = bitrate × duration ÷ 8. Find the file size of a 60-second store trailer at Valve’s preset (20 Mbps video + 0.192 Mbps audio).
Check your answer
Answer: About 151.4 MB.20.192 × 60 = 1,211.52 megabits; ÷ 8 = 151.44 MB. - Find the size of a 90-second trailer at YouTube’s 8 Mbps plus 0.384 Mbps audio, and of a 20-second vertical cut at the same rates.
Check your answer
Answer: 90 s: about 94.3 MB. 20 s: about 21.0 MB.8.384 × 90 ÷ 8 = 94.32 MB. 8.384 × 20 ÷ 8 = 20.96 MB. - Uncompressed 1080p needs at least 1.5 Gbps. How big would a 60-second uncompressed trailer be, in GB? Roughly how many times larger is it than the 151.4 MB store export?
Check your answer
Answer: About 11.25 GB, roughly 74 times larger.1.5 × 60 ÷ 8 = 11.25 GB = 11,250 MB. 11,250 ÷ 151.44 ≈ 74. - An HEVC export plays on your computer in Chrome but not in Firefox on another Windows computer. Using the lesson, is the cause hardware, software or a web application, and what export would avoid it?
Check your answer
Answer: It depends on support in the browser and the device: Chrome uses HEVC where the hardware supports it on Windows, and Firefox on Windows (from version 134) needs hardware decoding or a paid extension. Export H.264 with AAC in MP4, which plays in every major browser.Test each export in at least three places and record what fails and why. - Why does each outlet (store, vertical social, master) get its own export? Name the target and format for each.
Check your answer
Answer: Each outlet has different specs and purposes. Store: 1920 × 1080 MP4, H.264 + AAC at 5,000+ kbps (Steamworks). Vertical social: 1080 × 1920, about 20-30 s, MP4 H.264 + AAC, reframed shot by shot with text moved for the tall frame. Master: the highest quality (ProRes 422 or DNxHR HQ, or a Lossless/HQ preset), kept with the project and source folder, backed up.One file cannot meet a wide store spec, a tall phone frame and an archival quality target at once.
Challenge
Stretch problems. Expect to think before you write.
- In theory HEVC can make a file about half the size of H.264 at comparable quality. Estimate the HEVC size of the 75-second, 189.3 MB store trailer, and explain why you would still deliver H.264 to Steam.
Check your answer
Answer: About 95 MB. Steamworks prefers H.264 with AAC, and HEVC is patented and unevenly supported, so H.264 is the safer delivery even though it is larger.189.3 ÷ 2 ≈ 94.7 MB. Platforms also transcode uploads, so compatibility matters more than size here.
Review
Keep earlier skills sharp.
- Review (Unit 3, Lesson 3.4): what do the store-image rules and the trailer export rules have in common?
Check your answer
Answer: Both are specified in pixels for screens, both are matched to an official platform spec, and both are prepared to the exact size and shape from the best original (crop or reframe first; never stretch or scale up).Pixels per inch does not change screen display; resolution in pixels does.
Trailer Delivery Kit: Outlet Specs, Codecs Compared, File-Size Arithmetic, Export Recipes and Playback Log
SLS original technique sheet; specs from Valve’s Steamworks Documentation (Trailers), YouTube Help (recommended upload encoding settings; Get started creating YouTube Shorts) and MDN Web Docs’ web video codec guide; export steps from the Shotcut FAQ and User Guide and the Kdenlive 26.08 Manual, Rendering (all retrieved 2026-11-10); file sizes calculated by SLS from those bitrates · SLS original
Why this reading. Lesson 5.3 asks you to export your trailer for three outlets and prove where it plays. This sheet collects the official specs in one table, gives export recipes for Shotcut and Kdenlive, works the file-size arithmetic and gives you a playback test log.
1. Specs for each outlet (from the platforms’ own pages, retrieved 2026-11-10)
| Outlet | Resolution and frame rate | Container and codecs | Bitrate | Other |
|---|---|---|---|---|
| Steam store trailer (Steamworks Documentation) | Highest you have, up to 1920 × 1080; 30/29.97 or 60/59.94 fps | .mov, .wmv or .mp4; H.264 + AAC preferred | High, 5,000+ kbps; Valve’s preset 20 Mbps video, 192 kbps AAC stereo | 16:9 preferred, 4:3 accepted; audio 44 or 48 kHz; audio filtered to stereo |
| YouTube upload (YouTube Help) | Same frame rate as recorded; progressive | MP4 with moov atom at front; H.264 High Profile; AAC-LC or Opus, 48 kHz | 1080p: 8 Mbps (24-30 fps) or 12 Mbps (48-60 fps); 720p: 5 or 7.5 Mbps; stereo audio 384 kbps | 16:9 standard; the player adapts to vertical or square |
| Vertical short (YouTube Help, Shorts) | Up to 1080p, vertical | MP4, H.264 + AAC (as above) | As for 1080p | Up to 3 minutes; default privacy private for creators 13-17 |
| Your own web page (MDN) | As made | WebM with AV1 + Opus, with MP4 H.264 + AAC as fallback | — | Shotcut FAQ: WebM and/or Default H.264 |
| Master (Shotcut FAQ, Kdenlive Manual) | Project resolution and frame rate | DNxHR HQ or ProRes 422 (Shotcut); a Lossless/HQ preset (Kdenlive) | As high as the preset allows | Keep with the project file and source folder |
2. Codecs compared (MDN Web Docs, Web video codec guide)
| Codec | Compression | Licensing | Playback |
|---|---|---|---|
| H.264 (AVC) | Lossy; the baseline | Patented; licences apply to commercial use | Every major browser |
| HEVC (H.265) | In theory about half the size of H.264 at comparable quality | Patented | Depends on hardware and operating system; Firefox on Windows from version 134 via hardware or a paid extension |
| VP9 | Comparable to HEVC at similar bitrates | Open, royalty-free | Widely supported by browsers |
| AV1 | Up to 50% better than H.264 | Royalty-free | All browsers, but Safari only with a hardware decoder (M3 MacBooks and later, iPhone 15 Pro, iPhone 16 and later) |
3. File-size arithmetic
File size (MB) = (video Mbps + audio Mbps) × seconds ÷ 8, where 1 byte = 8 bits and 1 MB = 1,000,000 bytes. Real files differ a little because of container overhead and variable bitrate.
| Version | Bitrate | Length | Working | Size |
|---|---|---|---|---|
| YouTube 1080p, 30 fps | 8 + 0.384 Mbps | 75 s | 8.384 × 75 ÷ 8 | 78.6 MB |
| Steam (Valve preset) | 20 + 0.192 Mbps | 75 s | 20.192 × 75 ÷ 8 | 189.3 MB |
| Vertical cut, 1080p | 8 + 0.384 Mbps | 30 s | 8.384 × 30 ÷ 8 | 31.44 MB |
| Uncompressed 1080p (MDN: at least 1.5 Gbps) | 1,500 Mbps | 75 s | 1,500 × 75 ÷ 8 | 14,062.5 MB ≈ 14.06 GB |
The uncompressed version is about 1,500 ÷ 8.384 ≈ 179 times the YouTube version: that is what lossy compression buys, and why motion-heavy gameplay can show blocks or banding at low bitrates.
4. Export recipes
- Shotcut: File > Export > Video. Presets include YouTube and H.264 High Profile (the FAQ’s choice for video-sharing sites). Click Advanced to set the container, codec, resolution, frame rate and rate control (quality-based or bitrate-based); save a custom preset with + and a clear name, such as “Steam trailer H.264 20 Mbps”. For the vertical cut, use Reframe in Export > Video (version 24.09 and later; not in Linear 10-bit processing mode) or start a project with a vertical Video Mode.
- Kdenlive: File > Render (Ctrl + Enter). Generic presets include MP4-H264/AAC and WebM-VP8/Vorbis; Ultra-High Definition includes MP4-H265 (HEVC), WebM-AV1/Opus and WebM-VP9/Opus; Lossless/HQ holds the master options. More Options gives Custom Quality, Rescale and Aspect Ratio, which crops the timeline to the ratio you choose.
5. Playback test log
| Version | Where played (hardware / software / web app) | Plays? | Audio in sync? | Text readable? | Works muted for 10 s? | Notes |
|---|---|---|---|---|---|---|
| Store trailer | Computer / browser 1 | |||||
| Store trailer | Computer / browser 2 | |||||
| Vertical cut | Phone / gallery app | |||||
| Master | Computer / built-in player |
To test a web application offline, save a small HTML page on your computer containing a <video controls> element with a WebM source and an MP4 source (the pattern MDN shows), and open it in two browsers.
6. Sharing
Create no accounts. Post nothing without a parent’s permission, and only on an account a parent already controls. Credit every asset you did not make. Steam requires a trailer before a game can be released on Steam; you are working to its spec as practice.
Sources: Steamworks Documentation: Trailers (Valve) (partner.steamgames.com); YouTube Help: YouTube recommended upload encoding settings (support.google.com); YouTube Help: Get started creating YouTube Shorts (support.google.com); MDN Web Docs: Web video codec guide (Mozilla contributors, CC BY-SA 2.5) (developer.mozilla.org); Shotcut: Frequently Asked Questions (shotcut.org); Shotcut User Guide (PDF, November 2026) (shotcut.org); Kdenlive 26.08 Manual: Rendering (CC BY-SA 4.0) (docs.kdenlive.org)