Measure the problem before optimizing
No universal toggle doubles FPS. Repeat a representative scene or built-in benchmark and record average frame rate, stutter, temperature and approximate CPU, GPU and memory use before changing Windows. That baseline shows whether a modification helps or simply feels different for a few minutes.
Install stable Windows updates and the official GPU driver, restart and test with unnecessary apps closed. Avoid registry cleaners, unknown driver packs and utilities promising zero latency. A stable, measurable system beats a pile of changes that cannot be traced.
1. Assign the correct GPU to each game
Under Settings > System > Display > Graphics, add the game executable and select High performance. This is most useful on laptops with integrated and dedicated graphics, where Windows can select a low-power GPU. Restart the game after saving.
Verify the active GPU in Task Manager or the manufacturer’s official overlay. High performance increases power use and heat; on battery or in a light game, letting Windows decide may be more appropriate. Do not force a GPU that the laptop display route cannot directly use.
2. Enable optimizations for windowed games
Windows 11 provides Optimizations for windowed games under Settings > System > Display > Graphics > Default settings. Microsoft says it moves compatible DirectX 10 and 11 games from the legacy blt presentation model to the newer flip model, reducing frame latency and enabling modern features.
It targets windowed and borderless-windowed modes. Restart the game after changing it. If one app flickers, breaks capture or performs worse, disable the feature only for that executable instead of removing it from the entire library.
3. Configure refresh rate, VRR and cables
Under Advanced display, select the refresh rate your monitor supports. Running a 144 Hz panel at 60 Hz wastes part of its capability. Use a cable and port that support the chosen resolution and refresh rate; not every HDMI or DisplayPort connection on the same machine has equal bandwidth.
Enable variable refresh rate when the monitor and GPU support it. VRR reduces tearing as frame rate moves inside the compatible range, but it does not repair extreme drops or replace consistent frame delivery. Check the monitor’s physical menu too.
4. Use HDR and Auto HDR only on a suitable display
HDR can expand brightness and color, but a limited display may look washed out or dim. Enable it for the correct monitor under Display > HDR and use Microsoft’s calibration tool, then adjust SDR brightness for the desktop.
Auto HDR expands compatible SDR games, including older DirectX 11 and 12 titles. It does not add native textures or lighting. If a game looks wrong, disable Auto HDR for that app and keep HDR where it provides a visible benefit.
5. Automatic Super Resolution has hardware limits
Automatic Super Resolution uses AI to improve compatible games on certain Copilot+ PCs. Microsoft limits it to specific hardware and titles, so do not assume it appears on every Windows 11 computer. Check official compatibility first.
When available, compare text, HUD elements and fine geometry in motion. Like other upscalers, it can exchange internal resolution for performance. If the game offers DLSS, FSR, XeSS or another built-in option, compare both routes and use the most stable one.
6. Reduce background load without disabling security
Close browsers with many tabs, heavy synchronization, unused launchers and duplicate capture tools. Review Startup apps in Task Manager and disable only software you recognize. Keep security, audio, accessibility and essential drivers enabled.
Overlays are useful for chat, capture and metrics, but several can hook the renderer at once. Disable them one by one while diagnosing stutter. If the problem stops, reactivate only the tool you use.
7. Watch temperature, power and storage
Use the correct charger on a laptop and choose a power mode appropriate for its cooling. A CPU or GPU at its thermal limit can reduce frequency after several minutes. Keep vents clear and follow the manual when cleaning.
Maintain free space on the system and game drives. Updates, caches and temporary files need headroom. Allow shader compilation to finish before judging the opening minutes. Moving a game to an SSD can improve loading but does not add GPU power.
8. Change in-game settings in the right order
Start with resolution, upscaling and ray tracing because they often have the largest impact. Then adjust shadows, reflections, ambient occlusion and draw distance. Texture quality mainly uses video memory; lowering it can prevent stutter when VRAM is full even if average FPS changes little.
Set a frame cap the machine can sustain. A stable 60, 90 or 120 FPS can feel better than high peaks with constant drops. Use the game’s own shader-rebuild or cache tool before manually deleting files.
| Symptom | First check |
|---|---|
| Constant low FPS | GPU use, resolution, upscaling and ray tracing. |
| Stutter after several minutes | Temperature, VRAM, background work and shaders. |
| Screen tearing | Display refresh rate, VRR and frame cap. |
| Washed-out HDR | Display capability, calibration and per-app settings. |
9. Change one variable and preserve evidence
Change one setting, restart when required and repeat the same scene. Record the result. Changing the driver, power plan, resolution and five game options together makes it impossible to identify what helped or caused an error.
Create a restore point before major system changes and keep official installers that worked. When one patch harms a game, check developer notes and wait for a fix instead of applying unknown scripts.
Conclusion: optimization is balance, not one number
The best configuration maintains stable frame delivery, useful image clarity and reasonable temperatures. Enable Windows features that your hardware supports, reduce measured background load and tune each game for its engine and your display.
Save a stable profile before experimenting. If CPU, GPU or memory remains saturated under reasonable settings, the limit may be physical. Measuring it prevents spending money on fake optimizers and helps identify the component that would actually matter.