To limit the frame rate OBS sends to YouTube, open Settings > Video and choose a value under Common FPS Value. This is the overall output frame rate; it is not a separate frame-rate cap for a pre-recorded file added as a Media Source.
Choose an output rate that suits the motion in your video and the capacity of the computer doing the rendering and encoding. If 60 fps is not working well, OBS recommends trying 30 fps; that reduces the amount of frame work, though it does not guarantee that every performance issue will disappear.
Choose the outgoing OBS frame rate
A frame rate is the number of frames presented each second. In this case, the setting to focus on is OBS's output: the stream OBS constructs and sends, rather than a property that changes the video file on disk. The OBS Studio overview identifies Common FPS Value as the place to set the desired output frame rate. See the OBS Studio overview for the setting in context.
For a pre-recorded stream, the file supplies the pictures and sound, while OBS manages the scene and outgoing broadcast. The right output choice depends on what the footage looks like and whether your setup can render and encode that output reliably. A music loop with a mostly still devotional image may not gain much from a higher output rate. A clip with quicker movement may make the difference more visible, but a higher setting also asks more of the system.
Do not treat a frame-rate value as a universal YouTube requirement. This article explains the OBS control; it does not establish a current YouTube maximum or preferred value. If you need an exact platform requirement for your channel, consult YouTube's current live encoder settings guidance rather than relying on an old preset or a rule copied from another workflow.
Before changing a setting, decide what you are trying to improve. If the picture looks juddery, investigate whether the footage and output choices are suitable. If OBS reports rendering or encoding trouble, reducing the output rate may help reduce work. If the broadcast is already stable and the footage is mostly static, changing settings just to choose the larger number may add load without a visible benefit.
Set Common FPS Value
In OBS, open Settings, select Video, and find Common FPS Value. Choose the intended output value there, such as 30 or 60 fps, then apply the setting. The wording and location may vary slightly between versions, so use the Video page rather than looking for an FPS option inside the file's playback properties.
Make one deliberate change at a time. If you currently use 60 fps and want to test 30, change Common FPS Value, apply it, then observe the same scene or video under comparable conditions. This makes it easier to tell whether the change helped. If you simultaneously alter resolution, encoder settings, scene effects and the file, you will have a harder time identifying which change mattered.
The Common FPS Value choice is not a promise that every input will have that many unique frames available. OBS uses an output configuration for the stream; source material and playback may have their own timing and characteristics. The setting describes the intended output rate, not a conversion that improves the original recording or adds genuine detail that was not in it.
For channels that alternate between a static devotional artwork loop and recorded clips, keep a note of the configuration that works for each type of programme. OBS Profiles can retain output-related settings for reuse. The OBS Profiles guide explains how profiles help preserve configuration, including Video and Output settings. A profile is useful when you deliberately switch configurations; it does not itself improve performance.
Match the desired output FPS
The practical choice is usually between an output that is sufficient for the programme and one that asks the computer to process more frames. A pre-recorded file does not automatically mean that the outgoing stream should use a particular FPS. Consider the footage, what viewers need to see, and how OBS behaves during a sustained test.
| Choice | When it may fit | Trade-off to watch |
|---|---|---|
| 30 fps | A talking-head clip, slower footage, a music programme with artwork, or a setup struggling at 60 | Less frequent frame updates than 60; fast movement may look less smooth |
| 60 fps | Footage where smoother motion is important, when the source and setup support it | More rendering and encoding work; it may expose performance limits |
These are working choices, not rules about all channels. A 60 fps source sent through a 30 fps output is not made into a 60 fps broadcast by selecting a higher value elsewhere. Likewise, selecting 60 fps does not create extra real motion in a source that does not contain it. Judge the result on the actual programme, not only on a number in a menu.
You can also use the content itself to make the decision. For a quiet lofi station showing a still image, the value of extra motion updates may be limited. For a recorded dance performance, moving camera shot or sports clip, viewers may notice smoothness more. Neither example settles the encoding load question: you still need to test your own setup, especially if OBS is also scaling the picture, compositing multiple layers or applying effects.
If you are building a continuous programme from multiple clips, the playlist method and the outgoing frame rate are separate decisions. A guide to making an FFmpeg playlist for a nonstop Indian music channel is relevant if you are comparing a playlist-based workflow with playback through OBS. It does not change where OBS sets its own output FPS.
Understand the 60-fps performance trade-off
OBS notes that frame rate affects rendering and encoding performance: more frames mean more work to prepare and encode each second. The OBS encoding performance troubleshooting guide specifically cautions that 60-fps streaming can be more taxing than 30 fps and recommends trying 30 fps if 60 is not working for you.
That advice is a troubleshooting step, not a claim that 30 fps is always best. A setup with enough capacity may handle 60 fps for a suitable source, while another may struggle. Results depend on the complete workload, including resolution, scenes, filters, encoder choice and other tasks happening on the computer. Do not infer that the same frame-rate setting will behave equally well on every machine.
For an always-on channel, a brief preview is not the whole test. Let the intended scene and file run long enough to see whether OBS remains stable under the ordinary workload. Watch OBS's performance indicators and the stream's output, and note when the problem appears. A slowdown during scene changes or after a long run points to a different investigation than a problem that begins as soon as the stream starts.
Lowering output resolution is another potential way to reduce GPU resources, according to OBS's troubleshooting guidance. It is a separate trade-off: resolution affects picture dimensions and detail, while frame rate concerns how often frames are output. If you change both at once, compare carefully so you know which adjustment mattered. Start with the setting that matches the symptom and content rather than lowering every value by habit.
A stable, modest output can be more useful than a nominally smoother setting that causes missed or delayed frames. At the same time, a lower FPS will not repair unrelated causes such as a weak network connection, a problematic file, or an encoder configuration problem. Use the observed symptom to guide the next test, and consult OBS's current troubleshooting advice when its indicators point to rendering or encoding overload.
Try 30 fps if needed
If you selected 60 fps and OBS is struggling, test 30 fps through Settings > Video > Common FPS Value. OBS's own performance guide gives this as the practical fallback to try. The reason is straightforward: outputting fewer frames reduces the rendering and encoding work compared with processing more frames each second.
After changing the value, replay a representative part of the programme. Check for improvement in OBS's performance indicators and look at the stream output, not only the local preview. If the broadcast is still struggling, keep diagnosing rather than assuming the FPS change failed or that a more powerful computer is the only answer. Resolution, encoder settings, scene complexity and network conditions can each be relevant to different symptoms.
A useful test record is simple: note the output FPS, resolution, which scene and file were active, and the symptom you observed. Compare the same portion of the programme after each single change. This is especially helpful for a channel that runs overnight; a short daytime test may not reproduce the same combination of playback, scheduled tasks and scenes.
If 30 fps looks acceptable and the stream runs more smoothly, it may be a sensible operating choice for that programme. If motion becomes noticeably less smooth and OBS was not actually overloaded, you can reconsider 60 fps after checking the other parts of the setup. The point is to choose based on visible output and sustained behaviour, not to assume that either number is universally correct.
Where problems continue at 30 fps, lowering output resolution is a separate option identified by OBS for reducing GPU resource use. Make that change only if the resulting picture remains fit for your viewers. For a Telugu clip playlist, for example, the playlist's construction is another independent part of the workflow; the FFmpeg settings guide for a 24/7 Telugu video playlist covers a different approach to sending recorded material and should not be read as a control for OBS's Common FPS Value.
Separate stream FPS from Media Source controls
A local pre-recorded video is commonly added to OBS as a Media Source. OBS's Media Sources documentation describes playback properties such as looping, restart behaviour, decoding and playback speed. It does not document a separate source FPS cap. That distinction matters: change Common FPS Value when you intend to change the overall OBS output rate, and use Media Source options for playback behaviour they actually control. See the OBS Media Sources guide.
Playback speed and frame rate are not interchangeable controls. If a clip plays too quickly or slowly, playback speed may be the relevant property to inspect; changing output FPS is not a substitute for setting playback speed. Conversely, if the clip plays at the expected pace but the outgoing stream is configured for a different frame rate, Common FPS Value is the documented output control. Keep the diagnosis aligned with the symptom.
Looping a Media Source can make a file repeat, and restart behaviour can determine what happens when playback is activated again. Those settings help manage the source but do not create an independent stream FPS limiter. When a clip is part of a larger rotation, consider whether a playlist or multiple sources are more appropriate. A guide to streaming an FFmpeg playlist with a looping background video may help with that workflow question, while OBS output rate remains a separate setting.
The output setting also does not rewrite the original file. Keep a copy of the source unchanged if you need to preserve its original format, and treat OBS's Video configuration as the broadcast output choice. If the result differs from what you expect, check the source's playback behaviour, the selected scene and the output configuration independently. This avoids searching through Media Source properties for a control that the documentation does not describe as an FPS cap.
For a channel that must run when the operator's computer is off, the operating arrangement is a different concern from OBS's frame-rate setting. StreamNeo addresses the specific burden of keeping a local computer running for an uploaded video broadcast: it runs the file as a YouTube live stream, monitored and restarted automatically if it drops. This is relevant when the friction is leaving a computer on, not as a way to change Common FPS Value or a guarantee about YouTube acceptance.
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
How do I limit OBS stream FPS?
Open Settings > Video and choose the intended value under Common FPS Value. That setting controls OBS's overall output frame rate, rather than a separate cap for a local Media Source.
Where is Common FPS Value in OBS?
It is on the Video page inside OBS Settings. Choose the output value there, apply the change and test the stream with the intended scene and source.
Does OBS Media Source have its own frame rate setting?
The OBS Media Sources guide documents playback properties such as looping, restart behaviour, decoding and playback speed, but not an independent FPS cap. Use Common FPS Value to set the overall output rate.
Should I choose 30 or 60 fps?
Choose according to the motion you want viewers to see and the capacity available for rendering and encoding. OBS advises trying 30 fps if 60 fps is not working well; it is a troubleshooting option, not a guarantee that 30 fps is right for every programme or setup.