How do I fix choppy OBS gameplay recordings?

The steps at a glance

Choppy footage has a handful of causes, and each has its own fix. Changing settings at random burns recording sessions, so work through it in this order:

1. Make sure the file stutters, not your player or editor.
2. Record a one minute test with movement.
3. Read the OBS Stats window.
4. Fix rendering lag: give the GPU room.
5. Fix encoding lag: lighten the encoder’s load.
6. Match the game’s frame rate to the recording.
7. Convert variable frame rate footage before editing.
8. Check the test file, then record the session.

Step 1: Make sure the file stutters, not your player or editor

Choppy playback inside an editing timeline is often the computer struggling to decode a heavy file, not a fault in the recording. Before touching any OBS setting, play the recording itself in an ordinary video player. If it runs smoothly there, the file is fine and the editing machine needs lighter preview files, usually called proxies.

To test the file instead of trusting your eyes, open it in the free dropped frames checker. It reads the timestamp of every frame and compares each frame with the one before it, all inside your browser, and tells apart four kinds of choppiness:

With OBS, the first kind is the common one. OBS holds a constant frame rate, and when it falls behind it sends the previous frame again to keep the timing, as the checker’s page explains from the OBS source code. So OBS stutter tends to show up as repeated frames rather than holes in the file.

Step 2: Record a one minute test with movement

Use the same game, scene and settings you record with for real, and play the part that moves most: a fight, a sprint across the map, a quick spin of the camera. A menu or loading screen proves nothing, because a still picture repeated looks exactly like a still picture.

Record the test to MKV and remux it if you need MP4. OBS’s Standard Recording Output Guide recommends MKV because a recording that doesn’t stop cleanly won’t corrupt the whole file, and File > Remux Recordings turns it into an MP4 afterwards.

Step 3: Read the OBS Stats window

While the test records, open View > Stats. Three lines in that window tell you where to look:

OBS’s Stream Connection Troubleshooting guide puts dropped frames while streaming down to a network issue between your computer and the ingest server, so that line says nothing about a local recording. If the first two counters stay at zero and the file still repeats frames, the most likely cause is the game itself: Step 6.

Step 4: Fix rendering lag: give the GPU room

OBS’s Encoding Performance Troubleshooting guide explains that OBS needs GPU time to composite and render every scene, so a game that takes the whole graphics card leaves OBS short. Its fixes, in the guide’s own order:

1. Run OBS as administrator (Windows only). The guide treats this as the quick fix, because it lets Windows set aside part of the graphics card for OBS.
2. Quit anything else working the graphics card, a second game included. Task Manager on Windows or Activity Monitor on macOS shows which programs those are; only close the ones you know.
3. Limit the game to your monitor’s refresh rate or switch on V-Sync. Still not enough? Limit it to the frame rate OBS records at.
4. Turn the game’s graphics down. If the game and OBS can’t both hold a steady frame rate, the computer can’t run maximum settings and OBS at once.
5. Untick Multi-adapter Compatibility in the Game Capture source, unless you run linked graphics cards or a laptop with more than one GPU.
6. Switch off Game DVR in Windows. The guide says Game Mode is fine to leave on from Windows 10 version 1809.
7. Lower the output settings in Settings > Video (more in Step 5).
8. Simplify your scenes: fewer heavy sources and filters, and no browser or media source stretched over the whole canvas with empty space in it.

Change one thing, record another minute, and check again. If you change five settings at once, you won’t know which one mattered.

Step 5: Fix encoding lag: lighten the encoder’s load

When the encoder is the bottleneck, give it fewer pixels or fewer frames. In Settings > Video, lower the output resolution or the frame rate; the OBS guide’s own suggestion is to try 30 if 60 fps isn’t working. The warning text names the other lever: a faster encoding preset.

Look at the recording preset as well. OBS’s Recording Encoder Presets Guide says “Indistinguishable” can cost performance on older or weaker hardware, and that “Lossless” writes around 7 GB per minute and uses the CPU encoder. In Simple output mode, the Standard Recording Output Guide notes that any recording quality other than “Same as stream” takes extra resources, which matters when you stream and record at the same time.

Step 6: Match the game’s frame rate to the recording

If Stats shows no lag but the file repeats frames, the game ran slower than the recording. A 60 fps recording of a game running at 40 fps only gets 40 new pictures a second, so it fills the other 20 with copies: one frame in three repeats. Viewers feel that as judder on every camera turn, even when the game felt fine to play.

Cap the game at a frame rate it can hold through the busiest moments, and record at that rate, or at exactly half of it. If the game can’t hold 60 with OBS running, a steady 30 fps recording often looks smoother than an uneven 60.

Step 7: Convert variable frame rate footage before editing

OBS records at a constant frame rate, but many phone and screen recordings don’t. An Adobe employee’s FAQ for Premiere Pro (read October 19, 2026) says variable frame rate media can play with the audio out of sync with the picture, and recommends converting it to a constant frame rate before editing.

To find out whether a file is variable: in Premiere Pro 12.0.1 or later, right-click it and open Properties, which shows “Variable Frame Rate Detected”; or open it in the free MediaInfo, where Frame Rate Mode reads Variable. For the conversion, the FAQ prefers Shutter Encoder for difficult files and says HandBrake also works, with fewer features.

