Android Emulator Settings: Boost FPS & Fix Lag (2026)

The settings that matter most in any Android emulator are, in order: hardware virtualization turned on, the emulator running on your dedicated GPU, a 1280×720 starting resolution, CPU cores and RAM sized to your PC (never all of it), a renderer that suits your driver, and a 30 or 60 fps cap. Fix those before anything else.

The default configuration of any emulator is a conservative guess: it is designed not to crash on the widest possible range of PCs, not to run games well on your PC. This guide is organized in the order that works:

1. Prepare Windows so the emulator can use your hardware at all.
2. Set the emulator according to your hardware tier.
3. Squeeze out extra FPS once the basics are right.
4. Diagnose what is left, with a symptom → cause → fix table for lag, stutter and freezes.

Option names differ slightly between emulators, but the logic is the same everywhere.

Quick Checklist (If You Only Have Five Minutes)

• Hardware virtualization (Intel VT-x or AMD-V) is enabled.
• Windows is on the High performance power plan and your laptop is plugged in.
• The emulator runs on your dedicated GPU, not the integrated one.
• Emulator resolution is 1280×720 to start, not your monitor's native resolution.
• CPU cores and RAM follow the tier table below, not "as much as possible."
• Frame rate is capped at 30 or 60, not unlimited.
• Browsers, cloud sync and overlays are closed while you play.

Each point is explained below, along with what to do when it is not enough.

Part 1: Prepare Windows First

No emulator setting can compensate for a PC that is blocking or throttling the emulator. Do these once and they stay done.

Enable hardware virtualization

This is the single most important requirement. Modern emulators run an x86 build of Android inside a lightweight virtual machine, and that only runs at near-native speed when the CPU's virtualization extensions are turned on. Google's Android Emulator acceleration documentation lists Intel VT-x or AMD-V as a requirement for VM acceleration. With them disabled, the emulator either refuses to start or falls back to a far slower mode.

To check, open Task Manager (Ctrl + Shift + Esc) → Performance → CPU and look for "Virtualization: Enabled." If it says Disabled, you need to turn on Intel VT-x / Intel Virtualization Technology or AMD-V / SVM Mode in your BIOS/UEFI; Microsoft's enable virtualization on Windows page explains how to reach the UEFI settings from Windows. Our step-by-step guide on how to enable virtualization on Windows covers every major motherboard brand and the Windows features (Hyper-V, Windows Hypervisor Platform) that can conflict with it.

Use the High performance power plan

The Balanced power plan lowers CPU and GPU clocks whenever the load looks light, and an emulator's render loop can look light for a split second, which is enough to cause frame-time spikes.

1. Press Win + R, type powercfg.cpl and press Enter.
2. Select High performance (click "Show additional plans" if it is hidden).
3. On laptops, plug in the charger. Running on battery throttles the CPU and GPU no matter what else you set.

On NVIDIA cards you can also set NVIDIA Control Panel → Manage 3D settings → Power management mode → Prefer maximum performance. On AMD, disable Radeon Chill in AMD Software for the emulator.

Force the dedicated GPU

Laptops with both integrated and dedicated graphics often run new apps on the integrated chip to save power. Go to Settings → System → Display → Graphics, add the emulator's executable, and set it to High performance (Microsoft describes this per-app GPU choice in its graphics settings guide). This one change fixes a large share of "my gaming laptop runs the emulator badly" complaints.

Keep GPU drivers current, but not blindly

Driver updates often improve Vulkan, OpenGL and DirectX paths that emulators rely on. Get them from NVIDIA, AMD or Intel directly (Windows Update is usually several versions behind). Waiting a few days after a new release and checking user reports is a sensible habit. If performance drops right after an update, roll back via Device Manager → Display adapters → your GPU → Properties → Driver → Roll Back Driver.

Clear background load

• Close browsers: every tab is a separate process competing for RAM and CPU.
• Pause OneDrive, Google Drive or Dropbox; their disk activity causes micro-stutters.
• Disable overlays you are not using (Discord, recording tools, performance monitors).
• Turn on Game Mode in Settings → Gaming.
• Disable unneeded apps in Settings → Apps → Startup so they do not return on the next boot.

