For a pre-recorded 720p video, start with 1280×720 output and the frame rate already present in the file. Then choose the bitrate for the encoder’s codec: YouTube recommends 8 Mbps for H.264 or 6 Mbps for AV1 and H.265 at either 30 or 60 fps.
Those are starting points in YouTube’s guidance, not promises that a lower-quality source will look better or that every encoder and connection will behave alike. Check that your upload connection can sustain the stream, send a test with movement and sound, and review YouTube’s live health indicators before relying on it.
Set the output to 1280×720
A 720p output is 1280 pixels wide by 720 pixels high. If your source file is already 720p, use that size as the encoder output rather than enlarging it to 1080p or reducing it to a smaller frame. Matching the source dimensions avoids asking the encoder to invent detail or discard pixels unnecessarily.
If the file is larger than 720p, outputting at 1280×720 can be a reasonable choice when your aim is a 720p live stream. The conversion may reduce fine detail, but selecting a larger output cannot restore detail absent from the original. If the file is smaller, enlarging it to 720p may satisfy your planned output format, but it will not make the source genuinely sharper.
YouTube can detect resolution and frame rate from an incoming stream. If your encoder offers a manual output setting or uses a custom stream key setting, choose 1280×720 there and confirm the received stream in YouTube Studio. The labels differ between tools, so use the encoder’s own documentation for its controls rather than assuming a menu path.
A useful starting checklist is: output at 1280×720, preserve the original frame rate, and use a bitrate appropriate to the chosen codec. Do not treat the resolution field as a quality switch. The source file, encoding choices, and available upload capacity all affect what viewers receive.
Keep the source frame rate
Set the output frame rate to match the pre-recorded file. YouTube’s encoder guidance supports frame rates up to 60 fps, but that does not mean every file should be converted to 60. If a class recording or devotional video was made at 30 fps, transmitting it at 30 fps is the straightforward choice; if it was made at 60 fps, preserve that motion where your encoder and connection can sustain the stream.
Frame rate is the number of distinct images shown each second. Converting 30 fps footage to 60 fps does not create the missing moments from the original recording. Depending on the encoder, it may repeat frames or estimate new ones, neither of which guarantees a more natural result. It can also increase the amount of video data the encoder has to handle.
Conversely, dropping a genuine 60 fps source to 30 fps removes temporal detail. That may be acceptable if bandwidth or processing capacity is limited, but fast movement can look less smooth. Make that trade deliberately rather than setting the highest available number by habit.
A practical check is to inspect the file’s properties or the project/export settings used to make it. If you cannot establish its frame rate, run a short test and inspect the encoder’s output and YouTube’s detected details. The recorded-classes guide for a 24/7 tuition stream is useful context if your source is lessons rather than a single event: the stream’s delivery settings do not replace checking the recordings themselves.
Choose 30 or 60 fps for the content
For ordinary talking, a sermon, a static artwork with a voice track, or a slow ambience scene, 30 fps is usually the sensible starting point when that is how the file was made. Sixty fps is more relevant for fast motion or footage originally captured at 60 fps, such as rapid camera movement or sport. The key is to preserve the source when possible, not to pick a larger figure as a general quality upgrade.
YouTube’s listed 720p bitrate recommendations are the same at 30 and 60 fps for the codecs covered below. That can be surprising: a higher frame rate still carries more temporal information, but the table does not ask you to use a different listed recommendation for 720p60. It is not a reason to convert everything to 60 fps, nor does it remove the need to test your own output.
| File and content | Sensible output starting point | What to weigh |
|---|---|---|
| 720p file at 30 fps, mostly talking or still scenes | 1280×720 at 30 fps | Keeps the source cadence and avoids unnecessary conversion |
| 720p file at 60 fps, with quick motion | 1280×720 at 60 fps | Preserves the motion detail, provided the encoder and connection can sustain it |
| 720p file at 30 fps, converted to 60 fps | Usually keep 30 fps | Upsampling does not add original motion information |
| 720p file at 60 fps, reduced to 30 fps | Consider only for a real constraint | Lower data demand comes at the cost of some motion detail |
The right row depends on the file, not just the channel’s subject. A devotional channel may use a still image for hours, while a recorded dance performance has frequent movement. If you loop multiple clips, check that the source files have compatible frame rates and dimensions; a single output setting may otherwise require conversion at clip changes. For continuity concerns that sit outside picture settings, see how to add background music between videos, but do not assume an encoder’s loop behaviour from a general YouTube guide.
Set H.264 bitrate from YouTube’s table
For H.264 at 720p, YouTube lists a recommended video bitrate of 8 Mbps and a minimum of 3 Mbps for both 30 and 60 fps. These figures come from YouTube’s live encoder settings and bitrate guidance, consulted in 2026. They are official configuration recommendations, not results from a test of your particular file or network.
If your encoder is using H.264, use the recommended value as a place to begin a test, assuming your upload can sustain it. The minimum is not a target that should automatically be chosen to save bandwidth. Below the recommendation, complex movement may show more visible compression; at or above it, a poor source, an overloaded encoder, or an unstable connection can still produce a disappointing stream.
YouTube specifies constant bitrate (CBR) in its listed encoder settings. Set CBR if the encoder provides that control, and set keyframes at two-second intervals; YouTube recommends that interval and says not to exceed four seconds. A particular encoder may name or expose these controls differently, so check its documentation. Do not silently substitute a variable bitrate mode or a different keyframe interval and expect the same result as the documented setup.
The bitrate applies to video, not the entire connection. Audio also uses data, and network conditions vary. Keep room beyond the video bitrate rather than planning an upload connection whose measured capacity merely equals the video setting. If the connection cannot sustain the recommended H.264 rate, investigate whether a different codec supported by your workflow, a lower frame rate already consistent with the source, or another connection makes sense. Do not claim a guaranteed quality outcome from a number alone.
Compare AV1 and H.265 separately
For AV1 and H.265, YouTube’s 720p recommendation is 6 Mbps, with a 2 Mbps minimum, at both 30 and 60 fps. The figures are listed separately from H.264 in the same YouTube encoder guidance. Do not merge the codec-specific figures into one universal 720p bitrate: the recommended values differ by codec.
Choose the row that matches the codec actually being sent. An encoder’s dropdown may offer several codecs, but availability and compatibility depend on that encoder and the ingest workflow you are using. If you are not sure which codec is active, verify it in the encoder’s settings and in the stream details rather than inferring it from the chosen bitrate.
The lower listed rate for AV1 and H.265 does not mean you should set an H.264 stream to 6 Mbps and expect equivalent results. Nor does selecting AV1 or H.265 make a low-resolution, noisy, or poorly focused source more detailed. It is a codec-specific recommendation. The encoder must support the format correctly, and you should test what YouTube actually receives.
Keep the rest of the configuration consistent while comparing: same source segment, resolution, frame rate, audio, and network conditions. If you change codec and several other settings at once, it becomes harder to identify why the result changed. A short local test can help spot encoding artefacts, while a private or otherwise appropriate YouTube test stream helps you check the full path to the platform.
Configure audio and colour without overcomplicating it
For ordinary stereo audio over RTMP or RTMPS, YouTube’s recommended settings are AAC or MP3, 44.1 kHz sample rate, and 128 Kbps. For a simple spoken recording or music bed, stereo is often sufficient. If your source uses 5.1 audio, YouTube’s guidance says that over RTMP/RTMPS it is supported only with AAC, at 48 kHz and 384 Kbps. Confirm that the file and encoder really contain that format before selecting it.
For standard dynamic range (SDR), YouTube lists Rec. 709 and 8-bit colour as recommended advanced settings. If your source was created in a different colour format or has a specific HDR workflow, do not change it blindly based on a generic 720p checklist. The output colour space should make sense for the content and the encoding path.
Audio defects can be mistaken for a stream failure: a silent file, clipped dialogue, or unexpected channel layout will remain a problem even if the video bitrate is correct. Listen to a test stream on the device your audience is likely to use, and check the opening and any transitions. Keep voice and music at a usable balance rather than simply maximising the encoder’s audio level.
For transport, YouTube recommends RTMPS, its secure extension to RTMP, when your encoder supports it. Treat the stream key as a password: YouTube says to keep it private. Its guide to creating a live stream with an encoder explains the general workflow of creating a stream in YouTube Studio and sending the feed from software or hardware. It does not establish the precise loop or scheduling steps for every prerecorded-video tool.
Check upload capacity and test the stream
Your upload connection must sustain the outgoing stream over time, not merely show a brief high result in a speed test. The chosen video bitrate is only part of the traffic, and other devices on the same connection can compete for upload capacity. YouTube advises checking internet speed and testing before going live. Measure from the location and connection you intend to use, and test at the actual output settings rather than assuming a result from another room or time applies.
A test should contain both sound and movement. A static title card will not reveal how motion is encoded, and silence will not expose an audio-level problem. Watch the test playback, check that it is not repeatedly stalling, and review YouTube Studio’s stream health and warnings. If the upload varies or drops, first reduce competing network use or address the connection; changing several encoder values at once obscures the cause.
For a planned always-on broadcast, the test needs to represent the conditions under which you expect it to run. A laptop that sleeps, an encoder that stops when a file ends, or a connection that is shared with household traffic can interrupt playback even when the 720p numbers are correct. YouTube’s general encoder workflow explains how to send a live feed; it does not document the looping behaviour of every playback application. Follow the current documentation for the software you choose.
If the specific difficulty is keeping a computer available for a long-running broadcast, the guide to streaming without keeping a laptop open covers that operational decision. StreamNeo addresses the particular problem of leaving your own computer switched on for an always-on file-based YouTube broadcast: you upload the file, provide the stream key, and it runs without a local computer, with monitoring and automatic restarts if a drop occurs. It is YouTube-only; it does not remove the need to select appropriate settings, protect the key, or check the stream and source rights yourself.
Verify what YouTube receives
After sending the test, confirm that YouTube detects the intended resolution and frame rate. A file set to 1280×720 in an export dialog does not prove the live feed reaches YouTube at that size. Check the stream details in Studio or the Live Control Room, and compare the detected values with the encoder output.
Review the stream health messages while the test is running. Warnings can point to an incoming bitrate, connection, or encoding issue; use the message as a lead to investigate rather than assuming a single warning identifies the whole cause. If the feed is unstable, check both the network and the computer or playback tool generating it. If the stream is healthy but the image looks soft, inspect the source file and its scaling before increasing bitrate.
Do not judge only from a still frame. Watch a portion with movement, listen through a representative passage, and check transitions if your live programme changes clips. A 720p source with compression damage may remain soft at the recommended bitrate. Conversely, a clean static source may not visibly benefit from raising a setting beyond the recommendation. More bitrate is not a repair for missing source detail.
If the first test was not satisfactory, change one variable, repeat the same segment, and compare what you see. For example, if a 60 fps source is being converted or the connection is struggling, a source-matched 30 fps workflow may be worth testing only if that trade-off is acceptable. Preserve notes about the codec, rate, output size, and observed warnings so you can return to the last working configuration.
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
Is 6 Mbps enough for every 720p live stream?
No. YouTube lists 6 Mbps as its recommendation for AV1 and H.265 at 720p, while its H.264 recommendation is 8 Mbps. The correct row depends on the codec, and your source, encoder, and connection still need to be tested.
Should I use 30 fps or 60 fps for a pre-recorded video?
Keep the frame rate the file was made with where possible. Thirty fps is a sensible match for a 30 fps source with ordinary movement; 60 fps can preserve faster motion when the source is 60 fps. Converting to 60 fps does not recreate motion detail that was never recorded.
Can I stream a file by following YouTube’s encoder guide?
YouTube’s guide covers sending an encoder feed and managing the stream, but it does not give exact loop or scheduling instructions for every application. Check the current documentation for the specific software or hardware you use, and test the playback behaviour before relying on it for a long broadcast.
What should I do if YouTube detects less than 720p?
Check the encoder’s output dimensions and the detected stream details, then inspect whether the source is actually 720p. Test again after correcting one setting at a time. A larger bitrate will not by itself change a lower-resolution feed into 720p.