Step 8: Check the test file, then record the session

Run the test through the dropped frames checker once more. Next to the frame rate written in the file, it reports the effective frame rate (how many new pictures a viewer really gets while the game moves), whether the file is constant or variable frame rate, and a timeline of where any stutter sits. Its bar for a clean file: fewer than 0.5% of moving frames repeated, no freeze of 0.1 seconds or more, and no gaps in the timestamps. Those thresholds are the tool’s own, not OBS’s. Only when the test passes, record the long session with exactly the same settings.

The rest of a setup an editor can work with (separate audio tracks, a separate facecam, untouched files) is in how to record gameplay for your editor, and the recording settings table is in best OBS settings to record gameplay.

Can a recording that already stutters be fixed?

Partly. A single short freeze can be cut around or covered with a facecam shot, a reaction, a zoom or a piece of B-roll. Frame interpolation can invent in-between frames, but it is a guess, so check every interpolated shot closely. What no editor can do is bring back a frame that was never recorded. A whole session where the game ran below the recording frame rate judders on every turn, and cutting doesn’t hide that. When the stutter runs through the entire video, recording again after a clean one minute test is usually faster than fighting it.

How I check client footage for stutter

When I edit long-form Roblox and Minecraft videos, I look at the raw recordings before any cutting starts. One short freeze is a small problem: it can hide behind a cut. Uneven frames across a whole session are not, because no edit puts back pictures that were never captured, and a game that ran slower than the recording judders through every turn however well it is cut.

That is why a one minute test is worth recording before any long session, and worth checking before anything else gets recorded. If it comes back clean, the same OBS settings carry over to the real thing. I built the dropped frames checker so a creator can run that check alone, with nothing uploaded. For how the edit itself is built from footage like this, see how to edit gaming videos for YouTube.

Common mistakes when fixing choppy recordings

• Testing on a menu or a still scene. Stutter only shows while the picture moves.
• Reading Dropped Frames (Network) for a recording. That counter is about streaming.
• Leaving the game’s frame rate uncapped. The game takes the GPU time OBS needs.
• Changing several settings at once. The next test can’t tell you which change worked.
• Re-encoding or trimming the OBS file before sending it. It adds a generation of compression and can cut context the editor needed.
• Editing variable frame rate footage as it is. Convert it first, or the audio can drift away from the picture.

Choppy OBS recordings FAQ

Why is my OBS recording choppy when the game felt smooth?

Because playing and recording are two different loads. The game can run fine on screen while OBS misses frames rendering the scene or encoding it, and the Stats window shows which of the two. If both counters stay at zero but the file repeats frames, the game ran slower than the recording frame rate, which is easy to miss while playing.

What does “Encoding overloaded” mean in OBS?

It means the encoder can’t compress frames as fast as they arrive, so OBS skips some and counts them as skipped frames due to encoding lag. The warning itself suggests turning down video settings or using a faster encoding preset; lowering the output resolution or going from 60 to 30 fps also lightens the load.

Does Dropped Frames (Network) affect my recording?

No. That line counts frames lost on the way to a streaming server, and OBS’s stream troubleshooting guide puts it down to a network problem between your computer and the ingest server. For a local recording, look at the rendering lag and encoding lag counters instead.

Should I record gameplay at 30 or 60 fps?

Record at the highest frame rate your computer holds steadily with the game and OBS running together. A 60 fps file of a game stuck at 40 repeats one frame in three. OBS’s own troubleshooting guide suggests dropping to 30 if 60 fps is not working.

Can a choppy recording be fixed in editing?

Only in part. A short freeze can be hidden with a cut, a facecam shot or B-roll, but frames that were never recorded can’t be brought back. If the whole session stutters, find the cause with a one minute test and record again.

How do I know if my video has a variable frame rate?

Open it in MediaInfo and look at Frame Rate Mode, or right-click it in Premiere Pro and open Properties, which flags variable frame rate. OBS records at a constant frame rate; phone and screen recordings often don’t. Before editing, turn it into constant frame rate footage; Shutter Encoder and HandBrake both do this.

Sources

Why OBS needs the GPU, the fixes and their order, and the 30 fps suggestion: OBS knowledge base, Encoding Performance Troubleshooting, read October 19, 2026. MKV and Remux Recordings, and the “Same as stream” note: Standard Recording Output Guide, read October 19, 2026. The Indistinguishable and Lossless presets: Recording Encoder Presets Guide, read October 19, 2026. Dropped frames while streaming: Stream Connection Troubleshooting, read October 19, 2026. The exact Stats labels and the “Encoding overloaded” warning: OBS Studio source on GitHub, frontend/data/locale/en-US.ini, and Stats in the View menu: frontend/forms/OBSBasic.ui, read October 19, 2026. Variable frame rate in Premiere Pro, how to detect it and the conversion tools: Adobe Community, FAQ: How to work with Variable Frame Rate (VFR) media in Premiere Pro, written by an Adobe employee, read October 19, 2026. How the checker works, its clean rule and how OBS repeats the last frame: the dropped frames checker page. The 40 in 60 fps example is arithmetic.