Add antivirus exclusions for the emulator folders

Real-time antivirus scanning (including Windows Defender) intercepts disk reads and writes. An emulator constantly reads its virtual disk image, so that scanning shows up as stutter and slow loading. In Windows Security → Virus & threat protection → Manage settings → Exclusions, add only the emulator's installation folder and its data/virtual disk folder, never a whole drive. Microsoft notes that exclusions lower your protection, so keep the list short.

Part 2: Know Your Hardware Tier

Before touching any slider, open Task Manager and note:

• CPU: number of physical cores and roughly how old it is.
• RAM: total installed and how much is free when Windows is idle.
• GPU: dedicated (NVIDIA/AMD) or integrated (Intel UHD/Iris, AMD Vega/Radeon graphics).

Tier	Typical CPU	RAM	GPU	Sensible target
Low-end	4-core Core i3 / Ryzen 3, or older	8 GB	Integrated	Stable 30 fps, low–medium detail
Mid-range	6–8 core Core i5 / Ryzen 5	16 GB	GTX 1660 / RX 580 class or better	60 fps, high detail
High-end	8+ core Core i7/i9 / Ryzen 7/9	32 GB+	Recent dedicated GPU	60 fps, or higher in games that support it

These targets are starting expectations, not guarantees: every game has its own requirements. If your PC is at the low end or below, also read our guide to the best Android emulator for low-end PCs.

Part 3: The Emulator Settings, One by One

CPU cores

The Android system inside the emulator sees as many virtual cores as you assign. The rule: never assign all your cores, because Windows needs some to feed the emulator. If Windows starves, the emulator's input and disk handling stall even when the guest has compute to spare.

• 4-core CPU: assign 2.
• 6–8 core CPU: assign 4. This is the sweet spot for most mobile games.
• 12+ core CPU: assign 4–6. Few mobile games scale beyond that; the extra cores mostly go to Android background services.

RAM

More is not always better. Allocating too much leaves Windows short, it starts paging to disk, and you get stutters that look exactly like a GPU bottleneck. Too little, and Android's memory management runs constantly, causing hitches of its own.

• 8 GB PC: 3–4 GB for the emulator.
• 16 GB PC: 4–6 GB (6 GB for heavy open-world games).
• 32 GB PC: 6–8 GB. Mobile games rarely benefit from more.

As a ceiling, keep the emulator at or below about half of your total RAM. After changing RAM or cores, fully close and reopen the emulator: many emulators only apply these values on a fresh start.

Resolution and DPI

Resolution is the biggest single lever you have. The emulator renders every pixel you ask for, and most mobile games are designed for phone screens, so rendering at 1440p inside the emulator is mostly wasted GPU work.

• 1280×720: the best starting point for almost everyone; action and casual games look practically the same.
• 1600×900: a good middle ground for games with small UI text.
• 1920×1080: worth it on capable hardware or for strategy games with dense interfaces. Going higher rarely adds visible detail.
• 960×540: a last resort for weak integrated graphics in demanding 3D games.

Change resolution inside the emulator, not in Windows display settings. For DPI, the common default of 240 works for most games; raising it shrinks the in-game UI and touch targets.

Graphics renderer

The renderer decides how Android's graphics calls are translated for your desktop GPU. Names vary ("Graphics mode," "Render engine," "Backend"), but the options are usually:

• Vulkan: typically the lowest overhead on modern dedicated GPUs. Try it first if you have one.
• DirectX (11/12): a stable fallback, and sometimes the better choice on NVIDIA cards or when Vulkan shows glitches.
• OpenGL: the most compatible; often the best option for Intel integrated graphics and older cards.
• Software rendering: CPU-only. Use it only to diagnose a driver problem; it is not playable for 3D games.

There is no universal winner because driver quality varies. Play the same game for two or three minutes on each option, watch the FPS counter and look for visual glitches, then keep the best one. In NovaPlay the choices are native GPU, DirectX 11 (through ANGLE), OpenGL/Vulkan and software.

Frame-rate cap and VSync

