A low-end PC does not mean a bad recording. It means you have a smaller budget of processing power, and every setting in OBS spends some of it. On a stronger computer, 1080p at 60 frames per second with a demanding encoder may run without complaint. On a modest machine, the same settings can cause stuttering, dropped frames, or the familiar encoding overload warning. The aim of this guide is not to find a magic preset, but to help you spend that budget wisely: lower the settings that cost the most and matter least for your content, and protect the ones that matter most, such as clear audio and readable text.
There is no single definition of a low-end PC, and this guide does not set one. What matters is how your own computer behaves while OBS is running. If recordings stutter, if the fan runs constantly, or if OBS shows overload warnings, your settings are asking for more than the machine can give comfortably. The fixes below are starting points to test, not promises of a particular frame rate or quality. Results depend on your hardware, encoder, workload, and what else is running. If you have not installed OBS yet, start with the Windows download page, and for the general recording choices behind these settings, see our best OBS recording settings guide.
What slows OBS down on a modest computer
OBS work falls into three main jobs: capturing the screen or game, composing the scene from your sources, and encoding the result into a video file. Each job uses processor or graphics power, and on a modest computer they compete with the very program you are recording. A game, a browser with many tabs, or a video call can already use most of the available power before OBS starts. That is why closing unnecessary programs before recording often helps more than changing one OBS setting.
The heaviest costs are usually resolution, frame rate, and the encoder preset. A larger frame has more pixels to capture, scale, and encode, and a higher frame rate repeats that work more times each second. A slow encoder preset asks the processor to work harder on every frame to squeeze out extra quality. Browser sources, animated overlays, and several video filters add smaller costs that add up. When you troubleshoot, think in that order: resolution and frame rate first, encoder second, and sources and filters third. Changing one thing at a time makes it clear which change actually helped.
Resolution: the biggest saving you can make
Lowering the output resolution is usually the single most effective change on a low-end PC. Recording at 1280 by 720, or 720p, instead of 1920 by 1080 cuts the number of pixels in each frame by more than half, which reduces the work for capture, scaling, and encoding all at once. The picture will be softer, especially on a large screen, but for spoken tutorials, presentations, and simple desktop work it is often clear enough, and viewers are far more likely to notice stuttering than a modest drop in sharpness.
Set the base resolution to match your screen if you can, then set the output resolution to 720p in Settings, then Video. Use the Bilinear downscale filter, because it is lighter than Lanczos and the difference is hard to see at this size. If 720p still stutters, try 960 by 540 as a further step down for a test, and compare the result. Keep the resolution that stays smooth for a full test recording, not just the first ten seconds. If you later move to a stronger computer, raising the resolution again is a one-minute change, so you are not locking yourself in.
Choosing an encoder on limited hardware
On a modest computer, the encoder choice matters because the software encoder, x264, runs on the same processor as the program you are recording. If that processor is already busy, x264 on anything slower than the veryfast or ultrafast preset can overload it quickly. A hardware encoder, if your graphics card offers one, moves encoding to a dedicated part of the graphics card and leaves the processor freer. That is often the better starting point on a low-end PC, even if the picture needs a slightly higher bitrate for the same visible quality.
Open Settings, then Output, and look at the encoders listed. If you have a hardware option, choose it and set its preset to Performance or a similarly light option. If only x264 is available, choose the ultrafast or superfast preset and accept that you may need a higher bitrate to keep text readable. Do not use a slow or medium x264 preset on a weak processor in the hope of better quality: the extra quality is lost if frames are dropped. Test with a one-minute recording that includes your usual activity, and watch for the encoding overload message in the status bar.
Frame rate and downscaling
Frame rate is the second big lever. Thirty frames per second is enough for tutorials, presentations, talking-head videos, and most desktop work, and it halves the encoding work compared with 60 frames per second. On a low-end PC, 30 frames per second should be your default, and 60 should be treated as an experiment, not a starting point. Even for games, a smooth 30 frames per second recording is usually more watchable than a 60 frames per second recording that stutters every few seconds.
Downscaling is already covered in the resolution section, but the filter choice deserves a note. Bilinear is the lightest downscale filter and a sensible default on modest hardware. Lanczos can look slightly sharper on text, but it costs extra processing power that a low-end PC may not have to spare. If you record at the same resolution as your screen, no downscaling happens at all, so the filter does not matter. Test at 30 frames per second first, and only try 60 after a full test recording at 30 has stayed smooth, with no overload warnings and no dropped frames.
Scenes, sources and browser sources
Every source in a scene adds work, even when it is small or hidden behind another source. A display capture, a webcam, an image, a text label, and a browser source each need to be drawn every frame. On a strong computer that cost is easy to ignore; on a modest one it adds up. Keep your scenes simple: use one capture source per scene where possible, remove sources you are not using, and avoid stacking several browser sources with animation, video, or live widgets in the same scene.
Browser sources deserve special care because each one runs a web page in the background, which can use processor and memory even when the page looks still. If you use an overlay or alert widget through a browser source, keep it to one per scene and close the source when you do not need it. The same applies to animated backgrounds and large image files: a still image is far cheaper than a looping video. If you need overlays, our guide to overlays and scenes in OBS explains how to build them without overloading a scene. Also close browser tabs, chat apps, and other programs you do not need while recording.
Audio and filters on a weak processor
Audio is cheap compared with video encoding, so do not sacrifice it to save power. Set the sample rate to 48 kilohertz and the channels to stereo, choose the correct desktop and microphone devices, and balance the levels in the Audio Mixer. A clear voice matters more than a small increase in video sharpness, and listeners will forgive a 720p picture far sooner than a quiet or distorted microphone. Record a short test and listen with headphones before a long session.
Filters are the part of audio that can cost processor time. Noise suppression, noise gates, compressors, and limiters each add a little work, and several filters on several sources add up. On a low-end PC, use only the filters you actually need. If your room is quiet, you may not need noise suppression at all. If you do need it, try the lighter suppression option first and add one filter at a time, testing after each addition. Our OBS audio settings guide explains each filter and when it is worth using. If audio starts to crackle or lag, remove a filter before you change video settings.
A step-by-step low-end setup
Follow these steps in order, and test after you finish. Do not change the numbers again until you have watched a full test recording, because a setting that looks fine for ten seconds can still overload during a longer session.
- Close unnecessary programs, browser tabs, and other recording software, then open OBS Studio.
- Go to Settings, then Video. Set the common frame rate to 30 and the output resolution to 1280 by 720, with the Bilinear downscale filter.
- Go to Settings, then Output. Set Output Mode to Advanced, choose a hardware encoder if available, otherwise x264 on the ultrafast preset, and set the recording format to MKV.
- Set the bitrate to about 4,500 to 6,000 kilobits per second for 720p, or use a quality-based setting such as CRF 23 to 25 if your encoder offers it.
- Go to Settings, then Audio. Set the sample rate to 48 kilohertz, choose the correct devices, and set the microphone level so it reaches the yellow area without staying in the red.
- Keep the scene simple: one capture source, one webcam if needed, and no more than one browser source.
- Record for two minutes doing your usual activity, watch it back at full screen, and check for stuttering, overload warnings, and audio problems before recording for real.
If that test stays smooth, you can try one improvement at a time, such as raising the bitrate slightly or trying 1080p, and test again. If it still stutters, lower the output resolution to 960 by 540 or remove the webcam for a test to find the cause. For gaming on a modest machine, also read our OBS settings for gaming guide, which covers game capture and encoder choices in more detail.
Common mistakes
The most common mistake on a low-end PC is copying settings from a tutorial made on a strong computer: 1080p at 60 frames per second, a slow x264 preset, and several browser sources. Those settings may work well for the person in the video, but they can overload a modest machine in minutes. Another mistake is changing five settings at once, so you never learn which one caused the problem. People also forget to close other programs, leave a game running at its highest graphics settings while recording, or record to a nearly full drive.
- Using 60 frames per second before testing 30 frames per second.
- Choosing a slow x264 preset on a processor that is already busy.
- Keeping unused sources and browser widgets in every scene.
- Recording straight to MP4 for long sessions, then losing the file if OBS closes.
- Ignoring the encoding overload warning and hoping it will go away on its own.
Troubleshooting
If OBS shows encoding overloaded, lower the output resolution to 720p, drop the frame rate to 30, and use a faster encoder preset or a hardware encoder. Close other programs and try again. If the video stutters but there is no warning, check whether the game or application is using most of the processor, and lower its own graphics settings. If the recording is blurry, raise the bitrate slightly or check that the output resolution is not lower than you intended.
If there is no sound, check the Audio Mixer meters, confirm the correct devices are selected in Settings, then Audio, and make sure the right tracks are enabled. If OBS itself is slow to open or the preview lags, remove browser sources and animated overlays for a test, and restart OBS. For repeated overload problems, see how to fix encoding overloaded in OBS and how to fix lag and dropped frames in OBS.
Frequently asked questions
Can OBS run on a low-end PC?
Yes, in many cases, if you use lighter settings: 720p resolution, 30 frames per second, a hardware encoder or a fast x264 preset, and simple scenes. Test with a short recording on your own computer, because results depend on your hardware and workload.
What resolution should I use on a low-end PC?
720p is a good starting point for most modest computers. It is far lighter than 1080p and usually clear enough for tutorials and desktop work. Try 1080p only after 720p has stayed smooth in a full test recording.
Should I use x264 or a hardware encoder on a weak PC?
A hardware encoder is often the better starting point, because it leaves the processor freer for the program you are recording. If only x264 is available, use the ultrafast or superfast preset and a moderate bitrate.
Why does OBS lag on my low-end PC?
Lag usually means the settings ask for more processing power than the computer can give: high resolution, high frame rate, a slow encoder preset, or too many sources and background programs. Lower one setting at a time and test again.
Does lowering the frame rate to 30 help?
Yes, it can help a lot. Thirty frames per second roughly halves the encoding work compared with 60, and it is smooth enough for tutorials, presentations, and most desktop work. Use it as your default on a modest computer.
Conclusion
A low-end PC can produce good OBS recordings if you respect its limits. Start at 720p and 30 frames per second, use the lightest encoder available, keep scenes simple, and protect your audio. Test with a short recording, change one setting at a time, and raise the quality only when a full test stays smooth. That careful approach will give you stable, usable videos without overload warnings, and it leaves you a clear path to improve the settings later if your hardware changes.