Why Your GPU Is Not at 100 % in a Game, and What to Do About It
A powerful graphics card running at 60 % is not coasting: it is waiting. The seven usual causes, from the CPU to the frame limiter, how to tell them apart with three tests and when the right fix is to do nothing.

In short
- In a demanding game, a powerful GPU below 100 % usage is usually waiting for something else. The most frequent cause is the CPU, and within it, a single thread that cannot keep up.
- Some causes are not a problem: a frame limiter, vertical sync or a game that is light for your card also leave the GPU below its maximum.
- Total CPU usage is misleading. On a 16-core, 32-thread processor, one thread at 100 % reads 3 % in the total. You have to look at usage per thread.
- The fix depends on the cause: if it is the CPU, lowering the resolution does not help; you have to lower what weighs on the CPU (population, draw distance, shadows) or change processor.
If your GPU does not reach 100 % in a demanding game and the frame rate is not what you expect, something is holding it back. Almost always it is the CPU: the graphics card has capacity to spare, but the draw commands reach it more slowly than it could spend them, and while it waits, its usage drops. It is the most reliable hint of a bottleneck.
It is not always a problem, and it is not always the CPU. This guide goes through the causes in order of frequency, how to tell them apart and what to change in each case.
What “GPU usage” really measures
The percentage you see in Task Manager or an overlay shows how much of the time the GPU had work in flight, not how much power it is spending at each instant. Two nuances:
- 100 % means the GPU never runs out of work. It is normal when the GPU is the limit, and it is what you want to see in a demanding game.
- 50 % means that half of the time it had nothing to do. The card could deliver more frames if someone passed it work faster.
One more detail: Task Manager shows a single engine of the card by default (3D). If part of the game runs on another one (compute, data copy), the number looks lower than it is. For a reliable reading use the total usage in the manufacturer’s overlay or a tool such as PresentMon.
The seven causes, most to least frequent
| # | Cause | How to recognize it | What to do |
|---|---|---|---|
| 1 | CPU limiting (one thread) | One thread near 100 %; frames do not change when you lower the resolution | Lower population, draw distance and shadows; upgrade the processor |
| 2 | Frame limiter or V-Sync | Frames pinned at 60, 120 or 144 | Check the game’s limiter, the driver’s and vertical sync |
| 3 | Game or resolution not demanding enough for your GPU | GPU low, CPU low, frames already high | Nothing to fix; raise quality or resolution |
| 4 | Engine limited by design | A part of the engine (the game thread, the render thread) is serial and does not scale | Settings that reduce game load; wait for patches |
| 5 | Slow memory or storage | Stutter when crossing zones; GPU that drops in chunks | Dual-channel RAM with the profile on, an SSD, textures matched to VRAM |
| 6 | Network waits | In online games, drops in crowded zones even when your PC is idle | Measure ping; the cause may be on the server |
| 7 | Temperature or power limit | GPU or CPU clocks that drop over time | Improve cooling, check the power supply |
1. The CPU limits, usually a single thread
Most game engines have a main thread that coordinates the game logic (what each character does, what happens in the world) and prepares what the GPU must draw. That thread cannot easily be split across many cores. When it hits 100 %, the rest of the processor can be nearly idle and the GPU is waiting.
How to check it on Windows: open Task Manager, Performance tab, CPU, right-click the graph and choose Change graph to > Logical processors. With the game running, look for one or two threads pinned near 100 % while the GPU is low. A 16-core, 32-thread processor with one thread maxed out reports only 3 % total usage; that is why the total is useless.
2. A limit that you or the game set
If the GPU drops and the frame rate is pinned at a round number, a limiter or V-Sync is probably on. The GPU then does only the work needed to reach the cap and rests the remaining time. That is correct behavior. The guide to V-Sync, G-Sync, FreeSync and frame limits explains when it makes sense.
3. There is not enough work
A light game on a powerful card does not fill it, and that is fine. If you already have more frames than your display shows, spend the surplus on quality: a higher resolution, upscaling in native mode or higher settings.
4. The engine itself has a limit
Some games scale badly with many cores, or have parts of the logic that only run on one thread. Hardware does not fix that; patches do. If you see the same behavior on different PCs, it is the engine.
5. Memory or storage
The GPU can only draw what is already in memory. If the game loads textures or geometry from disk as you turn the camera, the GPU waits. The symptoms are stutter rather than a constant drop. You spot them by looking at the 1 % lows, not the average. The guide RAM, SSD and VRAM for big-world games expands on it.
6. The network, in online games
In an MMO, part of the work depends on data arriving from the server: where the other players are, what has happened. If it arrives late or in bursts, the scene updates worse even when your PC is free. Ping does not change GPU usage directly, but a saturated server or an unstable connection produces similar symptoms (choppy movement) that get mistaken for a PC problem.
7. Temperature and power limits
A GPU or CPU that heats up lowers its clock to protect itself, and performance drops over time. If the frame rate starts well and degrades after ten minutes, look at temperatures and clocks.
Three tests that separate the causes
- The resolution test. Lower it one step and return to the same spot. If the frame rate rises, the limit was the GPU. If it barely changes, it was the CPU (or something else). Raise it: if the frame rate does not drop, that confirms the GPU was not the limit.
- The thread test. Watch usage per thread. One thread at the maximum with the rest free points to the game’s main thread.
- The cap test. Temporarily turn off V-Sync and the limiter. If frames rise and GPU usage rises with them, it was a cap.
There is a symptom and cause table in the fps and ms calculator. Always run them in the same scene, the busiest one you play, and change one thing at a time. The details of the method are in CPU-bound versus GPU-bound.
What to do for each cause
- If it is the CPU: lower the settings that load the CPU (number of characters and objects, draw distance, shadows), close background programs, enable the fast memory profile and, if that is still not enough, the change is the processor. Processors with a lot of cache, such as AMD’s with 3D V-Cache, help especially in this case; they are explained in what 3D V-Cache is.
- If it is a cap you set: leave it, it is what you wanted.
- If it is memory or storage: 32 GB in dual channel, an SSD and textures that match your VRAM.
- If it is the network: measure ping and packet loss; see ping, latency and servers.
- If it is temperature: clean, improve airflow, check the cooler.
What you should not do is buy a faster graphics card without having confirmed that the GPU is the limit. With the CPU limiting, a better card leaves the frame rate where it was.
The case of persistent-world online games
Games with many players, fauna and building in the same world are typical ground for cause 1: many entities must be simulated and drawn at once. COLONIZED, a space survival MMO built with Unreal Engine 5 (closed alpha applications open, first waves planned for winter 2026-2027, not yet playable), is in that category, which is why we measure the cost of each part in milliseconds in the development build. We have not published system requirements. What we have measured so far is in our guide to optimizing Unreal Engine 5 games.
To choose hardware with this in mind, the guide is the best PC for MMO and survival games in 2026-2027.
Questions and answers
Why is my GPU not at 100 % in a game?
Because something makes it wait, or because it has not got enough work. The usual causes are a CPU bottleneck, a frame limiter or V-Sync, a game that is not demanding enough for your card, slow memory or storage and, in online games, waiting for data from the server.
Is it bad if the GPU is not at 100 %?
It depends. If you already get the frame rate you want, it does not matter. If the frame rate is low and the GPU sits at 50-70 %, you are paying for a card that cannot perform because something else limits it.
How do I know if it is the CPU?
Open Task Manager, switch the CPU graph to logical processors and look for one thread near 100 % while the GPU is low. Confirm it by lowering the resolution: if the frame rate does not rise, the GPU was not the limit.
What GPU usage is normal in a game?
In a demanding game at a high resolution with no frame limit, between 95 and 100 %. In games with many characters, such as an MMO, lower values are normal if the CPU is the limit.
Sources
Third-party figures link to their source. The date is the publication date or, when there is none, the day we checked the page.
- PresentMon: capture of frame times and latencies · Intel (GameTechDev, GitHub) · 2026-10-22