Leaving FPS "unlimited" is a common mistake. An uncapped GPU runs flat out, produces heat and, on laptops, thermal throttling that lowers sustained frame rates. Many mobile games also tie animation or physics to 30 or 60 fps.

• Low-end: cap at 30. A locked 30 feels far better than a frame rate that swings between 25 and 50.
• Mid/high-end: cap at 60.
• High-refresh monitor + strong GPU: try 90 or 120 only in games that officially offer a high frame-rate mode.

VSync removes screen tearing. If controls start to feel delayed, turn VSync off and rely on the frame-rate cap instead. NovaPlay has one-click caps at 30, 60, 120 and 144 fps, a fine adjustment up to 240, a high-FPS option and a VSync toggle.

ABI and ARM translation

Most Android apps are built for ARM processors, while your PC is x86. Many games ship x86 code as well, which runs directly; ARM-only games must go through a translation layer, which costs CPU time. If your emulator lets you choose the Android image, prefer an x86_64 one, and expect ARM-only titles to be somewhat heavier on the CPU. NovaPlay runs a 64-bit Android image with ARM translation built in, so ARM-only games still install.

Storage and texture options

Keep the emulator's data folder on an SSD: open-world games load thousands of small files, and hard drives turn that into long loads and in-game hitching. If your emulator offers hardware ASTC texture decoding, enable it: decoding compressed textures in software is a notable CPU drain in some 3D games.

Part 4: Recommended Configurations by Tier

Setting	Low-end	Mid-range	High-end
CPU cores	2	4	4–6
RAM	3–4 GB	4–6 GB	6–8 GB
Resolution	1280×720 (960×540 if needed)	1600×900 or 1920×1080	1920×1080
DPI	240	240	240
Renderer	OpenGL or DirectX	Vulkan (DirectX fallback)	Vulkan
FPS cap	30	60	60–120, game-dependent
In-game graphics	Low, shadows off	Medium–high	High

Start with your column, play for ten minutes, and only then adjust one setting at a time.

Where these settings live in NovaPlay

On first launch NovaPlay sets CPU, RAM and FPS values from your PC's hardware, so in NovaPlay the table above is a check rather than a starting point. It also has performance profiles, including a power-saving profile for modest PCs, and an eco mode. If the automatic values stutter in a specific game, lower the FPS cap first, then the resolution, and only then touch cores and RAM.

Part 5: How Do You Get More FPS?

Once Windows and the emulator are set correctly, these are the remaining levers, from most to least impact:

1. Lower in-game graphics first. Shadows, anti-aliasing and effects quality in the game itself often cost more than any emulator setting. Drop them before lowering resolution.
2. Lower resolution one step. Going from 1080p to 900p or 720p is the most reliable FPS gain.
3. Switch renderer. If you are GPU-limited on one backend, another may do better on your driver.
4. Check thermals. Laptops that throttle after 10–15 minutes need clean vents, a cooling pad, or a lower FPS cap.
5. Use per-game settings when available. A demanding 3D shooter and a light 2D game rarely need the same profile; if your emulator supports per-app profiles, use them.

How to measure properly: turn on the emulator's FPS counter, play for at least a few minutes (the first minute includes asset loading and is always worse), and change one setting at a time. For game-specific tips, see our dedicated Roblox FPS boost guide.

Part 6: Why Is the Emulator Lagging?

Not all "lag" is the same problem, and misdiagnosing it wastes time. First, decide which kind you have:

• Low FPS / choppy motion: choppy even in menus or offline modes. Almost always a settings or hardware issue.
• Stutter / micro-freezes: FPS is fine on average, but it hitches every few seconds. Usually RAM, disk, background tasks or thermals.
• Input lag: the game looks smooth but controls respond late. Usually VSync, the wrong GPU, or an overloaded CPU.
• Network lag: smooth locally, but rubber-banding or teleporting in online matches. This is your connection, not your PC.
• Crashes and freezes: the emulator hangs or closes. Usually too little RAM, overheating, or a driver conflict.

With the game running, open Task Manager side by side:

