Recording emulator gameplay sounds simple until you try it. You start OBS, press record, and the game that was smooth a moment ago turns choppy, the recording itself stutters, or the audio drifts out of sync. The reason is straightforward: recording adds a second demanding job, video encoding, on top of two already demanding jobs, running Windows and running the emulator. On a mid-range or low-spec PC, those three jobs compete for the same CPU, GPU, and disk bandwidth, and something has to give. This guide shows how to set up OBS for emulator recording so that the game stays playable and the recording stays watchable, with specific settings for weaker hardware and clear explanations of why each setting matters.
Understand Where the Cost Comes From
OBS recording costs resources in three places. Capture costs a little, as OBS reads frames from the emulator window. Encoding costs a lot, as OBS compresses those frames into a video file in real time. Writing the file costs disk bandwidth, especially at high bitrates or on a slow drive. The encoder choice determines which hardware bears the encoding cost. A software encoder, x264, uses the CPU, which is already busy running the emulator, so it is the most likely to cause frame drops on a low-spec PC. A hardware encoder, such as NVENC on Nvidia graphics, AMF on AMD graphics, or Quick Sync on Intel graphics, uses dedicated encoding hardware on the GPU, leaving the CPU freer for the emulator. If your PC has a hardware encoder available, use it for emulator recording. That single choice is the highest-impact decision in this entire guide.
The second major cost is resolution and frame rate. Recording at 1920 by 1080 and 60 frames per second requires roughly twice the encoding work of 1280 by 720 at 30 frames per second, and the difference is even larger if the emulator itself is also rendering at 1080p. For most emulator recordings, especially for sharing gameplay clips rather than producing professional videos, 720p at 30 frames per second looks good, uploads quickly, and keeps the game playable. Start there, and only raise resolution or frame rate if your PC proves it can handle more without dropping frames in either the game or the recording.
Set Up the Emulator for Recording First
Before opening OBS, configure the emulator for a recording-friendly session. Set the emulator resolution to match your intended recording resolution, ideally 1280 by 720, so OBS does not need to scale frames up or down, which adds work. Cap the emulator frame rate at 30 or 60 to match your recording frame rate, because a mismatch forces OBS to drop or duplicate frames. Close the browser and other heavy apps, as you would for normal low-spec gaming, because recording leaves even less headroom. Disable any emulator overlays, performance meters, or debug displays you do not want in the recording, and hide the Windows taskbar or desktop elements that might appear if you capture the wrong source. Test the game alone for a few minutes at these settings to confirm it is smooth before adding OBS to the mix. If the game already stutters without recording, recording will only make it worse, and you need to lower emulator settings first.
OBS Settings That Keep FPS Stable
Open OBS, go to Settings, Output, and set Output Mode to Simple if you are new to OBS, or Advanced if you want finer control. In Simple mode, set Video Bitrate to around 4500 to 6000 kilobits per second for 720p recording, set Encoder to Hardware if available, and set Recording Format to MP4 or MKV. MKV is safer if OBS crashes, because an interrupted MP4 can become unplayable, while an interrupted MKV usually remains recoverable, and OBS can remux MKV to MP4 afterwards from File, Remux Recordings. Set Recording Path to a drive with plenty of free space, preferably a different drive from the one Windows and the emulator run on, if you have one, because writing video to the same drive the emulator reads from creates disk contention.
In Advanced mode, you gain control over the encoder preset, which is where low-spec tuning lives. For NVENC, choose the Performance or Quality preset rather than Max Quality, because Max Quality costs more GPU time for a small visual gain. For x264, if you must use software encoding, choose Veryfast or Superfast, never Medium or Slow, because slower x264 presets produce better quality per bit but consume far more CPU, which is exactly what a low-spec emulator PC cannot spare. Set Rate Control to CBR for consistent quality, set Keyframe Interval to 2 seconds, and set Profile to High. These values are standard for gameplay recording and keep the encoder’s behaviour predictable.
Next, go to Settings, Video, and set Base Canvas Resolution and Output Resolution both to 1280 by 720, and Common FPS Values to 30. Matching base and output resolutions avoids a scaling step. If your monitor is 1080p and the emulator window is smaller, base canvas at 720p still works, because OBS will capture and scale the emulator source to the canvas, but setting the emulator itself to 720p, as above, keeps everything aligned. Go to Settings, Audio, and set Sample Rate to 48 kilohertz, which matches most video platforms and avoids resampling.
Capture Method: Window Capture Beats Display Capture
In OBS Sources, add a Window Capture source and select the emulator window, rather than using Display Capture for the whole screen. Window Capture is more efficient, because OBS only processes the emulator window, and it is cleaner, because notifications, taskbar popups, and other windows will not appear in the recording if you switch applications briefly. If Window Capture shows a black screen, which happens with some emulators and graphics configurations, try Game Capture as an alternative, and if that also fails, try Window Capture with the compatibility or capture method options toggled in the source properties. Display Capture is a last resort, not a first choice, because it captures everything, costs more, and leaks private notifications into your video.
Position the emulator window so it is fully visible and not overlapped by OBS itself while recording. OBS does not need to be visible to record, and minimising OBS during recording is fine. Keep OBS’s own preview at a reasonable size, or disable preview if you need every bit of GPU headroom, because preview rendering itself costs a little performance. Watch OBS’s status bar at the bottom while recording: it shows dropped frames, encoding lag, and rendering lag. A small number of dropped frames at the start is normal, but a steadily rising count means your settings are too demanding, and you should lower resolution, bitrate, or encoder quality.
Audio Without Echoes or Drift
Audio problems ruin recordings that otherwise look good. If you want game audio only, add no microphone source, and make sure OBS captures desktop audio from the emulator. If you want commentary, add a microphone source, wear headphones so game audio does not leak from speakers into the microphone and create an echo, and test levels before recording a long session. Speak at normal volume and check that the microphone meter in OBS moves without hitting the red. If audio drifts out of sync over a long recording, the cause is usually a mismatched sample rate or an overloaded system dropping audio frames. Setting audio to 48 kilohertz throughout, and reducing encoder load, usually resolves drift. Keep recordings under an hour per file where possible, both for sync reliability and for easier editing and uploading.
Test, Then Record for Real
Never start a long recording session without a test clip. Record sixty seconds of real gameplay, with the same game, settings, and OBS configuration you plan to use, then watch the clip back in full. Check three things: is the game smooth in the recording, is the audio in sync and clear, and does the file play correctly in a media player and after uploading? Also check OBS’s stats during the test for dropped frames. If the test clip is good, your real session will be good. If the test clip stutters, lower one setting at a time, resolution first, then frame rate, then encoder preset, and re-test. Changing three settings at once makes it impossible to know which change helped, and you may end up with lower quality than necessary.
Recommended Starting Settings Table
| Setting | Low-spec PC | Mid-range PC |
|---|---|---|
| Recording resolution | 1280 by 720 | 1920 by 1080 or 1280 by 720 |
| Recording frame rate | 30 FPS | 30 or 60 FPS |
| Encoder | Hardware (NVENC, AMF, Quick Sync) if available | Hardware, or x264 Veryfast |
| Bitrate (720p) | 4500 to 6000 kbps | 6000 to 8000 kbps |
| Capture source | Window Capture | Window Capture |
| Recording format | MKV, remux to MP4 after | MKV or MP4 |
| Emulator resolution | 1280 by 720 to match | Match recording resolution |
FAQ
Why does OBS make my emulator lag when the game was smooth before?
Because recording adds real-time video encoding on top of running Windows and the emulator. Use a hardware encoder, record at 720p and 30 FPS, and close other heavy apps to reduce competition for CPU and GPU.
Should I use x264 or a hardware encoder for emulator recording?
Use a hardware encoder (NVENC, AMF, or Quick Sync) if available, as it uses dedicated GPU hardware and leaves the CPU for the emulator. Use x264 only with Veryfast or Superfast presets if no hardware encoder exists.
Why is Window Capture better than Display Capture for emulators?
Window Capture only processes the emulator window, costs less performance, and keeps notifications and other windows out of the recording. Display Capture captures everything and costs more.
My recording stutters but the game felt smooth while playing. What is wrong?
OBS is likely dropping frames due to encoder overload. Lower recording resolution, frame rate, or encoder quality, and check OBS’s status bar for encoding and rendering lag during a test clip.
Should I record to MP4 or MKV in OBS?
MKV is safer during recording, because an interrupted MP4 can become unplayable, while MKV usually remains recoverable. OBS can remux MKV to MP4 afterwards from File, Remux Recordings.
This guide does not host, link to, or distribute copyrighted ROMs, ISOs or BIOS files. It describes legal emulator configuration only, and readers should obtain Android apps and games only from official sources such as the Google Play Store or the emulator developer’s official site.


