OBS Recording Laggy But Preview Looks Fine - Fix

There is a highly specific, uniquely frustrating paradox that many creators experience inside OBS Studio: You press record, run through your software tutorial or presentation, and keep a close eye on the OBS preview window on your second monitor. The preview looks perfectly fluid, rendering at a smooth 60 frames per second.

But when you click stop, navigate to your videos folder, and open the final .mp4 or .mkv file, the playback is a jagged, stuttering mess.

Why does OBS display a flawless visual image inside the app, but output a broken file to your hard drive?

This mismatch points to a clear division in how your computer handles video data. A smooth preview means your Graphics Processing Unit (GPU) has plenty of power to draw the pixels on your screen (Rendering). A laggy final file means your system is running out of processing memory when it tries to compress and save those pixels to your disk (Encoding).

Here is the definitive diagnostic blueprint to patch your data pipelines and fix choppy output files for good.

Step 1: Shift to a Hardware-Accelerated Video Encoder (The Direct Fix)

By default, OBS points its encoder at the software x264 profile, which runs on your main CPU. This is exactly why you see the symptom you do: your CPU has plenty of spare capacity to draw the live preview, but not enough to also compress millions of pixels to disk while other apps are open, so it overflows its frame budget and drops frames from the saved file only. Moving compression to your GPU's dedicated encode chip fixes it.

Open Settings > Output, switch Output Mode to Advanced, set the Video Encoder to your hardware engine (NVENC, AMD HW, QuickSync, or Apple VT), and drop the Preset from Max Quality to Quality. If you want the encoder settings explained end to end, the full walkthrough is here: OBS Encoder Lag: NVENC vs x264 Fix.

Step 2: Swap the Disk Writing Path Natively

If you have already switched to a hardware encoder but your final video file still skips or freezes every few seconds, your storage drive is experiencing a write bottleneck. If OBS is writing a high-bitrate video stream directly to an old, external mechanical hard drive or a slow cloud-synced folder (like OneDrive or iCloud), the drive cannot write the data blocks fast enough, causing dropped frames in the final file.

1. Go to OBS Settings > Output and click on the Recording tab.
2. Locate the Recording Path field.
3. Click Browse and change the destination directory to your computer's native internal Solid State Drive (SSD) typically your primary local C: drive folder.
4. Avoid recording directly to external USB flash drives, network-attached storage (NAS) boxes, or folders actively syncing to the cloud while you record.

Step 3: Match Recording Frame Rates to Display Refresh Rates

A massive cause of file-specific stuttering is frame rate desynchronization. If you are using a high-end monitor running at 144 Hz or 240 Hz, your preview screen may look perfectly smooth because your graphics card is rendering at hyper-speed. However, if OBS is configured to compress that data down to a standard 60 fps video file, the mathematical frames do not divide evenly, resulting in micro-stutters and frame skipping in the encoded file.

• The Fix: Go to the Video tab in OBS Settings. Ensure your Common FPS Values dropdown is locked to a stable 60 or 30.
• If you run a 144 Hz display, use your operating system display properties to drop your screen refresh rate down to a clean multiple like 120 Hz or 60 Hz while filming to ensure perfect frame division.

Step 4: Run OBS as an Administrator

Even when your preview looks clean, Windows can occasionally throttle OBS's encoding threads behind the scenes if a foreground application becomes exceptionally resource-intensive.

• The Fix: Close OBS Studio completely. Right-click the OBS desktop shortcut or executable launcher icon and select Run as administrator.
• Why it works: This activates a hardware scheduling flag inside the Windows graphics kernel. It commands the operating system to grant OBS's background recording pipeline high priority, ensuring that focused foreground apps never starve the video capture engine of essential graphics clock cycles.

Telemetry Health Matrix

To verify that your fixes are working in real time, open the Stats dock inside OBS Studio (View > Docks > Stats in the top menu bar). Run a test recording and check these three indicators:

A Recording That Matches Its Preview

The whole preview-looks-fine paradox comes from OBS splitting the work of drawing frames and saving them across different hardware, then letting the save stage fall behind. Managing that split is doable, but it is one more thing to watch on every take.

Cubix Capture never presents the gap in the first place: what it shows you is what lands in the file, smooth, on standard laptops, with automatic zoom and cursor smoothing already applied. For tutorials and walkthroughs, that means no test recordings just to confirm the output is not secretly choppy.

Related reading:

• OBS Recording Stuttering: Fix Choppy Video
• OBS Encoder Lag: NVENC vs x264 Fix
• OBS Lagging: How to Fix Recording and Streaming Lag