For a YouTube Live 720p trailer playlist, set the encoder to 1280×720 and use YouTube’s live-ingestion recommendation: 8 Mbps for H.264, or 6 Mbps for AV1 or H.265, at either 30 or 60 fps. Use constant bitrate (CBR), a two-second keyframe interval, RTMPS where available, and an upload connection with headroom.
Those are settings for the signal you send to YouTube, not a promise that every viewer will receive a native 720p version. YouTube transcodes live streams into viewer formats. Separately, a technically correct setup does not settle whether you have rights to broadcast the trailers and their music; confirm that before scheduling.
Choose a frame rate for the trailers
For most trailer playlists, 30 fps is a sensible starting point. It keeps the production straightforward and is sufficient for many film trailers, promotional clips and title cards. Use 60 fps only when the source material and presentation genuinely benefit from it, and when your encoder and connection can sustain it.
YouTube’s 720p live bitrate recommendations are the same at 30 and 60 fps. That does not mean the two choices are interchangeable in every production: the source frame rate, motion, encoder workload and available upload capacity still matter. A 24 fps trailer does not gain detail merely because you output it at 60 fps. Avoid needless frame-rate conversion where it adds no useful information.
Set the encoder’s output resolution to 1280×720 and choose the frame rate deliberately. YouTube says its default is to detect resolution and frame rate automatically; a custom stream key can be used to select resolution manually. Check the selected stream settings in Live Control Room and verify the encoder output before going live. YouTube’s live encoder settings and bitrate guidance is the place to confirm its current recommendations.
For a playlist, inspect the clips rather than relying only on the resolution label in a file browser. If trailers have different frame rates or aspect ratios, decide how you want them presented: preserve their intended proportions with suitable borders, or crop only if doing so does not cut off titles, subtitles or important image details. A consistent 720p canvas helps the transitions feel deliberate, but it cannot restore detail absent from a lower-resolution source.
Compare live bitrate recommendations by codec
Use the live table below when configuring the stream encoder. The minimums are listed for reference; they are not the recommended targets. These figures are YouTube’s ingestion guidance, not upload-encoding bitrates and not an estimate of what viewers will receive after YouTube processes the stream.
| Output | H.264 minimum | H.264 recommended | AV1 or H.265 minimum | AV1 or H.265 recommended |
|---|---|---|---|---|
| 720p at 30 fps | 3 Mbps | 8 Mbps | 2 Mbps | 6 Mbps |
| 720p at 60 fps | 3 Mbps | 8 Mbps | 2 Mbps | 6 Mbps |
These are the same codec recommendations at both listed frame rates. If you use H.264, configure 8 Mbps as the recommended live bitrate. If your encoder and workflow use AV1 or H.265, the listed recommendation is 6 Mbps. In either case, the codec must be supported by your encoder and accepted by the YouTube live setup you use. Do not select a codec solely because its recommended bitrate is lower; confirm compatibility and test the complete chain.
The minimum bitrate is not a goal for normal operation. A connection that only just accommodates the minimum leaves little room for variation, and complex footage can expose weaknesses that a static test image will not. Trailer footage often combines cuts, movement, fine detail, dark scenes and title graphics. Test with representative footage at the intended setting and look for visible breakup or instability in the preview.
Keep live guidance separate from upload settings. YouTube publishes separate recommendations for encoding videos that you upload as files. Those values do not replace the live-stream table above: for this broadcast, use the codec-specific live recommendation. YouTube automatically transcodes a live stream into output formats for viewers, so sending a 720p signal does not guarantee that a particular viewer sees a native 720p rendition. Their device, connection and available playback options affect what they can select.
Set CBR and the keyframe interval
Set rate control to constant bitrate (CBR). A constant target makes the stream’s outgoing data rate more predictable for the network connection than a mode that allows large bitrate swings. Configure the target from the live table: 8 Mbps for H.264 or 6 Mbps for AV1/H.265 at 720p, whether you choose 30 or 60 fps.
Set the keyframe interval to two seconds. YouTube’s live guidance recommends two seconds and says not to exceed four seconds. Some encoder interfaces express this as seconds; others ask for a number of frames. At 30 fps, a two-second interval corresponds to 60 frames, and at 60 fps it corresponds to 120 frames. Check whether the field expects seconds or frames before entering a value, since confusing the two can produce an interval far from what you intended.
Do not treat a longer interval as a way to reduce the bitrate recommendation. Keyframes and bitrate address different parts of the encoding process, and changing the interval does not make the stream conform to the recommended target. After setting both, inspect the encoder’s output status and YouTube’s incoming preview before starting the playlist.
Audio needs its own check. YouTube lists AAC and MP3 as supported audio codecs and recommends stereo at 44.1 kHz and 128 Kbps in its advanced guidance. Choose a single, consistent audio configuration for the playlist and listen for abrupt level changes between clips. Trailer masters can vary considerably in loudness; a technically connected audio stream can still be uncomfortable if one clip is much louder than the next. The YouTube audio and video settings provide the relevant published audio guidance.
Configure the encoder and ingest protocol
Create or select the stream in YouTube Studio’s Live Control Room, then connect your software or hardware encoder using the stream details YouTube provides. YouTube supports both software and hardware encoders; dedicated equipment is not a prerequisite for a 720p stream. Choose based on the production you actually need: a computer running encoder software may be enough for a prepared playlist, while external cameras, switching or other inputs can make dedicated hardware useful.
Use a video output of 1280×720, the chosen frame rate, the codec-specific live bitrate, CBR and a two-second keyframe interval. Set the audio as described above. Use RTMPS if it is available in your encoder and YouTube setup; YouTube describes it as a secure extension of RTMP. Follow the ingest address and stream-key instructions shown in the Live Control Room rather than copying connection values from an old saved profile.
The encoder choice should follow a few practical checks: does it support the codec you intend to use; can it sustain that codec, resolution and frame rate; can it take the required audio and video inputs; and does the computer or device remain stable during a long session? YouTube notes that you do not need expensive equipment to get started. If you do need a hardware video encoder, treat that as a production choice, not a requirement imposed by 720p.
If you are operating from a personal computer, remember that the encoder has to remain active and connected for the live broadcast to continue. For a long-running channel, that brings practical questions about power, network interruptions, restarts and who notices a failure at night. StreamNeo removes the need to leave your own computer running for an uploaded-file broadcast, which addresses that particular unattended-running problem; it does not decide whether a trailer is authorised or replace checking YouTube’s live settings.
A playlist built from separate trailer files also needs an encoder workflow that can advance cleanly from one file to the next. A continuous YouTube playlist preparation checklist can help organise the media side, while setting OBS to play the next video automatically is relevant if OBS is the software doing that job. Whichever method you use, test transitions and confirm that the stream does not stop when one file ends.
Check upload capacity before scheduling
Measure upload speed on the same internet connection, at the location and time you plan to use. Download speed is not a substitute: the stream travels out from your connection, so upload capacity is the relevant side to check. YouTube recommends leaving 20% headroom. Apply that margin to the total streaming bitrate, including audio, rather than assuming that a speed test result equal to the video target is enough.
As a practical calculation, add the video target and audio bitrate, then ensure the measured upload has capacity beyond that combined rate with the recommended headroom. The live video targets here are 8 Mbps for H.264 or 6 Mbps for AV1/H.265; stereo audio at 128 Kbps is a separate part of the outgoing stream. Other traffic on the same connection can compete for capacity, so a connection that looks adequate while idle may behave differently when other people are using it.
A speed test is a snapshot, not a guarantee of a stable broadcast. Repeat it under realistic conditions, use a wired connection where practical, and avoid large uploads or downloads during the stream. If the result varies or the preview reports connection trouble, reduce competing traffic or improve the connection before lowering settings. YouTube’s streaming tips cover its recommendation on upload headroom and related preparation.
Keep a simple record of the test: connection used, upload result, encoder codec and bitrate, frame rate, and whether the Live Control Room preview remained stable. If you need to troubleshoot later, this gives you a baseline rather than a vague memory that the internet seemed fine. For a 24/7 operation, also decide who will respond if the connection drops and how they will verify that the broadcast has resumed. A recovery plan for a continuous stream after an encoder crash is useful background for that operational side.
Build and test the trailer playlist
Prepare the playlist as a broadcast sequence, not just a folder of files. Check that each trailer plays, its audio is present, captions or subtitles are correct if used, and the ending leads sensibly into the next item. Decide whether the sequence repeats, includes a slate between trailers, or has other transitions. A short black gap or sudden audio jump may be noticeable even when the stream encoder itself is configured correctly.
Make a test sequence with the same sorts of material as the intended broadcast: motion, rapid edits, dark scenes, detailed imagery, title cards and the loudest audio changes. Test at the final resolution, frame rate, codec and bitrate. A static image or a single quiet clip is not a useful stand-in for the actual playlist. Watch the Live Control Room preview, check the sound on a separate device if possible, and make sure the stream remains connected through a file transition and a repeat point.
A playlist played locally is not automatically a live broadcast. The encoder must send the sequence to the active YouTube stream, and the playback application must keep moving to the next file. Do not assume that placing videos in a YouTube playlist alone will make them play as a live stream. If your production is built around a computer, rehearse the precise process you intend to use and confirm what happens when the playlist reaches its end.
There is a separate rights issue for movie trailers. A trailer being publicly viewable or available online does not by itself establish permission to rebroadcast it in a live channel. Confirm that you have the necessary rights for each trailer, music track and other included material. YouTube says it scans all live streams for matches to third-party content; if it identifies a match, a placeholder may replace the stream and YouTube may interrupt or terminate it if the content remains.
If you have licensed third-party trailers, YouTube says to ask the rights owner to add your channel to its Content ID allowlist. A licence without that allowlisting may still lead to interruption. Review YouTube’s live-stream copyright guidance and its general copyright guidance for the current explanation. Rules can vary by country or region, and no route guarantees avoidance of a claim or strike. Confirm the position for the specific material before putting the stream on a schedule.
Monitor stream health after it starts
Starting successfully is only the first check. In Live Control Room, watch the preview, stream-health messages and incoming status while the playlist is running. Check that the output remains at the intended resolution and frame rate, the audio continues across transitions, and the connection does not repeatedly drop or fluctuate. If YouTube flags a problem, use the message to identify whether it concerns the incoming signal, network or another setting before changing values at random.
Check from the viewer side as well. Open the live page on a separate device or connection, confirm the programme is visible and audible, and inspect the available playback quality options. Since YouTube transcodes the incoming stream, viewers may have different output options, and they may not see a 720p choice immediately. The encoder’s 720p setting describes what you send to YouTube; it is not a promise of a particular rendition for every viewer.
During a longer run, keep an eye on the playlist’s continuity and the person or process responsible for response. Know how to stop or restart the encoder, how to re-establish the stream if it disconnects, and how to verify that the replacement broadcast is actually live. For guidance on a different sort of continuous YouTube programme, the article on running an online-class playlist as a 24/7 stream covers related scheduling and continuity considerations.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
What bitrate should I use for YouTube Live 720p?
YouTube’s live encoder guidance recommends 8 Mbps for H.264 and 6 Mbps for AV1 or H.265, at both 30 and 60 fps. The listed minimums are 3 Mbps for H.264 and 2 Mbps for AV1/H.265; use the recommended target where your connection and encoder can sustain it.
Should I use 30 or 60 fps for a trailer playlist?
Use 30 fps as a practical starting point unless the source material and presentation benefit from 60 fps. YouTube lists the same 720p bitrate recommendations for both rates, but your source and encoder still need to support the choice reliably.
Will viewers receive native 720p if I send 720p?
Not necessarily. YouTube transcodes live streams into viewer formats, and the available playback options can vary. The encoder setting is your incoming resolution, not a guarantee that every viewer receives or selects a native 720p version.
Can I stream a playlist of movie trailers?
A playlist can be sent as a live programme through an encoder workflow, but simply creating a YouTube playlist does not make it a live broadcast. Separately, confirm that you have rights to the trailers, music and other material, and check YouTube’s current copyright guidance and Content ID requirements before streaming.