PC troubleshooting
Fortnite Settings Not Saving: Files, Restart and Rendering Mode
Find out why Fortnite settings reset on PC. Check GameUserSettings.ini permissions, renderer launch options and the result after a normal restart.
By FortRift Editorial Team · Published and checked · 3 min read
Quick answer
First identify what resets: several local settings, one rendering mode or an account preference. On Windows, Epic recommends checking whether GameUserSettings.ini is read-only. A renderer that reverts has a separate launcher-options fix. Save one change, restart normally and check the actual value before changing anything else.
A renderer change needs its own restart check.
Inspect the specific settings file before resetting a whole folder.
A Windows file fix does not apply to a console.
| What resets | Useful first check | How to confirm |
|---|---|---|
| Several PC video settings | Read-only property of GameUserSettings.ini | Save one setting, exit and relaunch |
| Rendering mode only | Existing launcher arguments and Epic's renderer guidance | Read the active mode after restarting |
| Settings after a crash | Whether the game exited normally | Compare one normal exit and relaunch |
| A console or account preference | Correct device and account | Avoid applying a Windows file procedure |
Record one setting that actually changes
Write down the setting, its original value, the value you choose and what appears after relaunching. Apply the change, exit the game normally and reopen the same account on the same PC. This is our diagnostic comparison; it does not claim that a crash is always the cause of a reset.
If only the rendering mode reverts, skip to that specific section. If a setting is greyed out or unavailable, record that as a different symptom. A setting that cannot be selected and one that fails to remain saved need different evidence.
Check the Windows settings file
Close Fortnite. Open %localappdata% in Windows, then FortniteGame → Saved → Config → WindowsClient. Open Properties for GameUserSettings.ini and clear Read-only if selected, then apply. This is the file-property check documented by Epic; it does not require deleting the file or downloading a replacement configuration.
Reopen Fortnite, change one harmless preference and repeat the normal exit-and-relaunch test. If the file is absent, confirm the Windows user and path rather than creating a guessed file. Keep a record of the setting you tested so you can tell whether the permission change helped.
If only rendering mode reverts
Epic documents these launcher argument sets: DirectX 12 uses -d3d12 -sm6; Performance uses -d3d12 -FeatureLevelEs31. Choose the set for your intended renderer; do not combine both or leave conflicting renderer flags from an old guide. Copy the existing field to a private note before replacing it.
In the Legacy launcher, find Fortnite under Settings and its Additional Command Line Arguments field. In Preview, use the game's Library menu → Manage → Launch Options. Follow the current official article linked below if your interface differs. Launch the game and inspect Rendering Mode before comparing performance.
Separate saving a mode from choosing the best mode
A mode staying selected proves that the persistence check passed. It does not establish that the mode is fastest or most stable on your hardware. Use the same scene and resolution when comparing options in our PC settings guide.
If the game closes before you can confirm the setting, move to the crash checklist. Repeatedly changing a configuration while a separate crash continues makes it harder to tell which problem you are solving.
When the change keeps coming back
Compare with any optional configuration or optimisation application you already use closed. Treat this as a controlled test, not proof that a particular application is responsible. Do not edit several files at once. Note whether the read-only property changes again or whether only the game's displayed value changes.
For support, provide the setting name, Windows version, launcher interface, current renderer arguments and your before/after observation. Share account information only through the official private support flow. A useful report states exactly which persistence test failed.
Your next steps
- Record the setting and its before-and-after values.
- Test Apply followed by a normal exit and relaunch.
- For local Windows settings, inspect GameUserSettings.ini's Read-only property.
- For a renderer-only reset, use the current Epic launcher instructions.
- Confirm the active setting and report a reproducible remaining failure.
Frequently asked questions
Should I delete GameUserSettings.ini first?
Start with the documented Read-only check and a single-setting retest. Deleting configuration resets preferences and is a separate troubleshooting action.
Why does Performance mode return to another renderer?
Inspect existing launch arguments and Epic's rendering-mode persistence instructions. Confirm the active mode after restarting; selecting it once is not the same test.
Can I use this Windows path on PS5 or Xbox?
No. The local file procedure is for Windows PC. A console issue should be investigated through its own settings and account context.
Does making the file read-only preserve my settings better?
Epic recommends clearing Read-only when settings fail to save. Forcing that property can prevent the game from writing subsequent changes.