Complete guide to boosting FPS in LoL: Medium graphics, 240 FPS cap, no overlays, and NVIDIA Low Latency Mode. ADC main binds and config explained.
LoL is a technically weird game. It's CPU-bound, not GPU-bound — your GPU sits idle while your CPU gets hammered during 5v5 teamfights. And even with top-end hardware, the client runs poorly out of the box. Here's my full setup as an ADC main: graphics, keybinds, camera, and my controversial take on overlays — the ones almost everyone uses and almost no one realizes are killing their FPS.
Graphics: 1920×1080, Everything on MEDIUM (Not Ultra), Capped at 240
Here's the first hot take: I play everything on Medium even though my PC can handle Ultra. Not to spare the GPU — just common sense. After extensive testing across High, Very High, and Ultra, I genuinely can't see a gameplay-relevant difference between Medium and Ultra. What I do see is more consistent frametimes with everything on Medium.
Resolution: 1920×1080.
Frame Rate Cap: 240 FPS.
Character Quality: Medium.
Environment Quality: Medium.
Shadows: Medium (or Low — Yorick's clones look the same either way).
Effects Quality: Medium (drop to Low during massive teamfights if your CPU is modest).
Anti-Aliasing: ON. Barely costs anything in LoL.
Wait for Vertical Sync: OFF (I will never stop saying this — see my sync guide).
Color Blind Mode: OFF unless you actually need it.
On the 240 FPS cap: LoL doesn't let you go higher, and
uncapping it (toggling "Frame rate cap" → Uncapped) in my experience causes instability and worse latency
. The instinct is "more FPS = better" — in LoL it's the opposite. The client is designed for consistent frametimes, and forcing it to push 600+ FPS introduces microstutters and variable latency. In CS2 or Valorant, uncapping helps. In LoL, it hurts. Cap at 240 and move on.
On laptops or mid-range PCs, Effects Quality: Low + Shadows: Low helps during big fights (5v5 + minions + Wukong/Annie clones). Medium everywhere else is plenty.
Quick Cast: ON + Shift+Key = The Combo Almost Nobody Sets Up Right
I run Quick Cast ON by default and Quick Cast with Indicator on Shift+key. It's the perfect combo:
Press Q alone → Q fires instantly at your cursor (classic Quick Cast, maximum input speed).
Hold Shift+Q → the ability indicator appears before you commit. If the ability needs precision (Caitlyn ult, Ezreal Q at long range), release at the exact right moment.
This gives you the best of both worlds: speed by default, precision when you need it. Only using regular Quick Cast means losing precision on long-range abilities. Only using Quick Cast with Indicator means losing speed on fire-and-forget abilities. The Shift combo gives you both.
Camera: Always Unlocked, Space for Big Repositions
Always unlocked camera. Every pro plays this way, and for good reason — it's what lets you see what's happening off-screen (incoming ganks, fights on the other side of the map, river control). If you play locked because you "lose track," the problem isn't the camera — it's practice.
Space key: the classic "center camera on my champion" bind. I use it when I'm repositioning hard (after a teleport, a Hecarim dash chasing me down, a failed recall) and need to find my character immediately. For keeping the camera on myself during long fights, I prefer releasing Space and going back to unlocked rather than toggling to locked — it gives you more control.
Other useful camera binds:
F1 centers on you; F2–F5 center on your allies. Great for watching a gank on the other side of the map without losing sight of your carry.
Camera Move Speed: max it out. The default speed is painfully slow.
My ADC Keybinds: A, X, 1–5, Z, V, MB5
This is the setup I've refined the most, because as an ADC the milliseconds between auto-attacking and moving are the difference between living and dying:
Attack on A (Attack Move): the classic bind. Shows your auto-attack range before committing — useful for knowing whether you're in range before you engage.
Fast attack on X (Attack Move on Cursor): the direct kite bind. Attacks the closest target to your cursor WITHOUT prompting and WITHOUT showing range. This is what I use during teamfights where speed is everything. The combo of A to check range + X for aggressive kiting covers 95% of situations.
Items 1–5 on keys 1–5: standard, but relocated (1 = elixir/control ward, 2–4 = core build, 5 = boots — yes, boots in slot 5 for quick actives).
Z and V for last item slots (when I carry an extra active like Edge of Night or Galeforce, it goes here — comfortable bind, easy to press without lifting your hand off the mouse).
Attack Only Champions on MB5 (mouse side button): the least-known and most useful bind. Attacks champions only, ignores minions. Essential for not losing your target mid-wave (Twitch going invisible on you while 8 minions are in the way — with Attack Only Champions, Caitlyn's Q locks onto Twitch, not the melee minion in front of him).
On item actives: learn what each item actually does before auto-building. People buy Bloodthirster because "it's always bought" and miss the fact that Galeforce on that same carry opens up way more outplay potential. Spending 20 minutes studying stats and passives will move the needle on your rank more than any overlay.
Current ADC tip (recent patch): Hexoptic over Yun Tal in 99% of cases. Yun Tal is overrated by YouTube shorts — Hexoptic gives you more stability in extended fights and better early-lane pressure. If you're unsure what to build in-game, that's your first rule.
The Client and Why I'm Anti-Overlay
Here's the take that gets the most pushback: I don't use any overlay (Blitz, Mobalytics, U.GG, Porofessor...) and I recommend you don't either.
Why? Two reasons:
1. LoL is poorly optimized. The client has needed serious optimization work for years. Overlays add another layer of processes — graphics hooking, game memory reading, and on-screen rendering. In my experience, they drop FPS noticeably during teamfights — which is exactly when you can't afford to lose them. 2. They atrophy your game sense. When I was starting out, yes, I used Blitz for builds. It told me "buy X, Y, Z" and I bought it. It worked, but I never learned why any item existed. The day I uninstalled it felt like learning to play from scratch. Now I build on my own and understand the why — and that's what lets me adapt when the enemy runs Dr. Mundo + Shen + Sion, where any standard overlay build falls apart.
If you've been playing a while and are heading toward Diamond+, overlays are a crutch that costs you both FPS and growth. If you're brand new, I get it as a transitional tool — but your goal should be to get off it, not to stay on it.
Legacy Cursor: Forgotten but Important
The default cursor in the newer LoL client is small and flat. Almost every pro uses the Legacy Cursor — bigger, more visible, especially during effects-heavy fights.
Settings → Interface → Use Legacy Cursor → ON.
It's buried where you'd least expect it and almost nobody enables it. If you're losing your cursor in visually chaotic teamfights, try this before any "magic NVIDIA tweak."
Why the NVIDIA Control Panel Actually Matters in LoL
LoL is one of the few popular competitive games without native NVIDIA Reflex. As I explained in the NVIDIA Control Panel guide, that makes it special: in CS2 or Valorant, Control Panel settings fight with Reflex and often get overridden. In LoL there's no Reflex to step on them, so the "Low Latency Mode: On" setting in the Control Panel actually does real work.
If you play LoL and haven't touched the Control Panel, that guide is the one that'll move the needle the most after this one.
What Doesn't Matter: Skins, Obscure Runes, and "Pro Tricks"
Skins "that improve auto-attack animation cancelling". Skins only change visuals and sometimes audio. They do NOT affect timing, range, damage, or anything mechanical. If you like a skin, buy it for aesthetics, not performance.
Exotic Mobafire runes to look pro. The meta runes on u.gg or op.gg are well-calibrated. "Hidden" builds are rarely better — they're just different, and usually less efficient.
"Pro tricks" like Windowed + Borderless for "better input": in LoL, exclusive Fullscreen is the smoothest mode. Borderless adds a window manager layer that genuinely introduces variable latency.
Dropping resolution to 720p in LoL "for more FPS." Unlike Valorant or CS2, the bottleneck in LoL is the CPU. Lowering resolution does nothing because your GPU was already sitting at 30% load.
Quick Summary
Resolution: 1920×1080.
Graphics: everything on Medium (not Ultra — you won't notice the difference). Effects/Shadows to Low if your CPU is modest.
Frame cap: 240 FPS — don't uncap it (causes instability).
Quick Cast ON by default, Shift+key = Cast with Indicator for precision.
Camera always unlocked. Space for big repositions.
ADC binds: A for attack with range display, X for fast attack-move, 1–5 for items, Z and V for last item slots, MB5 = Attack Only Champions.
Legacy Cursor: ON.
Anti-overlay: they tank your FPS and stunt your growth. Learn the items yourself.
Current ADC tip: Hexoptic > Yun Tal in 99% of cases.
NVIDIA Control Panel + Low Latency Mode ON: this is where LoL actually benefits (no Reflex to override it).
If you only take two things away from this guide: cap at 240 (don't uncap) and ditch the overlays. Those two alone will give you more FPS and consistency than any exotic graphics tweak.
Frequently Asked Questions
Why does League of Legends run slowly even though my PC is good?
LoL is CPU-bound, not GPU-bound: your GPU sits idle while your CPU gets hammered during 5v5 teamfights with effects. The client is also poorly optimized out of the box. That's why dropping to 720p barely helps — the bottleneck is the CPU, not the GPU.
Should I set LoL graphics to Medium or Ultra for more FPS?
Medium, even if your PC can handle Ultra. After extensive testing across High, Very High, and Ultra, there's no gameplay-relevant difference between Medium and Ultra — but frametimes are more consistent with everything on Medium. On modest CPUs, Effects Quality and Shadows on Low help during big 5v5 fights with minions and clones.
Do overlays like Blitz or Porofessor lower FPS in League of Legends?
Yes. Overlays add a layer of processes — graphics hooking, game memory reading, and on-screen rendering — that noticeably drops FPS during teamfights, which is exactly when you can't afford it. On top of that, relying on automatic builds prevents you from learning what each item does, which hurts your ability to adapt when the standard build doesn't cut it.
Should I remove the FPS cap in League of Legends for better performance?
No. Uncapping it causes instability and worse latency in LoL. The client is designed for consistent frametimes, and forcing it to push 600+ FPS introduces microstutters and variable latency. In CS2 or Valorant, uncapping improves performance — in LoL, it makes things worse. The recommended cap is 240 FPS.
