OBS Recordings Too Large? Fix Settings Before Re-Encoding
Reduce oversized OBS recordings by checking recording quality, rate control and output settings. Learn what to change next time and how to handle existing files.
If every OBS recording is unexpectedly huge, check Settings → Output before re-encoding your whole library. A lossless preset or a very demanding quality setting can create far more data than you need for a tutorial or sharing copy.
Changing OBS settings affects future recordings. An existing large file needs a separate export, a shorter excerpt or a sharing method that can handle the original.
Check the recording preset, not just the stream bitrate
In Settings → Output, inspect the recording controls. If you use Simple output mode, look at Recording Quality. OBS distinguishes High Quality, Indistinguishable, Lossless and Same as stream. Its preset guide describes increasingly large files as quality rises; Lossless is intended for a very different storage budget from routine sharing.
For a normal tutorial or meeting recording, start a short comparison with High Quality. Keep a higher-quality source if editing requires it, but choose that deliberately. Do not select Lossless simply because you do not want the text to look bad.
If you need a separate local recording, check its own encoder settings. Changing the streaming bitrate will not change an independently configured recording. Same as stream is the exception: that mode uses the stream’s encoding settings.
In Advanced mode, identify the control before changing a number
OBS’s advanced recording guide uses quality-based controls such as CQP for NVENC and CRF for x264. In those modes, lower quality-number values mean higher quality and generally larger files. Increasing the number slightly can reduce size; decreasing it can make the original problem worse.
For example, if a CQP setting of 18 produces files you cannot manage, compare a short recording at 20 with everything else unchanged. This is a diagnostic experiment, not a universal recommended value. Quality numbers are not interchangeable between encoders, and a hardware generation can change the available options.
| What you see | What to inspect first |
|---|---|
| Lossless selected | Whether you actually need pixel-preserving recording |
| CQP / CRF with a low number | A slightly higher value, using the same scene for comparison |
| CBR with a high bitrate | Whether the fixed data rate is appropriate for the recording |
| A 4K / 60 fps output for a simple tutorial | Whether the delivery needs that resolution and frame rate |
Use a one-minute comparison before recording another hour
Keep your current configuration noted or saved in a separate OBS profile. Use the same source sequence for each comparison, with both a difficult motion section and any text the viewer must read. A quiet desktop is not a fair substitute for the game or scrolling interface you actually record.
- Record one minute with the current settings. Note the duration, file size, encoder, quality control, output resolution and frame rate.
- Change one setting, then record the same sequence for the same duration. In Simple mode, compare the preset; in Advanced mode, change only the relevant quality control.
- Compare small text, motion, microphone audio and synchronization. A smaller file with missing sound or choppy capture is not a successful result.
- Estimate storage from your measured sample, then leave room for more complex scenes. A hypothetical 80 MB per minute is about 4.8 GB per hour; a quality-based recording can vary substantially across the session.
Only reduce resolution or frame rate when the content allows it
Under Settings → Video, check Output (Scaled) Resolution and the frame-rate setting. For slides and a talking head, test whether 30 fps serves the purpose. For fast gameplay or a motion demonstration, keep the frame rate needed to show the action.
Judge screen recordings by the smallest important text. If reducing output resolution makes menus unreadable, restore it and try a gentler quality adjustment. Recording a smaller application area at readable text size can be more useful than capturing an entire high-resolution desktop and shrinking everything later.
For an existing large recording, work from the source
If only a highlight is needed, export that section first. For a supported source under 500 MB, the video compressor can create a smaller sharing copy. Long OBS sessions often exceed that limit; use a desktop encoder for those, or share the original through storage that accommodates it.
If your recording has separate microphone and desktop-audio tracks, verify which tracks reach the exported file. The browser compressor processes primary tracks, so it is not the right workflow for preserving a multitrack editing master.
OBS’s File → Remux Recordings can move a recording into another container for compatibility. Remuxing is not the same as re-encoding: it will not normally produce the large size reduction you want. The OBS recording-output guide explains that workflow. Keep the source until you have checked the complete exported duration, sound and difficult scenes.