Should You Set Games to High Priority for FPS? CPU Priority & Affinity Explained

Setting a game to High priority in Task Manager is one of the oldest FPS tweaks on the internet — and one of the most misunderstood. The honest answer: on a modern, well-behaved PC it rarely changes your average FPS, but on a system with a busy CPU or lots of background apps it can smooth out 1% lows by keeping the game from getting bumped off the CPU at the wrong moment. This guide explains exactly what priority and affinity do, when they help, and how to set them without breaking anything.

Priority is a scheduling hint, not a performance switch — the win, if any, is fewer micro-stutters, not a bigger average number.

What CPU priority actually does

Windows shares the CPU between every running process using a priority system. When two threads want the CPU at the same time, the scheduler gives the time slice to the higher-priority one. The levels, from lowest to highest, are Low → Below Normal → Normal → Above Normal → High → Realtime. Almost everything runs at Normal.

Raising a game to High tells Windows: when the game and a background task both want the CPU, prefer the game. On a modern 8-core-plus CPU with nothing else running, this changes almost nothing — there’s enough CPU to go around, so the game already gets its time. The benefit appears when something else is fighting for the CPU: a browser with 40 tabs, a Chrome-based overlay, Windows Update, an antivirus scan, or a busy Discord/OBS setup. In those cases, High priority reduces the chance that a background thread grabs a core at the exact millisecond your game needs it, which is what produces a random hitch.

It does not overclock anything, unlock hidden performance, or increase your frame cap. It only changes who wins when the CPU is contended.

When it’s worth doing (and when it isn’t)

Worth trying if:

• You have a CPU-bound game (esports titles at high FPS, simulation-heavy games) and a mid-range or older CPU.
• You run heavy background apps while gaming — streaming, recording, many browser tabs, chat overlays.
• You feel occasional stutters even though your average FPS is fine.

Skip it if:

• Your average and 1% lows are already smooth.
• You’re GPU-bound (the CPU isn’t the bottleneck, so priority can’t help). Not sure? See how to check for a CPU or GPU bottleneck.
• You expect it to raise your average FPS — it won’t.

Like most tweaks on this site, this is a “measure it” change. Watch your 1% lows and frame-time graph before and after, not the average FPS number.

How to set High priority (the safe way)

Per session, via Task Manager:

1. Launch the game, then Alt+Tab out (or Ctrl+Shift+Esc to open Task Manager).
2. Go to the Details tab.
3. Right-click the game’s .exe → Set priority → High.
4. Confirm the prompt.

This resets when you close the game. Never choose Realtime — it can starve input, audio, and system threads and lock up your PC.

Make it stick — launch with High priority:

Create a shortcut that always starts the game elevated in priority. The command form is:

cmd /c start "" /high "C:\Path\To\Game.exe"

For Steam games, you can add a launch option or use a small .bat file that calls start /high. Some third-party tools (like Process Lasso) automate this per-process, but the built-in start /high method needs no extra software and is anti-cheat-safe.

What about CPU affinity?

CPU affinity goes a step further: instead of priority, it controls which cores a process is allowed to run on. You set it the same way — Task Manager → Details → right-click → Set affinity → tick specific cores.

Here’s the key point: on Windows 11, you almost never want to touch this. The scheduler already knows which cores are fastest (preferred/“favored” cores) and, on Intel hybrid CPUs, which are performance (P) cores versus efficiency (E) cores. Manually pinning a game usually removes the scheduler’s freedom and makes things worse.

The rare legitimate uses:

• A game that schedules badly onto E-cores and stutters — pinning it to P-cores only can help (many titles now handle this correctly, so test first).
• Isolating a background app (like a capture encoder) onto specific cores so it stays out of the game’s way — often a better move than pinning the game itself.

If you do experiment, change one thing at a time and A/B test with a frame-time overlay. Affinity also resets on relaunch, so it needs the same shortcut/script treatment to persist.

Better latency wins to do first

Priority and affinity are minor, situational tweaks. If you’re chasing smoother frames and lower input lag, these move the needle more reliably:

• Set the right power plan so cores stay awake — see best power plan for gaming.
• Fix the real cause of hitching with our how to fix lag spikes in games guide.
• Lower system-wide timer latency with timer resolution — the single most consistent input-lag tweak we cover: the ultimate guide to timer resolution for gaming.
• Tune the whole input chain in how to minimize input delay for competitive gaming.

Bottom line

Setting a game to High priority is safe, free, and worth a quick test if you game with heavy background load or on a CPU-bound system — but it’s a frame-time smoother, not an FPS unlock, and Realtime is a trap. Leave CPU affinity to the Windows 11 scheduler unless you’ve measured a specific problem. Set it, watch your 1% lows, and keep it only if the frame-time graph actually gets flatter.