If your YouTube Live channel mainly plays a pre-recorded video, use the file’s actual frame rate as the starting point for OBS. Matching is a practical default for preserving the video’s cadence, not a YouTube Live requirement.
In OBS, open Settings > Video > Common FPS Value and choose the appropriate rate. Then test the stream with representative motion and audio: a setting that fits the file still has to run reliably on your computer and connection.
Find the source video’s actual frame rate
Check the video’s media information or the export settings used to make it. A file’s resolution does not tell you its frame rate: two 1080p videos, for example, may have different rates. If you still have the editing project, its export details are often the clearest record of what was produced.
Do not assume that a devotional recording, lofi loop, news package or lecture is 30 fps just because that rate is common. YouTube’s upload guidance lists 24, 25, 30, 48, 50 and 60 fps as common rates, and says uploaded content should retain its recorded rate. That advice is useful context for preserving cadence, but it is upload guidance, not an explicit rule for an OBS media source in a live stream. See YouTube’s recommended upload encoding settings for the distinction.
If you are choosing a rate for a playlist rather than one file, check the important clips individually. A channel might combine a 25 fps local news segment with a 30 fps studio introduction, or mix older 24 fps footage with newer material. There is no single rate that can preserve every source’s original cadence in a mixed playlist; choose for the material viewers will see most, then test the transitions.
This is also a useful point to decide whether your channel needs to play a single continuous file or manage a changing set of sources. For a simple rerun playlist, the approach described in how to make YouTube gaming reruns resume after a reboot raises a related operational question: what should happen when playback is interrupted? The frame-rate choice and the restart behaviour are separate decisions.
Open OBS video settings
In OBS, select Settings and then Video. The page includes Base (Canvas) Resolution, Output (Scaled) Resolution, and Common FPS Value. For this task, the last control determines OBS’s intended output frame rate. OBS’s overview guide explains these video settings and says Common FPS Value should match the desired output FPS.
Keep resolution and frame rate separate in your thinking. Changing the canvas or scaled output resolution does not set the FPS, and selecting an FPS does not decide the output resolution. If the video is 1080p, for instance, you can still choose a different output resolution for the stream; make each choice deliberately rather than changing several controls at once and losing track of what helped.
If you are following an existing OBS profile, check that you have opened the profile used for the intended stream. A setting changed in one profile may not carry over to another. Before going live, confirm the profile, the selected video source, the audio path and the output settings together.
For a long-running channel, it helps to keep a short note of the chosen settings beside the programme schedule: source rate, OBS output rate, resolution, and the result of the last test. This is more useful than relying on memory after a computer restart or a handover. It also makes it easier to compare a later change with the configuration that was behaving as expected.
Set Common FPS Value
Choose the source rate if it is available as a Common FPS Value and it suits the intended output. If your file is 25 fps, start by selecting 25; if it is 30 fps, start at 30. This does not mean that OBS must always copy a source rate exactly, or that YouTube requires it. It is a straightforward default when most of the broadcast is one pre-recorded video.
The reason is cadence. A video contains frames at its own rate; the stream output has a rate of its own. When those rates differ, frames may need to be repeated, omitted or otherwise mapped onto the output timing. The exact result depends on the source, output setting and playback path. Matching rates avoids asking the output to run at a different cadence from the main content, but it does not guarantee a better-looking stream or fix unrelated problems such as poor encoding performance or an unstable connection.
If OBS does not offer the file’s precise rate in the control, do not treat that as a reason to invent a custom setting or assume a higher number is better. Choose the nearest sensible available output rate, test it, and watch the motion. When the source rate and output rate differ, judge what viewers actually receive rather than relying on the setting name alone.
YouTube’s live guidance is separate: it publishes an encoder frame-rate limit of up to 60 fps. That is a ceiling, not an instruction to use 60, and it does not turn a 60 fps output into extra detail in a 24 or 25 fps source. The practical choice remains tied to the source and the system that must render and encode the stream.
When matching is practical
Matching is easiest when one file, or a group of files with the same rate, accounts for most of the stream. A 25 fps recorded sermon played for hours is a simple case: set OBS’s output to 25 fps if available, then check a test broadcast. The same logic applies to a 30 fps study loop, a 24 fps ambience film or a 60 fps gaming rerun, provided the computer can handle the selected output.
A rate match is especially useful when the video has visible, regular motion: a person speaking and moving their hands, a scrolling ticker, a camera pan, or moving text over a background. A still image with music may not reveal cadence differences as readily, but that does not make the rate irrelevant. Test the parts that viewers are likely to notice, not only the opening frame.
For a collection of clips with different rates, select the rate that best serves the dominant or most important material. If transitions between files are frequent, review several changes in a test. A playlist that alternates 24, 25 and 30 fps cannot retain all three original cadences through one fixed output rate. Decide which compromise looks most acceptable in the actual programme.
A broader guide to common live-streaming encoding workflows can help put this one setting in context. FPS is only part of the output path: the source, encoder, selected resolution and connection all matter. Keeping those decisions distinct makes troubleshooting less confusing.
When to consider 30 fps instead
Consider 30 fps if a 60 fps output makes OBS unstable or the computer cannot keep up. OBS’s performance troubleshooting guidance recommends trying 30 fps when 60 fps does not work, because fewer frames can reduce rendering and encoding work. That can be a useful trade-off, but it changes the output cadence relative to a 60 fps source. Test your own footage before settling on it.
Do not raise a 24, 25 or 30 fps source to 60 just because YouTube allows up to 60 fps. A higher output setting does not create source frames that were never recorded. For low-motion material, the visual difference may be less obvious than for a fast camera pan or sports footage, but there is no general reason to choose the higher rate without a need for it.
There are two separate limits to consider. OBS needs enough capacity to render and encode the chosen output; the connection needs enough upload capacity for the selected stream. Lowering the FPS may ease the first problem, but it does not automatically solve the second. YouTube’s live encoder page lists bitrate guidance that varies with resolution, frame rate and codec. Check its current live encoder settings rather than assuming that one bitrate suits every 30 or 60 fps stream.
The lower-rate choice may be sensible for a quiet devotional loop where motion is limited and a computer struggles at 60 fps. For fast gaming footage, a change from 60 to 30 may be more noticeable. There is no universal winner: weigh the source cadence, the motion viewers will see, system stability and the bitrate you can sustain at the chosen output.
Test cadence and system load
Test with the same file, audio, transitions and OBS scene you intend to use. YouTube recommends testing before an event with similar movement and audio, and monitoring stream health and messages. Use a private or unlisted test where appropriate, and check the stream as a viewer as well as in OBS. A local preview alone does not show you every issue in the outgoing stream.
Include a section with motion, not only a title card. Watch for uneven movement, repeated-looking frames, dropped frames, audio that drifts out of sync, or warnings in YouTube’s stream health. If the content is a bhajan recording, listen through a representative passage; if it is a news loop, inspect the ticker and any scene changes. A short, deliberate test gives you more useful evidence than leaving the setting untouched because the picture appeared still at the start.
If the result is poor, change one variable at a time. First confirm that OBS is using the intended profile and source. Then test the source-rate match against a reasonable alternative, such as 30 fps where appropriate. Record what changed and what you observed. If you lower FPS and the rendering load improves but YouTube reports a connection issue, investigate upload capacity and bitrate separately.
For a 24/7 channel, a test should also resemble the conditions of a long run. Include the normal audio, transitions and any overlays. Keep an eye on the output after a restart or scene change if those happen in ordinary operation. A rate that looks acceptable in a brief static check may behave differently when the full scene is active, so base the decision on the real programme rather than a bare test pattern.
If the persistent burden is keeping the same computer on to play and send a fixed video, StreamNeo can remove that specific task: you upload the video and set the YouTube stream key, then the broadcast can run without your computer staying on. That addresses playback and ongoing operation, not the creative choice of frame rate; check the output with your actual material and current YouTube guidance.
For further context on a continuous ambience channel, see the practical YouTube Live encoder settings for a 24/7 rain sounds stream. Its subject is a different kind of programme, but the same discipline applies: settle the output settings, test the stream, and monitor the result rather than treating one number as a guarantee.
Check YouTube Live’s frame-rate limit
YouTube’s published live encoder settings say the frame rate can be up to 60 fps. OBS cannot make YouTube accept an output beyond that published limit, and a source that is lower than 60 fps does not need to be set to 60 to meet a special live-stream rule. Confirm the current official guidance before changing a live setup, since platform recommendations can be updated.
The rate also has to be considered alongside resolution, codec and bitrate. YouTube lists different recommended ingest bitrates for different combinations; selecting 60 rather than 30 fps can change the relevant guidance. Matching the video’s rate does not tell you whether your internet connection can sustain the chosen bitrate, just as a suitable bitrate does not establish that OBS can render every frame reliably.
YouTube’s encoder guidance also covers items such as keyframe interval and CBR encoding for RTMP/RTMPS. Treat those as separate encoder settings, not as reasons to change FPS. Check the official page for current requirements and recommendations, run a connection test, and inspect stream health during the trial broadcast. Neither matching the source nor selecting a listed bitrate promises approval, uninterrupted operation or a particular viewer experience.
If you are deciding between 30 and 60 fps, compare the source’s actual rate, visible motion, OBS performance and available upload capacity. For a 60 fps gaming video, 60 may preserve its intended cadence if the setup can sustain it. For a 25 fps sermon or a 30 fps lofi loop, matching the source is a more direct starting point. These are practical examples, not platform mandates.
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 FPS should OBS use for a prerecorded video?
Start with the video’s actual frame rate and choose that rate in Settings > Video > Common FPS Value if it is available and the system can run it reliably. Matching is a practical default for the source’s cadence, not a YouTube Live requirement. Test the result with representative motion and audio.
Should OBS be 30 or 60 fps for YouTube Live?
Choose based on the source and the system, not solely on the fact that YouTube Live supports up to 60 fps. A 60 fps source may suit 60 fps output if OBS and your connection can sustain it; OBS recommends trying 30 fps if 60 fps is not working. Lowering the output changes cadence relative to a 60 fps source, so test before deciding.
Does setting OBS to 60 fps make a 30 fps video smoother?
It does not add source detail that was not recorded. Output and source rates differ, so frames may be mapped to a different cadence, and the result depends on the material and playback path. Test visible movement rather than assuming a higher output number improves the video.
What if my playlist contains several frame rates?
Choose an output rate that best serves the dominant or most important clips, then test transitions between different rates. One fixed output cannot preserve every source’s original cadence in a mixed-rate playlist. Check the actual stream and adjust if the compromise is distracting or the system struggles.