-
Notifications
You must be signed in to change notification settings - Fork 0
Reference Overclocking
The Switch runs its CPU and GPU at conservative clocks to save battery and stay cool. For the heavier emulators — N64, Dreamcast, Saturn, PSP, DS, 3DS, and PS2 especially — raising those clocks is the single biggest thing you can do to turn a stuttering game into a smooth one. This page covers doing it safely.
Best effort: overclocking is done through separate homebrew, not HaulNX. The tools below are the authoritative source for their own setup — this is an overview, not a replacement for their docs.
This requires custom firmware. Overclocking needs Atmosphère (or equivalent CFW) with sysmodule support. It's not possible in a stock or "hbmenu-only" setup.
sys-clk is the standard overclocking sysmodule. It lets you set CPU, GPU, and memory clocks — globally or per-game — and applies them automatically.
- Install sys-clk into
sd:/atmosphere/per its README, and reboot. - Control it with an overlay: status-monitor-overlay or the sys-clk Tesla overlay, opened via Tesla / ovlloader. The overlay shows live clocks, temperature, and frame timing, and lets you set per-game profiles.
- Launch your emulator, open the overlay, and raise the clocks (see ranges below). Save it as a per-game profile so it only applies where you want it.
- CPU clock is what most emulators are bottlenecked by. Raising it helps N64, Saturn, Dreamcast, PSP, DS, 3DS, and PS2 the most.
- GPU clock matters when you're upscaling or running docked at higher resolution (DuckStation upscaling, PPSSPP rendering resolution).
- Memory (EMC) clock gives a smaller, broader boost and runs warm — raise it last.
Rough guidance (exact safe maximums vary by unit and by docked/handheld):
| Handheld | Docked | |
|---|---|---|
| CPU | up to ~1785 MHz | up to ~1785 MHz |
| GPU | ~460–768 MHz | up to ~921 MHz+ |
| Memory | ~1600 MHz | up to ~1996 MHz |
Docked gives you both more thermal headroom and higher official GPU/memory ceilings, so demanding systems (Saturn, Dreamcast, N64) are happiest docked.
- Heat and battery are the real costs. Higher clocks mean more heat and faster drain; sustained max clocks handheld will get the console warm and the fan loud. Watch the temperature readout in the overlay.
- Raise gradually. Bump CPU first, test the actual game, then add GPU/memory only if you still need it. There's no benefit to maxing everything for a game that already runs full-speed.
- Per-game profiles beat a global overclock — you don't want light 2D games (or the Switch's own menus) running hot for no reason.
- Overclocking is widely used and generally safe within these ranges, but it's not officially sanctioned; you accept the thermal wear-and-tear tradeoff.
Big help: N64 (RetroArch), Flycast / Dreamcast, Yaba Sanshiro / Saturn, PPSSPP / PSP, melonDS / DS, Raikopon / 3DS, NetherSX2 / PS2, Cemu / Wii U — PS2 and Wii U need it more than anything else here, and are the cases where docked isn't really optional. Little or no benefit: the 8- and 16-bit systems and the handhelds up through GBA — those run full-speed at stock clocks already.