• CPU at or near 100% → you are CPU-limited: fewer background apps, fewer emulator instances, lower in-game effects.
• Memory above about 90% → Windows is paging: lower the emulator's RAM or close other apps.
• GPU at 100% → lower resolution or graphics quality.
• GPU busy on "GPU 0" when your dedicated card is "GPU 1" → the emulator is on integrated graphics; force the dedicated GPU (Part 1).

Symptom → cause → fix

Symptom	Most likely cause	Fix
Very low FPS everywhere, slow boot	Virtualization disabled	Enable VT-x/AMD-V in BIOS; check Task Manager shows "Virtualization: Enabled"
Low FPS on a laptop with a good GPU	Emulator running on integrated graphics	Windows Graphics settings → emulator → High performance
Smooth at first, worse after 10–15 minutes	Thermal throttling or battery mode	Plug in, High performance plan, clean vents, cap FPS
Stutter every few seconds	Windows paging, too much RAM allocated to the emulator	Lower emulator RAM to half of total or less; close browsers
Hitches when loading areas	HDD or antivirus scanning the virtual disk	Move data to SSD; add antivirus exclusions
Constant low FPS, GPU underused	Wrong renderer or software rendering active	Switch to Vulkan/DirectX/OpenGL and compare
Low FPS with CPU at 100%	Too many background apps or cores misassigned	Close background load; follow the core table
Screen tearing	No frame-rate sync	Enable VSync or cap FPS at your refresh rate
Controls feel delayed	VSync latency or CPU overload	Disable VSync and keep an FPS cap; reduce background load
Rubber-banding only online	Network (Wi-Fi, congestion, VPN)	Wired connection, pause downloads, disable VPN
Graphical glitches or black screen	Driver bug or renderer incompatibility	Change renderer; update or roll back GPU driver
Emulator crashes during play	Not enough free RAM, overheating, driver conflict	Lower allocations, check temperatures, reinstall driver
Performance got worse over time	Corrupt config or cache	Reset settings to defaults or reinstall the emulator

Fixing network lag

If FPS is fine but online matches feel delayed:

• Use Ethernet. It is the biggest network improvement most players can make; Wi-Fi interference causes exactly the kind of intermittent packet loss that feels like lag spikes.
• Check who else is using the connection. Large downloads or 4K streaming on the same network raise your ping. If your router supports QoS, prioritize your PC.
• Disable your VPN while playing. It adds routing distance and usually raises ping.
• Try a different DNS (for example, 1.1.1.1 or 8.8.8.8) if matchmaking or logins are slow. This affects lookups, not in-match ping.

Reinstall or upgrade?

Reinstall if the emulator used to run better and degraded over time, or if you have piled up conflicting settings: a clean install clears corrupt configs and caches.

Consider upgrading if your CPU is well over six years old, you have less than 8 GB of total RAM for games that need 4 GB inside the emulator, or your GPU does not support Vulkan 1.1 or newer. For the cheapest upgrade, more RAM or an SSD usually helps more than anything else.

Frequently Asked Questions

Does giving the emulator more RAM always increase FPS? No. Past the point the game needs, extra RAM does nothing, and taking too much from Windows causes paging and stutter. Follow the tier values above.

Should I use Vulkan or DirectX? Start with Vulkan on a dedicated GPU and DirectX or OpenGL on integrated graphics, then compare both in the same game. Your driver decides the winner more than the emulator does.

Why does my game stutter even though the FPS counter shows 60? Average FPS hides short hitches. Stutter with good average FPS usually points to RAM paging, disk access or background tasks; see the table above.

After the Settings: Controls Matter Too

Performance is only half of a good experience. Playing touch-first games with a keyboard and mouse needs proper key mapping; our guide to keyboard and mouse controls for mobile games covers movement, aiming and camera setup. If you also capture your sessions, recording adds its own load: the guide on how to record mobile gameplay on PC explains how to keep the encoder from eating your frame rate.

Summary

Emulator performance problems almost always trace back to a short list: virtualization disabled, the wrong GPU or renderer, resolution set too high, RAM misallocated, or Windows itself competing for resources. Prepare Windows, apply the settings for your tier, then use the symptom table for whatever is left, changing one thing at a time. If you want to try these settings in NovaPlay, it is a free download for Windows 10 and 11.