Fortnite Settings Not Saving: How to Fix Settings That Keep Resetting

Fortnite settings not saving, official Fortnite promotional artwork featuring Peely
Image credit: Epic Games.

Fortnite settings not saving can be especially frustrating when you spend time fixing your graphics options, sensitivity or keybinds only to find that everything has changed after restarting the game. On Windows PC, Epic Games documents a specific file permission problem that can stop Fortnite from retaining settings. The good news is that you can check it without reinstalling the game or deleting your configuration.

The best fix for Fortnite settings not saving depends on which options are resetting. If video settings return to their previous values every time you launch Fortnite, start with the local configuration file. If only controls change after an update, that may be a different issue. This guide explains how to identify the difference, apply Epic’s official Windows fix, test whether it worked and avoid losing an otherwise usable setup.

Why Fortnite settings not saving happens on PC

When Fortnite settings not saving affects a Windows installation, the most useful first check is the Read-only attribute on the GameUserSettings.ini file. Fortnite needs to be able to write its preferences there. Epic’s official support article tells players to remove that attribute before starting the game again. Make a note of a few current settings before changing anything, so you can compare the results after restarting.

Fortnite settings not saving, official Fortnite promotional artwork featuring Peely
Image credit: Epic Games.

How to fix Fortnite settings not saving in Windows

To troubleshoot Fortnite settings not saving in Windows, first close the game completely rather than leaving it running in the background. Press the Windows key, search for the Run app or use Windows and R together, then enter the local application data shortcut shown below. Open the FortniteGame folder, followed by Saved, Config and WindowsClient. Find GameUserSettings.ini, right-click it, choose Properties and clear the Read-only tick box if it is selected. Choose Apply, close Properties and launch Fortnite again.

To check whether Fortnite settings not saving has been resolved, change one easy-to-recognise option, select Apply where the menu offers it, then exit normally and reopen the game. If that option is still in place, you have evidence that the save path is working. Try a second setting before rebuilding your entire configuration. If the option immediately switches back or only certain categories reset, move on to the more specific checks below instead of repeating the same file change indefinitely.

What if you play Fortnite on console?

Fortnite settings not saving on a console needs a different approach because Epic’s file-permission fix is specific to the Windows PC path. Console players should not look for GameUserSettings.ini, and players using another device should not assume the same menu or storage location exists. It is safer to confirm the exact symptom, game version and platform before following a PC-only tutorial on PlayStation, Xbox, Nintendo Switch or mobile.

Rendering Mode and graphics options keep resetting

A setting that refuses to stick is not always the same thing as an entire configuration being lost. Rendering modes can require a restart before the change actually takes effect. If the game then launches with a different mode than the one selected, revisit the Windows file attribute before trying broader performance fixes. Our guide to Fortnite Performance Mode explains what that renderer is meant to do, while our Epic Quality Assets guide covers the separate installation option that players may confuse with an in-game graphics setting.

Controller sensitivity and keybinds are not saving

If Fortnite settings not saving mainly affects controller options, those preferences deserve a separate check. Start by confirming you are editing the appropriate controller options rather than a keyboard profile, and make sure changes are applied before leaving the settings screen. It is useful to record your sensitivity, deadzones and aim-assist values before troubleshooting. That gives you a baseline if the settings need to be entered again, particularly after a large update or a change of input device.

Epic has separately acknowledged instances of keybindings resetting after updates, which can affect actions such as reloading, building or interacting. Its published workaround is to manually adjust the bindings in Fortnite’s settings. Do not assume that changing Windows file permissions will solve every update-related keybind issue. If only a few actions stopped working while your video preferences were preserved, inspect those assignments first and follow the status of any known update issue.

Check individual audio and display settings

When Fortnite settings not saving only affects a visual audio indicator, double-check that the option was applied and is enabled in the Audio menu before diagnosing a broader save failure. The same principle applies to frame-rate displays and other toggles: verify one isolated option, restart once and establish whether the problem is a forgotten selection, a specific setting or all settings together.

Fortnite Tilted Town
Fortnite Tilted Town

Avoid losing a working configuration

If Fortnite settings not saving began suddenly across several options, note the date the problem started and whether Fortnite had recently updated. Avoid deleting the configuration folder as an early troubleshooting step. Removing existing files can discard custom preferences, and Epic states that it cannot restore a player’s previous settings after they have been reset. Keeping a written record or screenshots of values is therefore more useful than repeatedly restoring everything to defaults.

When the issue is actually low FPS

Players troubleshooting sluggish performance should also separate a saved configuration from an effective configuration. A setting might remain selected but still fail to deliver the desired frame rate because of hardware limits, thermal conditions or a separate performance bottleneck. Check the actual FPS and game behaviour before treating every stutter as evidence of Fortnite settings not saving. Our existing PC optimisation and FPS display guides are better starting points when preferences persist but performance is disappointing.

Further troubleshooting if nothing saves

If Fortnite settings not saving continues after the Read-only box has been cleared, check again after exiting Fortnite to see whether the same attribute returned. Record what changed, whether the problem affects all settings and whether an update happened immediately beforehand. On Windows, you can also use the Epic Games Launcher to verify installed Fortnite files if there are signs of broader game corruption, though file verification is not the same as a guaranteed fix for configuration permissions.

Be particularly cautious with third-party optimisation tools, one-click configuration packs or copied competitive settings. They can make it difficult to know which value is responsible for the result. Test with one deliberate setting change and one restart instead. If the problem began after applying a custom configuration, stop changing multiple variables at once and compare the current setup with the values you recorded.

Epic’s official instructions for this issue are available in What do I do if Fortnite doesn’t save my settings?. They identify the Windows configuration file and the exact Read-only check described above.

For someone experiencing Fortnite settings not saving on PC, the official Read-only check is a sensible starting point because it is precise, reversible and directly supported by Epic. If that does not resolve your symptoms, the distinction between video settings, input bindings and general game instability will guide the next step. The linked troubleshooting guides below cover those related issues without confusing them with this specific file permission fix.

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *