Valorant config.ini Tweaks: The Real FPS Boosters That Matter

Forget the endless forum threads filled with “miracle fixes” that do nothing. When it comes to squeezing more frames per second out of Valorant, the /config folder is often touted as a goldmine. In reality, most widely shared config.ini tweaks are either entirely overridden by in-game settings, are specific to older Unreal Engine versions, or offer negligible gains. Our goal today is to separate the signal from the noise: we’re diving into the GameUserSettings.ini and Engine.ini files to identify precisely which settings can provide a testable, measurable FPS increase or input latency reduction.

This isn’t about magical numbers; it’s about understanding the Unreal Engine 4 variables that Valorant uses and making informed adjustments. Before we touch anything, understand that while these modifications are generally safe and within the bounds of what the game engine supports, always back up your files first.

Locating Your Valorant Configuration Files

Your Valorant configuration files are stored in a specific location unique to your Windows user profile.

1. Press Windows Key + R to open the Run dialog.
2. Type %LOCALAPPDATA% and press Enter. This will open your AppData\Local folder.
3. Navigate through Valorant\Saved\Config\.
4. Inside this folder, you’ll see one or more folders with long alphanumeric names (e.g., 1234ABCD-5678-EFGH-IJKL-MNOPQRSTUVWX). These are your unique user IDs. Open the one corresponding to your primary Valorant account.
5. Within your user ID folder, you’ll find GameUserSettings.ini and Engine.ini. These are our targets.

Important: Before making any changes, copy both GameUserSettings.ini and Engine.ini to a safe backup folder. If anything goes wrong, you can easily restore them.

GameUserSettings.ini: The User-Facing Controls (Mostly)

The GameUserSettings.ini file primarily reflects the settings you adjust within Valorant’s in-game menus. For most users, changing these values directly here offers no benefit over using the UI, as the game will often overwrite them or interpret them identically. However, there are a few exceptions where granular control or bypassing UI limitations can make a difference.

Resolution and Scaling

• ResolutionSizeX=<width>
• ResolutionSizeY=<height>
• LastUserConfirmedResolutionSizeX=<width>
• LastUserConfirmedResolutionSizeY=<height>
• FullscreenMode=<0-2> (0=Fullscreen, 1=WindowedFullscreen, 2=Windowed)

These parameters control your display resolution. While you can set them here, it’s generally best to use the in-game display settings. Incorrect values can lead to display issues. The only advanced tweak related to resolution that actually impacts FPS is sg.ResolutionQuality.

• sg.ResolutionQuality=100.000000

This corresponds to your render scaling. Setting it to 100.000000 means the game renders at your native resolution. Lowering this value (e.g., 80.000000) will render the game at 80% of your resolution and then upscale it. This provides a significant FPS boost at the cost of visual clarity, making the image softer or blurrier. While accessible in-game, modifying it directly here can sometimes offer more precise control or ensure it sticks. For competitive play, 100.000000 is almost always preferred for maximum clarity, but if you’re desperate for frames on very low-end hardware, this is your most impactful single setting.

Frame Rate and V-Sync

• FrameRateLimit=0.000000 (or 60.000000, 144.000000, etc.)

This sets an absolute FPS limit. 0.000000 means uncapped. While the in-game settings offer specific caps, directly setting FrameRateLimit can be useful for consistency. Capping your FPS slightly above your monitor’s refresh rate (e.g., 144 FPS for a 144Hz monitor, or 240 FPS for a 144Hz monitor if your system can consistently achieve it) can reduce frame time variance and input lag compared to an uncapped, fluctuating framerate. Experimentation is key here for your specific setup.

• bUseVSync=False

This is critical for competitive play. V-Sync synchronizes your game’s frames with your monitor’s refresh rate to prevent screen tearing. However, it introduces input lag. For any competitive scenario in Valorant, bUseVSync must be set to False. This setting is also available in-game, but ensuring it’s False here removes any doubt.

Graphics Quality (Beyond In-Game “Low”)

Most sg.Quality settings (like sg.ViewDistanceQuality, sg.AntiAliasingQuality, sg.PostProcessQuality, sg.TextureQuality, sg.EffectsQuality) are directly controlled by the in-game graphics options. Setting them to 0 or 1 here will usually mirror the “Low” or “Medium” settings in the UI. However, a couple of specific settings can be pushed lower than what the UI allows, potentially yielding minor gains.

• sg.ShadowQuality=0
• sg.FoliageQuality=0

While Valorant’s in-game settings usually go down to “Low,” setting sg.ShadowQuality and sg.FoliageQuality to 0 might provide a fractional FPS boost by ensuring these elements are rendered at their absolute minimum detail or potentially disabled if the engine allows. In Unreal Engine, 0 often means “disabled” or “lowest,” while 1 is typically “low.” Test this on your system; the visual impact might be negligible, but any frame matters for some.

