“Pre-recorded live stream” can mean either a normal video uploaded to YouTube or prerecorded footage sent out through a live encoder. The recommended container and codecs depend on which route you mean: YouTube’s upload guidance recommends MP4 with H.264 video, while its live-ingest guidance lists RTMP or RTMPS and different codec options.
Neither list should be read as a complete acceptance policy. They are published recommendations and encoder settings for distinct workflows; check YouTube’s current guidance before preparing an important stream.
First decide what “pre-recorded live” means
The phrase is ambiguous because a video can be prerecorded in two different ways. You might upload a finished file as a regular YouTube video, where viewers watch it as a video upload. Or you might feed a file or playlist through a live encoder, so YouTube receives it as a live broadcast.
The second route is what many channel owners mean by a 24/7 playlist, a scheduled loop, or a continuous devotional, lofi, study, or news channel. The content may have been recorded earlier, but the broadcast still uses YouTube Live’s ingest process. A normal upload does not become a live broadcast merely because its contents were recorded in advance.
This distinction matters when you see answers such as “use MP4” or “YouTube Live accepts H.264”. MP4 is a container recommendation for a file upload. H.264 is one of the video codecs listed for live ingest, but YouTube also lists other live video codecs. Those statements describe different stages, so combining them into a single format rule is misleading.
A useful first question is: will YouTube receive a completed file through the upload flow, or will an encoder send a live feed to your stream URL and key? Choose the corresponding guidance below. If your setup involves a third-party encoder or cloud service, verify that it supports the protocol and codec combination required for the workflow you intend to use.
For a normal upload: MP4 and recommended codecs
For a regular video-file upload, YouTube’s recommended upload settings specify an MP4 container, H.264 video, and AAC-LC, Opus, or Eclipsa Audio. This is a recommendation, not a claim that YouTube accepts only those formats. The official page is titled YouTube recommended upload encoding settings; refer to it for the current details rather than treating a short summary as the full policy.
A container is the file wrapper that holds video, audio, and related information. H.264 is the video compression format inside the wrapper. Audio has its own codec. Keeping those roles separate helps when an export tool asks for a “format” and then offers separate video and audio settings.
For an uncomplicated export, MP4 with H.264 video and one of the recommended audio codecs is a sensible starting point. YouTube’s upload guidance also recommends progressive scan, preserving the frame rate used when recording, and a 48 kHz audio sample rate. It advises avoiding edit lists and placing the MP4’s moov atom at the beginning of the file, a setting often called “Fast Start”. These are useful export details, but they should not be mistaken for the live encoder requirements discussed later.
Preserving the source frame rate avoids unnecessary conversion. If a video was recorded at one frame rate and exported at another, the encoder may have to duplicate or discard frames; that can affect motion, especially with moving artwork, scrolling text, or footage. Do not increase the frame rate simply because an export menu allows it. If you are making a continuous feed rather than uploading a finished file, your encoder settings are the more relevant reference.
For an upload, inspect the exported file before publishing: confirm that it plays through, that the audio is present and in sync, and that the image is oriented and framed as intended. A successful local playback does not guarantee every platform processing result, but it catches basic export mistakes before you wait for an upload to complete.
For live ingest: protocol and supported codecs
When prerecorded footage is sent through a live encoder, the relevant settings are in YouTube’s live encoder documentation. Its listed ingest protocols include RTMP and RTMPS; its live settings page lists H.264, H.265/HEVC, or AV1 for video, and AAC or MP3 for audio. See Choose live encoder settings, bitrates, and resolutions for the current published encoder guidance.
Here, RTMP or RTMPS describes how the encoder sends the feed to YouTube. It is not a video codec, and it is not a file container such as MP4. The video and audio codecs describe how the picture and sound are encoded within that live feed. A tool that can open an MP4 file is not necessarily able to send a live feed, and an encoder that can stream H.264 does not by itself answer what settings to use for a normal upload.
YouTube’s listed live guidance recommends constant bitrate (CBR) and a two-second keyframe interval, with a maximum interval of four seconds. It also gives a frame-rate ceiling of up to 60 fps. These are live-ingest settings, not instructions for changing the frame rate or keyframes of an uploaded MP4. If you are configuring an encoder for an ongoing playlist, start with the platform’s current recommendations and test the actual output rather than assuming the source file’s export settings carry over unchanged.
The keyframe interval affects how often the encoder supplies a full reference frame, which can influence how the stream is processed and how viewers recover after joining. The practical lesson is not to tune every parameter in isolation: use the encoder’s YouTube profile where available, check that its output matches the selected protocol and codec, then inspect the preview and stream health before relying on it overnight.
For a first test, send representative material rather than a still image only. Include the kind of motion and audio the channel will actually use, then check the live preview, sound, and stream health. YouTube’s encoder setup instructions explain the setup flow. Treat the stream key as a credential: enter it only in the encoder or service that should broadcast to your channel, and do not publish it with a link or screenshot.
Keep upload and live settings separate
This comparison keeps the two paths distinct. It is a compact guide to YouTube’s published recommendations, not a complete list of every format or configuration the platform might accept.
| Workflow | Container or transport | Video | Audio | Useful detail |
|---|---|---|---|---|
| Regular file upload | MP4 recommended | H.264 recommended | AAC-LC, Opus, or Eclipsa Audio | Preserve source frame rate; use progressive video and the recommended upload settings |
| Live feed from an encoder | RTMP or RTMPS listed | H.264, H.265/HEVC, or AV1 listed | AAC or MP3 listed | CBR; two-second keyframes recommended, with a four-second maximum |
| HDR live workflow | RTMP(S) or HLS, depending on the documented setup | HEVC in YouTube’s HDR guidance | Follow the encoder’s applicable setup | HDR has additional bit-depth and transport details |
Do not take “MP4” from the upload row and assume that it is the required live transport. Likewise, do not take AV1 from the live video list and assume that it is the recommended codec for a normal upload. They are not interchangeable answers to the same question.
YouTube says it transcodes live streams into multiple output formats for playback across devices and networks. That means your encoder settings describe what you send to YouTube, not the exact codec or resolution every viewer will receive. You are responsible for a compatible ingest feed; YouTube’s playback processing is a separate step.
If you use FFmpeg, OBS, or another encoder, keep a saved profile for the live output and a separate export preset for file uploads. This avoids changing the wrong settings when switching between a scheduled live loop and a regular video. The practical FFmpeg resolution guide for a nonstop playlist stream can help with one part of that configuration; for keyframes, see the separate explanation of keyframe intervals for 24/7 streams.
Where HDR live streaming differs
HDR adds constraints that do not apply to every standard dynamic range stream. YouTube’s HDR live guidance specifies HEVC video and a 10-bit HDR configuration. The encoder guidance does not list AV1 as supported for HDR in that setup. If you need HDR, use the dedicated Stream HDR video on YouTube instructions rather than inferring HDR compatibility from the general live codec list.
The HDR documentation also covers HLS, where the guidance specifies transport stream (TS) segments with durations between one and four seconds. Those segment details belong to the documented HLS path; they are not an MP4 upload rule, nor a general requirement to impose on every RTMP stream. Consult the official page for the complete configuration and check that your encoder supports the HDR mode you are selecting.
Before committing to HDR, consider what your source actually contains and whether your full playback chain is prepared for it. An HDR label alone cannot restore highlight or colour information that was not captured or mastered into the source. A standard dynamic range source can remain a standard dynamic range stream; do not convert settings simply to use a more complex mode.
Choose the workflow that matches your goal
If you want a finished video available on your channel, use the upload workflow. Export the file using YouTube’s recommended upload combination as a starting point, check its playback, then upload it in Studio. This is the straightforward route for a one-off recording, a completed lesson, or an archive that viewers can watch on demand.
If you want viewers to encounter a live broadcast at a scheduled time or to keep a channel running from a playlist, use live ingest. Your encoder must send a live feed using YouTube’s stream configuration, even when the material itself was recorded earlier. You can operate that encoder on a computer you maintain, or use a managed workflow if you do not want a local machine to be responsible for a continuous broadcast.
That choice also determines what can fail. In a local setup, a computer sleeping, an operating system update, an encoder crash, or a network interruption can stop the feed. A computer-based workflow may still be the right fit if you already run an encoder and can monitor it. The OBS setup guide for a 24/7 playlist on Windows is relevant if that is your route; the cloud service comparison for nonstop YouTube streaming in India can help frame the alternative without changing the codec requirements.
For a channel whose main pain is leaving a personal computer running and restarting a dropped broadcast, StreamNeo turns an uploaded video into a YouTube live stream that can run with your computer switched off and restart if it drops. That addresses the continuity burden; it does not change YouTube’s separate upload recommendations, replace your responsibility for the content, or make an untested source file suitable for broadcast.
Whatever route you choose, test the exact file, audio, encoder profile, and channel configuration you intend to use. Check the stream preview before an important event, and confirm current guidance in YouTube Help: platform settings can change, and a published recommendation is not a guarantee that every file will process identically. For a continuous stream, decide who will notice a problem and what they will do about it, rather than treating “live” as synonymous with unattended.
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 format should a prerecorded YouTube Live stream be?
If you mean a normal file upload, YouTube recommends MP4 with H.264 video and AAC-LC, Opus, or Eclipsa Audio. If you mean prerecorded footage sent through a live encoder, use the separate live-ingest guidance: RTMP or RTMPS with one of its listed video and audio codecs.
Can I upload an MP4 and make it a live stream?
Uploading an MP4 through the normal video-upload flow publishes a video; it does not make that file a live broadcast. To present prerecorded footage as a live stream, an encoder or live-streaming workflow must send it to YouTube as a live feed.
Does YouTube Live accept HEVC or AV1?
YouTube’s live encoder settings list H.265/HEVC and AV1, as well as H.264, for video ingest. HDR has separate guidance: follow YouTube’s HDR instructions for HEVC and the relevant transport details rather than assuming the general codec list applies unchanged.
Should I use the same settings for uploads and live streams?
No. An upload is a file-format and export-settings question; live streaming is an encoder and ingest question. Keep separate presets, and check YouTube’s current official pages before changing either workflow.