If ScummVM is spinning up your fans, draining a laptop battery, or stuttering on a small device, the fix is almost always a handful of settings. Switch to the OpenGL graphics mode, drop any heavy scaler, set the AdLib emulator to MAME, and play with uncompressed audio. Those four changes cut the most CPU work, and you can make all of them from the ScummVM menus in a few minutes.
Old point-and-click games barely tax modern hardware on their own. The load comes from how ScummVM draws, scales, and sounds. Below is what each setting costs and the order to change things so you tackle the biggest drains first.
What makes ScummVM use so much CPU?
ScummVM’s heaviest work is graphics, not the game logic. A game like Monkey Island runs at 320×200. Getting that tiny image onto a modern screen means scaling it up, and some scaling methods run complex math on every pixel of every frame. Software scalers and image filters are done on the CPU, so they add up fast.
Audio is the second big cost. Music synthesis and decoding compressed sound files both run on the CPU. The more accurate the emulation, the more work per second.
A few games add their own load. Some engines redraw the whole screen every frame instead of just the parts that changed, which multiplies the scaling cost. You can’t rewrite the engine, but you can shrink everything around it. Here are the fixes, ranked by how much they usually help.
1. Switch to the OpenGL graphics mode
This is the single biggest win. In the ScummVM OpenGL graphics mode, the original game image is handed straight to your graphics card, and the card does the stretching. That moves scaling off the CPU and onto hardware built for it.
The alternative, SDL Surface, uses a software scaler that runs on the CPU. On a weak machine that difference is the gap between smooth and choppy.
To change it, open ScummVM, select a game (or go to Global Options), open the Graphics tab, and set the Graphics mode to OpenGL. You can read the full breakdown on the ScummVM graphics settings page. If your device has no working graphics driver, OpenGL may not appear, in which case the next fix matters even more.
Rule of thumb: if OpenGL is available, use it. It hands the hardest job to your GPU and frees the CPU for everything else.
2. Drop the scaler and turn off filtering
If you have to use the SDL Surface mode, the scaler you pick decides the CPU cost. Fancy scalers like HQ2x, HQ3x, and the various edge-smoothing filters run heavy per-pixel algorithms every frame. The plain Normal scaler does the least work.
Set the scaler to Normal, and choose 1x if your screen can handle the small image, or 2x for a modest, cheap upscale. Every step up in scale and every fancier filter is more pixels and more math per frame.
- Set Scaler to Normal (avoid HQ2x, HQ3x, AdvMAME, and similar).
- Use the lowest scale factor you can stand, 1x or 2x.
- Turn off Filter graphics. Linear filtering adds smoothing work you may not even want on pixel art.
On the OpenGL mode there is no software scaler at all; the card handles the stretch, so this whole cost mostly disappears. That is another reason to prefer OpenGL when you can.
3. Set the AdLib emulator to MAME
Music is the next drain. Many classic games use AdLib (OPL) synthesis, and ScummVM offers three emulators for it. They trade accuracy for CPU:
| AdLib emulator | CPU cost | Best for |
|---|---|---|
| MAME | Lowest | Weak or battery-powered devices |
| DOSBox | Medium | A balance of sound and speed |
| Nuked | Highest | Powerful PCs chasing accuracy |
MAME uses the least CPU power, so pick it when speed matters. You’ll find this under the Audio tab as the AdLib emulator option. The difference in sound is small; the difference in load can be large on a slow chip.
Watch out for FluidSynth and MT-32 emulation too. Both sound great but ask for a fast CPU. If a game defaults to one of those and you’re struggling, switch the preferred device back to AdLib with MAME.
4. Use uncompressed audio when you can
Decoding compressed audio costs CPU on every clip that plays. FLAC, OGG, and MP3 all have to be unpacked in real time, and those decoders are surprisingly heavy on slow hardware. Uncompressed audio skips that step entirely.
If you rip or convert your own game audio, keep it uncompressed for the lowest load. This matters most on single-board computers and handhelds, where audio decoding can eat a real slice of a small CPU budget. On a fast desktop the cost is minor, so don’t bother re-ripping a working setup.
Quick check: if a specific game stutters only when music or speech plays, compressed audio is a likely culprit. Test with an uncompressed copy.
5. Cap the frame rate and keep v-sync on
A few game engines can run without a frame limit, which pushes the CPU to draw as many frames as possible. That is wasted effort for a game meant to run at 60 frames per second. Where a game offers a frame rate option, keep it at the standard rate rather than an uncapped or 120 fps mode.
V-sync ties the draw rate to your monitor’s refresh, which also stops the machine from rendering pointless extra frames. It’s on by default and worth leaving on for both smoother output and less busywork.
6. Trim the extras
A couple of smaller settings help on the weakest machines:
- Turn off shaders. Like filters, they run per-pixel work on top of everything else.
- Skip aspect ratio correction in SDL Surface mode if you don’t need it, since it adds a software stretch pass. In OpenGL the card handles it, so leave it if you prefer the look.
- Close other apps. ScummVM’s own load is small once it’s tuned, so background programs may be the real reason your CPU is busy.
A low-CPU settings checklist
Work through these in order and stop when performance is good enough:
- Set Graphics mode to OpenGL.
- If using SDL Surface, set Scaler to Normal at 1x or 2x.
- Turn off Filter graphics and any shader.
- Set the AdLib emulator to MAME.
- Avoid FluidSynth or MT-32 emulation on slow hardware.
- Use uncompressed audio where you control the files.
- Keep v-sync on and cap the frame rate at the standard setting.
Most people never need to go past the first four. If a specific game still runs hot after all this, that engine likely redraws the full screen each frame, and there is a hard limit to what settings can do. On a genuinely underpowered device, that game may simply be too demanding, and a lighter title is the honest answer.
Frequently asked questions
Why is ScummVM using so much CPU on old games?
The games are light, but scaling and audio are not. Software scalers, image filters, and accurate music emulation all run on the CPU every frame. Switching to OpenGL and lighter audio settings usually fixes it.
Which ScummVM scaler uses the least CPU?
The Normal scaler at 1x or 2x. Fancy scalers like HQ2x and HQ3x run heavy per-pixel math on every frame. Better still, use the OpenGL graphics mode, which does the scaling on your graphics card instead.
Does OpenGL mode really lower CPU usage in ScummVM?
Yes. In OpenGL mode the game image is handed to the graphics card, which does the stretching. That moves the heaviest job off the CPU, so it’s the first setting to change if it’s available on your device.
What is the least CPU-intensive audio setting?
Set the AdLib emulator to MAME, which uses the least CPU of the three options. Avoid FluidSynth and MT-32 emulation on slow hardware, and use uncompressed audio so nothing has to be decoded in real time.
ScummVM still stutters after changing settings. Now what?
Some game engines redraw the whole screen every frame, which no setting can fully fix. If you’ve applied OpenGL, a light scaler, and MAME audio and it still struggles, the device may just be too slow for that particular game.
Conclusion
To lower ScummVM’s CPU use, switch to the OpenGL graphics mode so your GPU handles scaling, and if you’re stuck on SDL Surface, use the Normal scaler with filtering off. Set the AdLib emulator to MAME, avoid the heavier synths, and play with uncompressed audio. Make those changes in order and stop when the fans go quiet. A good result is smooth play with no stutter and a CPU that stays cool and idle.
Recommended Articles:
cups-browsed Using High CPU on Linux? Here’s Why and How to Fix It
Is CS2 CPU or GPU Intensive? What Really Limits Your FPS
CPU Load Line Calibration: What It Does and What to Set It To
Max CPU Boost Clock Override: What It Does and When It Helps
IIS Worker Process High CPU: How to Find the Cause and Fix It