• bUseDynamicResolution=False
• bUseHDRDisplayOutput=False

Ensure bUseDynamicResolution is False. Dynamic resolution scaling automatically lowers your render resolution when FPS drops, which can cause jarring visual changes and input lag spikes. Unless you specifically want this feature for extreme low-end stability, keep it off. Similarly, bUseHDRDisplayOutput should be False unless you have an HDR-capable monitor and actively want to use HDR in Valorant. Disabling it saves minor processing overhead.

Engine.ini: Deeper Engine Optimizations

The Engine.ini file offers access to more fundamental Unreal Engine 4 console variables that aren’t exposed in the game’s UI. These are where more advanced and potentially impactful FPS and latency tweaks reside.

The [SystemSettings] Block

This section is where most performance-critical Unreal Engine variables are declared. If you don’t see a [SystemSettings] block, simply add it to the top of your Engine.ini file.

[SystemSettings]

Now, let’s add some potent tweaks.

1. r.Streaming.PoolSize=<value> This variable controls the size of the texture streaming pool in VRAM. Textures are loaded into this pool as needed.

   • Too Low: Can cause textures to constantly stream in and out, leading to stuttering and visual pop-in.
   • Too High: Can allocate too much VRAM that isn’t actually used, potentially starving other processes or causing issues if your GPU has limited VRAM.
   • Recommendation: A good starting point is to set this to roughly 25-30% of your GPU’s dedicated VRAM.
   • Concrete Example: For a GPU with 8GB of VRAM, you might set r.Streaming.PoolSize=2048 (2048MB = 2GB). For a 12GB VRAM GPU, r.Streaming.PoolSize=3072 (3GB) could be appropriate. Always monitor your VRAM usage (e.g., with MSI Afterburner) to find the sweet spot for your system. A common mistake is setting this to 0, which often means an automatic, potentially unoptimized value.

2. r.StaticMeshLODDistanceScale=<value> This scale factor determines how aggressively static meshes (like environmental objects, walls, etc.) switch to lower-detail Level of Detail (LOD) models as you move further away.

   • Higher Value (e.g., 2.0 or 3.0): Objects will switch to lower detail models sooner. This can significantly improve FPS, especially in complex areas, at the cost of some visual fidelity for distant objects.
   • Lower Value (e.g., 0.5): Objects retain higher detail for longer, reducing FPS.
   • Recommendation: Start with r.StaticMeshLODDistanceScale=2.0. If you need more frames and can tolerate the visual change, try 3.0.

3. r.ViewDistanceScale=<value> Similar to StaticMeshLODDistanceScale, but affects the general rendering distance of various objects.

   • Higher Value (e.g., 2.0): Reduces the overall view distance, rendering fewer distant objects or simplifying them more aggressively. Can boost FPS.
   • Recommendation: Pair r.ViewDistanceScale=2.0 with StaticMeshLODDistanceScale for a combined effect.

4. r.MaxAnisotropy=0 Anisotropic filtering improves the clarity of textures viewed at oblique angles. Setting this to 0 disables it completely, providing a small FPS boost at the cost of texture sharpness, especially on floors and walls in the distance. While Valorant’s art style is clean, disabling this can still offer minor gains.

5. r.DepthOfField.MaxSize=0 Disables depth of field effects. Valorant doesn’t heavily rely on cinematic depth of field during gameplay, but some agent abilities or specific visual cues might use it. Setting this to 0 ensures it’s off, potentially saving minor rendering cycles.

6. r.BloomQuality=0 Disables bloom effects (the glow around bright lights). Valorant uses bloom subtly. Disabling it can offer a minor FPS gain and a slightly “flatter” visual.

7. r.RefractionQuality=0 Disables refraction effects (e.g., light bending through glass or water). Valorant’s maps have minimal such effects during gameplay, so turning this off is a safe bet for a minor boost.

8. r.GTSyncType=2 This Unreal Engine variable relates to GPU-CPU synchronization.

   • 0: Default (often V-Sync based or automatic).
   • 1: CPU waits for GPU.
   • 2: GPU waits for CPU.
   • Recommendation: Setting r.GTSyncType=2 is often suggested in competitive Unreal Engine games for reducing input lag, as it can help the GPU not get too far ahead of the CPU. However, its impact can vary by system and might even cause minor frame dips on CPU-limited systems. Test this carefully. Combine with r.FinishCurrentFrame=0 for potentially lower latency.

