Black Ops 7 FPS Boost: Settings, VRAM Scale and Worker Threads
SHORT ANSWER
The two highest-impact Black Ops 7 fixes are lowering VRAM Scale Target from its 90% default to 60-70%, which resolves most stuttering, and turning ray tracing and motion blur off. Beyond that, run the game from an SSD (it is a hard requirement), enable NVIDIA Reflex at On + Boost, and cap frames slightly below your refresh rate for consistent frame times.
At a glance
| Storage requirement | SSD - officially required |
|---|---|
| Biggest single fix | VRAM Scale Target 60-70% |
| Turn off first | Ray tracing, motion blur |
| Anti-cheat | Kernel-level - settings and driver tuning only |
| Latency setting | NVIDIA Reflex On + Boost |
Key takeaways
- The default VRAM Scale Target of 90% causes stuttering on most cards. Dropping it to 60-70% is the single most effective fix in the game.
- Black Ops 7 requires an SSD. Running it from a mechanical drive produces stutter that no settings change will fix.
- Ray tracing and motion blur cost a large share of your frame budget and provide zero competitive benefit.
- On Intel 12th to 14th generation CPUs, the renderer defaults to using efficiency cores as well as performance cores, which hurts frame-time consistency.
- Shader pre-loading is worth letting finish. Interrupting it guarantees hitching in your first matches.
Quick setup
- 1
Set VRAM Scale Target to 65%
The 90% default leaves no allocation headroom, so every unexpected allocation becomes a visible hitch. This single change resolves most Black Ops 7 stuttering reports.
- 2
Turn ray tracing and both motion blur options off
World motion blur and weapon motion blur are separate settings. Ray tracing is the largest frame cost in the game and buys you nothing in multiplayer.
- 3
Let shader pre-loading finish
Skipping it moves the compilation cost into your first matches, where it appears as hitching you will blame on something else.
- 4
Confirm the game is on an SSD with free space
An SSD is a hard requirement rather than a recommendation, and a nearly full drive slows down substantially. Keep 15-20% free.
- 5
Configure latency and presentation
Fullscreen Exclusive display mode, V-Sync off, NVIDIA Reflex at On + Boost, and a frame cap about three below your refresh rate.
- 6
On Intel 12th to 14th gen, constrain renderer worker threads
The renderer defaults to using efficiency cores as well as performance cores, which makes frames wait on the slower ones. Match the worker count to your P-core count and compare 1% lows rather than average FPS.
VRAM Scale Target: the setting that causes most Black Ops 7 stutter
Black Ops 7 ships with VRAM Scale Target set to around 90%, meaning the game will fill up to nine tenths of your graphics memory with streamed assets. On paper that maximises texture quality. In practice it leaves almost no headroom, and when the game needs to allocate anything unexpected - a new map area, a killcam, a UI transition - it has to evict assets first. You feel that as a hitch.
Lowering it to 60-70% costs you very little visible texture quality and eliminates a large share of the stuttering people otherwise attribute to their CPU or their drive. On cards with 8 GB of VRAM the difference is dramatic; even on 12 and 16 GB cards it flattens the frame-time graph.
Graphics settings for competitive multiplayer
| Setting | Recommended | Why |
|---|---|---|
| VRAM Scale Target | 60-70% | Leaves allocation headroom. The most effective anti-stutter setting in the game. |
| Ray tracing | Off | The largest single frame cost available. In multiplayer it buys you nothing at all. |
| Motion Blur (world and weapon) | Off | Costs frames and smears exactly the fast movement you need to track. Turn both variants off. |
| Display Mode | Fullscreen Exclusive | The lowest-latency presentation path. Borderless costs you a compositor step. |
| V-Sync | Off | Full frame of added latency. Use a frame cap with G-Sync or FreeSync instead. |
| Frame rate limit | About 3 below your refresh rate | Keeps you inside the VRR window and prevents the queue latency of hitting the ceiling. |
| NVIDIA Reflex Low Latency | On + Boost | Shortens the render queue. Boost helps specifically in the CPU-bound moments that dominate large multiplayer maps. |
| Upscaling (DLSS / FSR / XeSS) | Quality | Large gain, minimal softening. Match the technology to your GPU vendor and never run two at once. |
| Shadow quality | Low | Large GPU saving. Low shadows also make players in dark interiors easier to pick out. |
| Volumetric quality | Low | Smoke and atmospheric fog. Expensive, and it obscures targets. |
| Particle quality / resolution | Low | Where frame rate collapses during heavy firefights and killstreaks. |
| Texture resolution | One step below maximum | Combined with a lower VRAM Scale Target, this keeps you comfortably inside your memory budget. |
| Shader pre-loading | Let it complete | Interrupting it moves the compilation cost into your first matches, where it appears as hitching. |
Renderer worker threads on Intel hybrid CPUs
On Intel 12th through 14th generation processors, the renderer defaults to spreading work across every logical thread the CPU reports - which includes the efficiency cores. Those cores are considerably slower than the performance cores, so any frame that waits on an E-core finishes late. The average frame rate looks acceptable and the frame-time graph is spiky.
Constraining the renderer's worker count so it maps to your performance cores generally produces flatter frame times on these CPUs. This is configured in the game's own options file, which the game itself writes and reads - it is not a modification of game code.
- Identify your performance core count. Task Manager > Performance > CPU shows total cores; your CPU's product page lists the P-core and E-core split.
- Close the game completely before editing, or it will overwrite your change on exit.
- Set the renderer worker count to your P-core count, not your total logical thread count.
- Test across two matches and compare 1% lows, not average FPS - this change targets consistency, not peak.
- If it makes no difference, revert it. On AMD CPUs and on Intel chips without E-cores there is nothing here to fix.
System requirements people ignore
- An SSD is a hard requirement, not a recommendation. Black Ops 7 streams assets aggressively and a mechanical drive produces stuttering that no graphics setting fixes.
- Keep at least 15-20% of the drive free. Full SSDs slow down substantially, and a Call of Duty install is large enough to push a small drive there.
- Enable XMP or EXPO. Large multiplayer maps with many entities are memory-bandwidth sensitive.
- Set the Windows power mode to Best performance so cores are not parked between rounds.
- Disable Xbox Game Bar background recording - it holds GPU encoder resources.
- Close hardware-accelerated browser tabs and Discord streams before playing.
Frequently asked questions
How do I fix stuttering in Black Ops 7?
Lower VRAM Scale Target from its 90% default to 60-70% first - this resolves the majority of stuttering reports on its own by leaving the game allocation headroom in graphics memory. Then confirm the game is installed on an SSD, which Black Ops 7 requires, let shader pre-loading finish, and turn off ray tracing. On Intel 12th to 14th generation CPUs, constraining renderer worker threads to your performance cores also helps frame-time consistency.
What VRAM Scale Target should I use in Black Ops 7?
Between 60% and 70%. The 90% default fills almost all of your graphics memory with streamed assets, leaving no room for the allocations the game makes during map transitions, killcams and UI changes - and each of those becomes a visible hitch. Lowering it costs very little visible texture quality and produces a substantially flatter frame-time graph, especially on 8 GB cards.
Does Black Ops 7 need an SSD?
Yes, it is an official requirement rather than a recommendation. The game streams assets continuously and a mechanical hard drive cannot supply them fast enough, which produces stuttering that no graphics setting will fix. Moving the install to an SSD or NVMe drive is more effective than any amount of lowering settings.
Is it safe to edit the Black Ops 7 config file?
Editing the options file the game itself writes and reads is normal use of the settings the game exposes. Editing anything else inside the game directory is not, and modern Call of Duty titles run kernel-level anti-cheat that checks file integrity. If you are unsure which file is which, stay in the in-game menu - the VRAM Scale Target change available there is worth more than the worker-thread tweak anyway.
WRITTEN BY
Frost Live
Frost Live is the founder of Frozen Tweaks and the creator behind the FrozenTweaks optimization guides. He has spent years testing Windows, GPU driver and in-game settings on competitive titles including Counter-Strike 2, Valorant, Fortnite, Apex Legends and Call of Duty, and turned the tweaks that survived that testing into the Frozen Tweaks optimizer.
Related guides
Read this guide as plain markdown
Stop re-doing this after every update
Frozen Tweaks applies the system-level optimizations in our guides, logs every change so you can roll any of it back, and re-applies your configuration after Windows and driver updates revert it.
Download Frozen Tweaks