Key takeaways
- CPU limit: the frame rate drops when the screen fills with enemies and effects, even on the lowest graphics preset.
- Presentation and refresh-rate mismatch: since The Edge of Fate update in July 2025 the game no longer offers exclusive fullscreen. “Fullscreen” is now a borderless mode that follows the Windows desktop refresh rate, so a desktop left at 60 Hz quietly limits the game.
- Overlay hitching: in a Bungie staff thread opened in June 2026 to collect framerate reports, many players linked regular hitches to the Steam overlay.
- Settings that are too heavy for the GPU: shadows, ambient occlusion, foliage and depth of field cost the most.
- System issues: an outdated GPU driver, a stale shader cache after a patch, thermal throttling, a laptop running on integrated graphics, or the game installed on a hard drive.
To fix FPS drops in Destiny 2, first find out whether your CPU or your GPU is the limit, then set Windows to your monitor’s real refresh rate, turn off the Steam overlay, drop Shadow Quality, Screen Space Ambient Occlusion and Foliage Detail Distance, and cap the frame rate about 3 FPS below your refresh rate. Most sudden drops come from one of five causes, and each one has a quick check, so work through them in order instead of lowering every slider at once.
Why Destiny 2 drops frames on PC
Destiny 2 still runs on DirectX 11 and leans heavily on the processor. Physics, AI, networking and the many enemies in strikes, raids and public events are handled by the CPU, so a high-end graphics card can sit at half load while the frame rate falls in busy fights. Five causes cover almost every case:
63pcs Destiny 2 Sticker, Cute Cartoon Vinyl Waterproof Stickers for Water Bottle,Skateboard,Laptop,Phone,Journaling,Scrapbooking Decals for Party Supply Decor
Included for 'How to Fix FPS Drops in Destiny 2: Causes, Checks and Fixes' because the listing specifies Cute Cartoon Vinyl Waterproof Stickers for Water Bottle and Skateboard, details this guide uses to compare options.
View on Amazon
Numskull Destiny 2 Witherhoard Exotic Grenade Launcher Figure 14x7 (35x18cm) Limited Edition Replica Plaque - Official FPS Sci-Fi Action Video Game Figurine Collectible
Included for 'How to Fix FPS Drops in Destiny 2: Causes, Checks and Fixes' because the listing specifies Official FPS Sci-Fi Action Video Game Figurine Collectible, details this guide uses to compare options.
View on Amazon
CC Countdown Characters Destiny 2 Ghost Shell Buildable Collectible Figure
Included for 'How to Fix FPS Drops in Destiny 2: Causes, Checks and Fixes' as a relevant option in this category; details come from the product listing.
View on Amazon- CPU limit: the frame rate drops when the screen fills with enemies and effects, even on the lowest graphics preset.
- Presentation and refresh-rate mismatch: since The Edge of Fate update in July 2025 the game no longer offers exclusive fullscreen. “Fullscreen” is now a borderless mode that follows the Windows desktop refresh rate, so a desktop left at 60 Hz quietly limits the game.
- Overlay hitching: in a Bungie staff thread opened in June 2026 to collect framerate reports, many players linked regular hitches to the Steam overlay.
- Settings that are too heavy for the GPU: shadows, ambient occlusion, foliage and depth of field cost the most.
- System issues: an outdated GPU driver, a stale shader cache after a patch, thermal throttling, a laptop running on integrated graphics, or the game installed on a hard drive.
Checks: find your bottleneck in five minutes
Turn on a performance overlay (NVIDIA app, AMD Software or MSI Afterburner) and play the area where the drops happen. Watch GPU usage, frame rate and frame time together.
| What you see | Likely cause | Go to |
|---|---|---|
| GPU usage 95-99% and FPS below target | GPU limit | Graphics settings table |
| GPU usage under about 80% while FPS falls in big fights | CPU limit | CPU-side fixes |
| In-game counter looks steady but motion stutters every few seconds | Frame pacing or overlay hitching | Presentation and overlay fixes |
| FPS never goes above 60 on a 144 Hz or faster monitor | Windows refresh rate set to 60 Hz | Presentation fixes |
| FPS is fine for 20-30 minutes, then sinks | GPU or CPU temperature over about 85-90°C, or a long-session slowdown | System fixes |
A steady counter with a spiky frame-time graph points to pacing or hitching, not raw GPU power, so lowering graphics settings will not cure it.
Fix 1: presentation, refresh rate and overlays
Set the desktop refresh rate
Open Windows Settings, then System, Display, Advanced display, and choose the highest refresh rate your monitor supports. Because the game now presents through a borderless mode, it inherits this value. Then confirm Window Mode is set to Fullscreen and the in-game resolution matches your native resolution, so the image is not rescaled.
Use variable refresh rate properly
If you own a G-SYNC or FreeSync monitor, enable it for windowed and fullscreen applications in the driver (in the NVIDIA Control Panel the option is “Enable for windowed and full screen mode”). A borderless game is treated like a window, so a fullscreen-only setting may not apply.
Turn off overlays
In Steam, right-click Destiny 2, open Properties, and on the General tab untick “Enable the Steam Overlay while in-game”. Close other overlays you do not need, such as Discord and recording tools.
Fix 2: graphics settings that move the needle
Destiny 2 does not offer DLSS, FSR or XeSS upscaling, so Render Resolution is your only built-in scaling tool. Start from these values and raise cheap settings only if you have headroom.
| Setting | Value for stable FPS | Why | Cost to performance |
|---|---|---|---|
| Shadow Quality | Low (Medium on strong GPUs) | The most expensive setting in most scenes | High |
| Screen Space Ambient Occlusion | Off (HDAO if you have headroom) | Contact shadows you rarely notice in combat | High |
| Foliage Detail Distance | Low | Draws grass farther away with no gameplay value | Medium |
| Foliage Shadows Distance | Low | Extra shadow work in open zones | Medium |
| Depth of Field | Off | Blur pass that also softens the image when aiming | Medium |
| Environmental / Character Detail Distance | Medium | Fewer objects to prepare each frame, which helps CPU-limited systems | Medium |
| Light Shafts | Medium | High adds cost in bright outdoor scenes | Low to medium |
| Motion Blur, Wind Impulse, Chromatic Aberration, Film Grain | Off | Cosmetic effects with small but real cost | Low |
| Anti-Aliasing | SMAA | Sharper than FXAA and cheap | Low |
| Texture Quality | Highest with 8 GB VRAM or more, Medium with 4 GB | Uses video memory, not much GPU compute, until VRAM runs out | Low unless VRAM is full |
| Render Resolution | 100% at 1080p; 85-90% at 1440p or 4K if GPU-limited | Reduces pixels rendered on a GPU limit | High |
| Field of View | 90-100 if FPS is tight | Wider views put more objects on screen for both CPU and GPU | Low to medium |
Fix 3: cap the frame rate for smooth frame times
An uncapped Destiny 2 swings between highs and lows, and those swings feel like drops even when the average is high. Turn on Framerate Cap Enabled and set Framerate Cap a few frames under your refresh rate. With variable refresh, this keeps every frame inside the adaptive-sync range, so you can leave Vsync off and avoid both tearing and extra input lag.
| Monitor refresh | Time per refresh | Suggested Framerate Cap | Frame-time target |
|---|---|---|---|
| 60 Hz | 16.7 ms | 58 | 17.2 ms |
| 120 Hz | 8.3 ms | 117 | 8.5 ms |
| 144 Hz | 6.9 ms | 141 | 7.1 ms |
| 165 Hz | 6.1 ms | 162 | 6.2 ms |
| 240 Hz | 4.2 ms | 237 | 4.2 ms |
Worked example: if a CPU-limited raid encounter dips to about 100 FPS, frame time rises to 10 ms. On a 240 Hz monitor that is a jump from 4.2 ms to 10 ms, which feels like a big stutter; capping at 141 narrows the swing to 7.1-10 ms. If your lows sit far below refresh, pick a cap the game holds almost all the time, since a stable 120 feels better than a jumpy 180.
For NVIDIA cards, set NVIDIA Reflex Low Latency to On + Boost on a desktop, or On for laptops, where Boost can add heat and trigger throttling. Reflex mainly reduces input lag, but it also keeps GPU clocks up during CPU-limited moments.
Fix 4: CPU-side relief
- Close browsers, launchers and capture tools that compete for CPU time, especially on 4- and 6-core processors.
- Set the Windows power mode to Best performance, and on laptops make sure the charger is connected.
- Check that your RAM is running at its rated speed (XMP or EXPO enabled in BIOS). Running memory at default speed hurts CPU-bound games more than GPU-bound ones.
- Remember the floor: Bungie’s recommended specs list an Intel Core i5-2400 or i5-7400, or a Ryzen 5 1600X, with a GTX 970 or GTX 1060 6GB. Hardware near those minimums will dip in large activities no matter which settings you choose.
Fix 5: system and install fixes
- Update your GPU driver from NVIDIA, AMD or Intel directly, which Bungie support also recommends.
- After a big patch, verify game files in your launcher, then play one full activity so new effects compile and cache before you judge performance.
- Reset settings by closing the game and renaming the cvars.xml file in %appdata%\Bungie\DestinyPC\prefs; the game rebuilds it with defaults on the next launch.
- On laptops, open Windows Settings, System, Display, Graphics, choose Destiny 2, and select High performance so it runs on the dedicated GPU.
- Install the game on an SSD. Loading zones and patrol areas stream assets constantly, and hard drives cause hitches.
- Check temperatures. If the GPU or CPU passes about 85-90°C, clean dust filters and improve case airflow before changing anything else.
When nothing helps
Regular hitches on a powerful system with low GPU usage usually mean the engine and presentation issues many players have reported since the switch to borderless-only fullscreen. Bungie’s framerate thread on its PC support forum asks for a short video, a DxDiag report and the activity where it happens; adding your data there is the best next step, while a frame cap and the overlay fixes keep the game as smooth as possible.