9. r.FinishCurrentFrame=0 Another variable related to frame presentation. Setting this to 0 generally aims to reduce input latency by instructing the engine to not force the GPU to finish rendering the current frame before starting the next. This is a common “low latency” tweak for Unreal Engine titles.

10. r.LightMaxDrawDistanceScale=2.0 Increases the scale at which lights are culled (no longer rendered). A higher value means lights will disappear or simplify at a shorter distance, potentially improving FPS in areas with many light sources.

Example Engine.ini Configuration (Add to your file, or create [SystemSettings] if it doesn’t exist):

[SystemSettings]
r.Streaming.PoolSize=2048 ; Adjust based on your VRAM (e.g., 2048 for 8GB VRAM)
r.StaticMeshLODDistanceScale=2.0
r.ViewDistanceScale=2.0
r.MaxAnisotropy=0
r.DepthOfField.MaxSize=0
r.BloomQuality=0
r.RefractionQuality=0
r.GTSyncType=2
r.FinishCurrentFrame=0
r.LightMaxDrawDistanceScale=2.0

Debunking Common “Placebo” Tweaks

Many .ini tweaks circulated online for Unreal Engine games are either outdated, specific to other games, or simply do not apply to Valorant. Here are a few to disregard:

• bSmoothFrameRate=False (or True): This setting, often found in GameUserSettings.ini, is largely irrelevant for modern competitive games like Valorant. Its primary function was to smooth out frame rates in older Unreal Engine titles, but it’s often overridden by the in-game frame rate limiter or is simply not effectively utilized by Valorant’s engine implementation.
• MaxFPS= (or MinFPS=): These are often confused with FrameRateLimit. Stick to FrameRateLimit in GameUserSettings.ini for controlling your maximum FPS.
• bUseBackgroundLevelStreaming=False: This setting controls whether the engine streams levels in the background. While it sounds like it could reduce stutter, setting it to False can actually increase loading times or cause more noticeable hitches when transitioning between areas, as the engine might have to pause to load assets. Valorant’s optimized streaming usually handles this well by default.
• Tweaks related to specific DirectX versions or older rendering paths: Valorant uses DirectX 11. Many older Unreal Engine tweaks relate to DX9 or specific rendering features that are no longer relevant or optimized differently.

Testing Your Tweaks: The Crucial Step

Modifying config files without testing is like shooting in the dark. To confirm if a tweak actually matters for your system:

1. Backup first. (Yes, again!)
2. Apply one tweak at a time. Resist the urge to dump all suggested changes at once. This makes it impossible to identify which change had an effect (or caused an issue).
3. Use Valorant’s built-in performance graphs. Press Ctrl+F in-game to toggle the FPS counter and other performance metrics (like frame time, CPU/GPU usage).
4. Establish a benchmark. Play a custom game on a specific map (e.g., Ascent or Haven, known for varying complexity). Walk the same path, use the same abilities, look in the same directions. Note your average FPS and 1% Lows before any changes.
5. Re-test after each tweak. Compare your new FPS and 1% Lows to your benchmark. Look for consistent, measurable improvements, not just fleeting spikes.
6. Assess visual impact. Does the tweak significantly degrade visual quality to an unacceptable level for the FPS gain?

Remember, Valorant is a highly optimized game from Riot Games. Many of the “low-hanging fruit” optimizations are already handled by the in-game settings. The tweaks discussed here are for those looking for marginal gains or fine-tuning beyond the UI, often at the expense of minor visual fidelity or by adjusting how the Unreal Engine handles background processes.

Final Considerations

• Game Updates: Valorant patches (e.g., Patch 8.08, 9.0) can sometimes reset your GameUserSettings.ini and Engine.ini files to default values, or even invalidate specific tweaks if the underlying engine code changes. Always keep your backups and re-apply/re-test after major updates.
• Hardware Dependency: The impact of these tweaks is highly dependent on your system’s specifications (CPU, GPU, RAM, VRAM). A tweak that boosts FPS significantly on an older, CPU-limited system might have no noticeable effect on a high-end rig.
• Vanguard: Riot’s anti-cheat, Vanguard, monitors your game files. However, modifying these specific .ini files with legitimate Unreal Engine variables is generally considered safe and standard practice for performance tuning in many Unreal Engine games. Stick to the documented engine variables discussed here and avoid third-party tools that inject code or modify game binaries.

Optimizing Valorant isn’t about finding a single magic setting; it’s about making informed, incremental adjustments. By focusing on these specific GameUserSettings.ini and Engine.ini variables, you stand the best chance of actually improving your FPS and reducing input lag, rather than chasing placebo effects. Test rigorously, understand the trade-offs, and enjoy a smoother, more responsive Valorant experience.