You can preserve a film’s 23.976 fps cadence in your encoder if it supports 24000/1001, but YouTube’s published live-stream guidance does not specifically confirm that incoming rate. For a cautious starting point, use the bitrate row for your resolution at 30 fps as an approximation, then send a test stream and check its health before scheduling the playlist.
That distinction matters: preserving the source cadence is a sensible encoder choice, not evidence of a documented YouTube ingest guarantee. The published tables and API settings leave the fractional rate unspecified, so treat the first broadcast as a test of your complete setup rather than assuming the frame-rate label settles the question.
What YouTube documents about incoming frame rates
YouTube’s live encoder settings guidance gives general recommendations for resolution, frame rate, bitrate, codecs and other settings. It says the encoder should use a frame rate up to 60 fps, but does not enumerate 23.976 fps as an incoming choice. That language sets a broad upper range; it does not establish support for every possible fractional rate within it.
The YouTube Live Streaming API’s cdn.frameRate field is more specific about the values exposed for stream configuration. Its documented values are 30fps, 60fps and variable; it does not list a dedicated 23.976 value. The API reference is useful evidence about what that field accepts, but it is not a definitive statement that YouTube’s ingest pipeline rejects a signal produced at 23.976 fps.
The practical conclusion is deliberately narrower than either “YouTube supports it” or “YouTube will reject it”. In the official pages reviewed, exact 23.976 fps ingestion remains unspecified. You can preserve the film’s cadence in your encoder and verify what happens with your chosen stream key, settings and workflow.
YouTube says Live Control Room detects encoder resolution and frame rate automatically by default. A custom stream key can enable manual resolution settings. It also transcodes incoming live video into different formats for viewers, so the input configuration and every viewer’s playback output are not the same thing. Do not assume that selecting one input cadence means every viewer receives that exact cadence.
Preserve 23.976 cadence if your encoder supports it
A film labelled 23.976 fps commonly uses a rate of 24000/1001 frames per second. If your encoder offers that exact rate, retaining it avoids an unnecessary conversion before the video reaches YouTube. It is a source-preserving choice: it keeps the intended timing relationship between the film’s frames rather than forcing an arbitrary conversion simply because a settings menu has a familiar 30 fps option.
Check the encoder’s actual output setting, not only a project label or a file’s metadata. Some tools display rounded values, while others allow you to choose a precise fractional rate. Make sure the selected mode is progressive if the source is progressive, and avoid switching frame-rate modes between playlist items without testing the result. A playlist can contain films with different properties even when the files look similar in a media library.
For a conventional SDR stream, YouTube’s settings guidance identifies Rec. 709 and 8-bit as recommended advanced video settings. It recommends constant bitrate (CBR), a two-second keyframe interval, and says not to exceed four seconds. Those settings do not confirm 23.976 ingest, but they give you a documented baseline around which to test it. YouTube lists H.264, H.265/HEVC and AV1 as video codec options in its encoder guidance; the available codec choices depend on your encoder and workflow.
YouTube recommends RTMPS, and its encoder settings page covers RTMP/RTMPS. If your setup uses HLS ingestion instead, follow the separate HLS ingestion documentation rather than applying RTMP assumptions to it. HLS segment duration and RTMP keyframe interval are different settings: YouTube’s HLS guide recommends media segments of one to four seconds, while its general encoder guidance recommends a two-second keyframe interval. Do not treat those as interchangeable controls.
Audio needs a check alongside video. For RTMP/RTMPS, YouTube lists AAC or MP3, and specifies 44.1 kHz for stereo with 128 kbps stereo audio. A film may have a quiet opening, a long silent passage, or dialogue that is much easier to assess with headphones than from a dashboard indicator. Confirm that the encoder is sending the intended track and that the live preview carries clean, continuous sound.
If your files have different frame rates, resolutions or audio layouts, note those differences before building the loop. A cadence-preserving setting for one title does not prove every file in a playlist will behave identically. The operational lesson is to choose a consistent, intentional encoder configuration, then test the transitions and representative content that will actually be broadcast.
Why 23.976 ingestion remains unconfirmed
The general Help page’s “up to 60 fps” wording describes an upper limit, not a list of all accepted rates. The API’s named choices describe values for a particular configuration field, not every possible signal that the wider ingest pipeline might handle. Taken together, the pages neither specifically confirm 23.976 fps nor establish that it is refused.
This is why a careful setup should use words such as “unconfirmed in the reviewed documentation” rather than “officially supported” or “unsupported”. Platform documentation can be updated, and settings available in an encoder, an API field and the live ingest service are related but not identical. If this exact rate is important to your channel, check the current official guidance and test the stream you intend to run.
The API also documents a variable frame-rate option paired with variable resolution. That option should not be casually equated with a fixed 23.976 fps film output. A constant-rate film source and a variable-rate mode are different choices; use the mode your encoder and channel workflow can manage, and rely on the test and stream-health feedback to assess the result.
YouTube’s documentation on settings, health and latency does not lay out how an encoder should schedule, loop or transition a multi-file film playlist. It cannot validate your playlist’s end behaviour, file hand-offs or sound continuity. Those must be exercised in the encoder or playback workflow you will actually use.
Frame rate also says nothing about whether you have the rights to stream a particular film. The technical pages cited here do not decide that question. Establish the distribution rights for each title independently, and consult current official platform guidance rather than treating a working technical test as rights clearance.
Use the 30 fps bitrate row as an approximation
YouTube publishes bitrate rows by resolution and by 30 fps or 60 fps classes, not by 23.976 fps. For a 23.976 fps input, the 30 fps row is therefore a practical approximation for a starting bitrate, not an official YouTube recommendation for that fractional rate. Match the row to your output resolution and codec, then confirm the result on your actual upload connection.
| Output and codec | YouTube’s published 30 fps row | How to use it for 23.976 fps |
|---|---|---|
| 1080p, H.264 | 5 Mbps minimum; 14 Mbps recommended | A practical starting reference, not a 23.976-specific recommendation |
| 1080p, AV1 or H.265 | 4 Mbps minimum; 10 Mbps recommended | A practical starting reference, not a 23.976-specific recommendation |
| 720p, H.264 | 3 Mbps minimum; 8 Mbps recommended | A practical starting reference, not a 23.976-specific recommendation |
| 720p, AV1 or H.265 | 2 Mbps minimum; 6 Mbps recommended | A practical starting reference, not a 23.976-specific recommendation |
These figures are the values in YouTube’s current encoder-settings table as reviewed for this article in October 2026; the table labels them for 30 fps, not for 23.976 fps. The minimum and recommended figures are not a promise that a connection will deliver a stable broadcast. The right choice depends on whether your upload link can sustain the outgoing stream during normal use, not just during an isolated speed test.
If you are choosing between codecs, use one your encoder, stream key and intended workflow support reliably. Codec efficiency can affect the bitrate needed for a given picture, but a codec that is awkward to configure or unstable in your tool is not automatically a better choice. For HDR, YouTube recommends H.265 and says AV1 is not supported for HDR in the cited settings guidance; if the playlist is SDR, do not select HDR settings just because they are available.
Do not lower a film’s cadence to chase a bitrate row. Frame rate and bitrate solve different problems: cadence describes how frames are timed, while bitrate describes the amount of encoded data sent over time. If the upload connection cannot sustain a recommended rate, reduce resolution or choose a more conservative tested configuration rather than assuming the frame-rate conversion will fix the network constraint.
For a practical decision, compare three things together: source cadence, resolution/codec row, and reliable upload capacity. The YouTube values give a documented reference point for the second item; they do not substitute for checking the third. If you are already investigating bitrate for a different high-resolution source, the 4K 60 fps bitrate guide is relevant for understanding why resolution and frame-rate classes change the table, but its 60 fps values should not be copied onto a 23.976 fps film stream.
Send a test stream and inspect stream health
Before you schedule the playlist, send a private or otherwise non-public test stream using the same encoder, output frame rate, codec, bitrate, audio source and stream path you plan to use. YouTube’s guidance says to test before going live, using movement and audio similar to the intended stream. A static menu screen is a poor stand-in for a film with pans, credits, grain, dark scenes and music.
In Live Control Room, inspect stream health and any warnings or messages while the encoder is sending. Confirm that the incoming stream remains connected, that the audio and video are present, and that the settings shown are the ones you intended to send. Health feedback is more useful than simply seeing a preview image once; leave the test running long enough to observe sustained behaviour and a file transition if your workflow has one.
For a 23.976 output, the test answers a practical question rather than rewriting the documentation: does this encoder-to-YouTube path accept and handle the signal in your circumstances? Keep a record of the encoder configuration and any health messages. If the stream reports a problem, change one setting at a time so you can tell whether the issue is frame rate, bitrate, audio, connection or a transition in the playlist.
Do not infer too much from one successful preview. It confirms that a preview was visible at that moment; it does not guarantee the stability of an overnight run, performance under a different network load, or successful handling of every file in the playlist. For a channel that must keep going through an internet interruption, the guide to preventing outages covers the separate reliability problem of keeping an always-on stream available when the connection fails.
If the test indicates congestion, first compare the chosen bitrate with the upload capacity available to the encoder while other household or business traffic is active. You can reduce the outgoing bitrate, reduce resolution, or move other traffic off the connection; change settings deliberately and repeat the test. A short speed test is a useful check, but it cannot by itself demonstrate that the upload will remain steady through a long broadcast.
Check representative film playback before scheduling
Test more than the opening frame. Choose a representative stretch with motion, a quiet or dark scene, dialogue or music, and a title or credit sequence if those appear in the playlist. Look and listen on the YouTube preview, and if possible check playback from another device or connection. This helps separate an encoder-side problem from a viewer-side buffering or device issue.
Then test the playlist as a whole in the actual encoder workflow. Confirm what happens when one file ends and the next begins, whether the next title starts at the intended point, whether audio cuts, overlaps or falls silent, and whether the playlist stops, repeats or waits at the end as intended. The official encoder pages reviewed do not specify multi-file scheduling or transition behaviour, so this must be tested rather than inferred from YouTube’s frame-rate guidance.
A film’s cadence may be preserved within each file while the playlist still has uneven motion at a transition. That can happen if files have differing frame rates, if the encoder changes output modes, or if a loop restarts with a pause. Watch the hand-off rather than judging only a continuous scene from a single title. If the workflow converts files to a common output rate, inspect whether the motion remains acceptable before you use that setting in a long run.
Latency is another separate choice. YouTube defines stream latency as the time between capture by the encoder or camera and presentation to the viewer. Lower latency can increase playback buffering; if viewers are watching a film playlist without interacting live, immediate delivery may matter less than stable playback. YouTube’s DVR controls let viewers pause, rewind and resume an event, which may be useful for a long-form channel, although the available behaviour depends on the stream settings.
If you are comparing a local computer with a hosted workflow, focus on who has to keep the encoder running and who will notice a stopped broadcast. StreamNeo turns an uploaded video into a YouTube-only 24/7 live stream, so the specific pain it removes is leaving your own computer switched on to keep the file playing; you still need to prepare the file, connect the channel and test the finished stream. A playlist of Hindi devotional material has its own sequencing considerations, described in this guide to rotating Hindi songs by mood.
Once the exact playlist, stream key and output settings have passed a representative test, document them so the next scheduled run starts from a known configuration. Note the chosen cadence, resolution, codec, bitrate and audio format, along with anything you had to change after reading health feedback. If a film is replaced, a file is re-encoded or the upload connection changes, repeat the relevant checks rather than assuming the earlier test applies unchanged.
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
Can I stream 23.976 fps to YouTube Live?
YouTube’s general encoder guidance says up to 60 fps, while the API’s documented cdn.frameRate values are 30 fps, 60 fps and variable. The official pages reviewed do not specifically confirm 23.976 fps ingestion, so preserve the source rate if your encoder supports it, then test and check stream health.
What bitrate should I use for a 23.976 fps film stream?
Use the published 30 fps row matching your resolution and codec as a practical approximation, not as an official 23.976 recommendation. For example, YouTube’s table lists 1080p H.264 at 14 Mbps recommended for 30 fps, while the 1080p AV1/H.265 row recommends 10 Mbps; check that your upload can sustain the selected rate.
Should my live film playlist be 24 fps or 30 fps?
If the encoder offers 24000/1001 and the source is 23.976 fps, preserving that cadence avoids an unnecessary conversion. YouTube’s documentation reviewed here does not specifically settle fractional-rate ingest, so the deciding step is a test with your complete encoder and playlist, not an assumption that 30 fps is required.
What keyframe interval should I use, and how do I test the playlist?
YouTube recommends a two-second keyframe interval and says not to exceed four seconds. Send a test with representative motion and audio, inspect Live Control Room’s stream health, and check file transitions, audio continuity and end behaviour before scheduling the complete playlist.