Last updated: May 2026. Verified on Fortnite Chapter 7 with AlphaRes v1.1.0 on Windows 11 24H2.
When Fortnite resets your resolution after every update, the cause is Epic Games’ configuration reconciliation logic, not a bug in your system or a flaw in your monitor profile. On every patch, and occasionally between launches, Fortnite scans GameUserSettings.ini, identifies any non-standard resolution values, and rewrites them to one of the recognized presets. Players who run a 1600×1080, 1440×1080, or any other custom stretched resolution see their carefully chosen values disappear within hours of the next chapter rollover.
The permanent fix is simple at the operating-system level: set the Windows read-only attribute on GameUserSettings.ini. When read-only is set, Fortnite’s update process attempts to overwrite the file but fails at the OS file-system layer, leaving the player’s chosen values intact. The fix can be applied automatically using AlphaRes, manually using PowerShell’s attrib command, or through the File Explorer Properties dialog. All three methods produce the same result: a configuration file that Fortnite cannot modify.
This guide covers the underlying cause, the read-only mechanism that defeats it, three procedures for applying the fix (AlphaRes, PowerShell, GUI), verification steps, and the recovery procedures for the rare cases where the fix is reverted. The information applies to Fortnite on Windows 10 and Windows 11. It does not apply to Mac, console, or Epic-streaming clients.
TL;DR Fix
- Cause: Fortnite’s update process rewrites
GameUserSettings.inion patches, replacing non-standard resolution values with recognized presets. - Fix: Set the Windows read-only attribute on
GameUserSettings.ini. Fortnite’s write attempt fails at the OS layer and your custom values survive. - Verification: Open the file in Notepad to confirm the resolution lines, then check Properties to confirm Read-only is ticked. Both must be true.
- Common pitfall: Running AlphaRes without administrator elevation. The resolution gets written, but the read-only flag fails silently and Fortnite resets the file on the next patch.
Why Fortnite Resets Your Resolution
Fortnite ships with a configuration reconciliation routine that runs during every patch installation and during certain game-launch sequences. The routine reads GameUserSettings.ini, validates each entry against the recognized schema, and overwrites any value Epic considers non-standard. Resolution values are at the top of that list. A custom ResolutionSizeX=1600 with ResolutionSizeY=1080 does not match any of the presets Epic ships with the game, so reconciliation rewrites both lines to the system desktop default, typically 1920x1080.
This is not a bug. It is a deliberate Epic engineering choice intended to prevent broken configurations after patches change the schema, after monitor changes, or after driver migrations. The same logic protects Fortnite from launching at 0x0 if a player ran the game on an older monitor and unplugged it. The unintended side effect is that legitimate competitive setups with stretched or custom resolutions are also overwritten.
The reconciliation runs most aggressively during patch installation, which is why the symptom presents as “resolution resets after every update.” It also runs during chapter rollovers (when the configuration schema gains new fields), after engine version bumps, and occasionally after a clean Fortnite reinstall. Between routine play sessions on the same patch, the file usually remains stable.
The Permanent Fix: Read-Only Attribute
Windows file systems support a read-only attribute that prevents any process from writing to a file, regardless of the process’s user privileges. When the read-only attribute is set on GameUserSettings.ini, Fortnite’s reconciliation logic attempts the standard sequence (open file for write, replace contents, close), and the open-for-write call returns an access-denied error from the kernel. Fortnite handles the error silently, the file remains unchanged, and the player’s custom resolution survives the patch.
This works because Fortnite does not try to clear the read-only attribute before writing. Most game engines do not, since clearing read-only on a user configuration file would be an unusual operation. Fortnite reads the file (which read-only does not block), attempts the write, sees the failure, and moves on without retrying.
The read-only attribute is stored in the file system’s metadata, not in the file contents. It survives normal file operations: copying, moving, antivirus scans that do not modify the file, and Windows updates. It does not survive a deliberate file deletion, a Fortnite reinstall that removes the entire WindowsClient folder, or a manual attribute clear from PowerShell or File Explorer.
Method 1: Use AlphaRes (Recommended)
AlphaRes is the canonical tool for applying and locking custom Fortnite resolutions. It writes the resolution values to GameUserSettings.ini and sets the read-only attribute in a single Apply action. This method is recommended for almost all players because it eliminates the most common error (forgetting to set read-only after a manual edit) and runs the entire procedure under elevation if launched with administrator rights.
Download AlphaRes v1.1.0
Get the verified binary from the official AlphaRes download page. The file is 533 KB, x64 only, and ships unsigned (SmartScreen will warn on first run, which is expected). Avoid clones at alphares.dev or alphares.info; they sometimes serve repackaged builds.
Run as Administrator
Right-click alphares_x64.exe and select Run as administrator. This is non-optional. Without elevation, the resolution write to GameUserSettings.ini succeeds, but the read-only attribute set fails silently because the file is owned by the current user but the attribute change is treated as a privileged operation under some Windows configurations.
Enter Width and Height
Type the resolution width into the Width field and the height into the Height field. Common competitive picks: 1600x1080 (balanced), 1440x1080 (maximum stretch), 1720x1080 (mild stretch). For non-stretched custom resolutions like 1024x768 retro setups, the same procedure applies.
Tick the Read-only Checkbox
This is the step most users miss. The Read-only checkbox controls whether AlphaRes sets the Windows read-only attribute on GameUserSettings.ini after writing the values. With it unchecked, AlphaRes writes the resolution but leaves the file writable, and Fortnite’s reconciliation logic rewrites the values on the next patch.
Click Apply
AlphaRes writes the resolution values, sets the read-only attribute (if checked), and closes the file handle. There is no confirmation dialog. Close AlphaRes and launch Fortnite. The resolution will apply on the next loading screen and persist across every future patch until the read-only attribute is manually cleared.
%LocalAppData%\FortniteGame\Saved\Config\WindowsClient\GameUserSettings.ini in File Explorer, right-click the file, choose Properties, and confirm the Read-only checkbox is ticked. If it is, the fix is applied and Fortnite cannot reset your resolution.
Method 2: Manual Command-Line Approach
For power users who prefer scripted workflows, the fix can be applied entirely from PowerShell using the built-in attrib command. This method is also useful when AlphaRes cannot be installed (for example on locked-down corporate workstations) or when a player wants to script the fix as part of a larger PC-setup automation.
The procedure has three steps. First, edit GameUserSettings.ini manually in Notepad to set the resolution values. Second, save and close the file. Third, run a single attrib command from an elevated PowerShell window to set the read-only attribute.
Open the Configuration File
Press Win+R, paste %LocalAppData%\FortniteGame\Saved\Config\WindowsClient\GameUserSettings.ini, and press Enter. The file opens in Notepad. If the file does not exist, launch Fortnite once and let it sit on the lobby for ten seconds, then close it. The file will be created.
Edit the Resolution Lines
Find ResolutionSizeX and ResolutionSizeY. Set them to your custom values, for example ResolutionSizeX=1600 and ResolutionSizeY=1080. Do the same for LastUserConfirmedResolutionSizeX and LastUserConfirmedResolutionSizeY if present. Save the file and close Notepad.
Lock with PowerShell attrib
Open PowerShell as administrator. Run attrib +R "$env:LocalAppData\FortniteGame\Saved\Config\WindowsClient\GameUserSettings.ini". The command sets the read-only attribute and returns silently. To verify, run (Get-Item "$env:LocalAppData\FortniteGame\Saved\Config\WindowsClient\GameUserSettings.ini").IsReadOnly; the output should be True.
The tradeoff against Method 1 is reliability of the manual edit. AlphaRes writes a structured set of fields including WindowMode and FrameRateLimit that have to be correct for the resolution to apply cleanly. Manual editing in Notepad gives full control but also exposes the user to syntax errors that prevent Fortnite from reading the file at all (in which case Fortnite generates a fresh default file and ignores the manually-edited one).
Method 3: Manual GUI Approach
For users who prefer File Explorer over the command line, the read-only attribute can be set entirely through the GUI. This is the slowest of the three methods but requires no installed software and no command-line knowledge.
Edit the File in Notepad
Navigate to %LocalAppData%\FortniteGame\Saved\Config\WindowsClient\GameUserSettings.ini, right-click the file, and choose Open with, then Notepad. Edit the resolution lines as described in Method 2. Save and close.
Open File Properties
Right-click GameUserSettings.ini in File Explorer and choose Properties from the context menu. The Properties dialog opens on the General tab.
Tick Read-only and Apply
At the bottom of the General tab, find the Attributes section. Tick the Read-only checkbox. Click Apply, then OK. Windows may prompt for administrator confirmation; click Continue. The file is now read-only and Fortnite cannot rewrite it.
Verifying the Fix Worked
Verification has two checks. Both must pass. If either fails, the fix is not in place and the resolution will reset on the next patch.
Check 1: Resolution values are written correctly. Open %LocalAppData%\FortniteGame\Saved\Config\WindowsClient\GameUserSettings.ini in Notepad. Find ResolutionSizeX and ResolutionSizeY. Both should show the custom values entered in AlphaRes (or via manual edit). If they show the system desktop resolution instead, the write step failed; re-run AlphaRes as administrator.
Check 2: Read-only attribute is set. Right-click the same file, choose Properties, look at the Attributes section on the General tab. Read-only must be ticked. If it is not, the lock step failed; re-run AlphaRes as administrator (Method 1) or run the attrib +R command (Method 2).
What to Do If the Fix Breaks
The read-only fix is durable but not unbreakable. There are three known scenarios where the attribute is reverted or the file is recreated. Each has a specific recovery procedure.
GameUserSettings.ini. The old file (with read-only set) is replaced by a fresh writable file.%LocalAppData%\FortniteGame\Saved\Config\WindowsClient\ to the antivirus exclusion list, then reapply AlphaRes. Disable any registry or attribute “cleaning” feature in optimizer tools.FortniteClient-Win64-Shipping.exe processes), then re-run AlphaRes as administrator and click Apply.Common Diagnostic Patterns
The exact failure mode of the resolution-reset bug points to which step of the fix is missing. Use this table to map the symptom you observe to the underlying cause and the corresponding fix.
| Cause | Diagnostic Check | Fix |
|---|---|---|
| Read-only attribute not set | Resolution reverts after every Fortnite patch. File Properties shows Read-only unchecked. | Run AlphaRes as administrator and tick the Read-only box, or run attrib +R on the file. |
| Read-only set but write failed | Resolution reverts immediately after closing AlphaRes. File contents still show desktop resolution. | Close Fortnite, re-run AlphaRes as administrator, verify file write before applying lock. |
| Settings menu won’t apply changes | In-game Settings menu shows the resolution but reverts when Apply is clicked. | This is correct behavior. The read-only attribute is doing its job. To change resolution, run AlphaRes again with the new values. |
| File deleted by chapter rollover | Resolution reset after a major Fortnite chapter update. File modification timestamp matches the update. | Reapply AlphaRes after the rollover. The new file accepts the lock cleanly. |
| Antivirus cleared attribute | Read-only flag clears on a schedule (daily, weekly) without Fortnite patches. | Add the WindowsClient folder to AV exclusions and reapply. |
| GPU scaling not configured | Resolution applies in GameUserSettings.ini but the screen image shows black bars or pillarboxing. |
Configure GPU scaling: NVIDIA Control Panel sets Scaling to Full-screen with Override; AMD Adrenalin sets GPU Scaling on with Full Panel mode. |
What NOT to Do
Common Mistakes
- Do not edit
GameUserSettings.iniwhile Fortnite is running. Fortnite holds a file handle that prevents the write from persisting. Close Fortnite first. - Do not run AlphaRes without administrator elevation. The resolution write succeeds, but the read-only attribute set fails silently. Right-click the executable and choose Run as administrator.
- Do not expect the read-only attribute to persist after a Fortnite reinstall. Reinstalling the Epic Games launcher or the Fortnite game removes the entire
WindowsClientfolder. Reapply AlphaRes after any reinstall. - Do not delete
GameUserSettings.inias a “fix.” Some forum posts suggest this. Deleting the file resets every Fortnite setting (audio, video, controls) to defaults and creates a fresh writable file that resets your resolution again. - Do not download AlphaRes from clone domains like alphares.dev, alphares.info, or alphares.app. These sometimes serve repackaged builds with adware. Use the verified official download page.
- Do not assume the in-game Settings menu can override the read-only file. Once read-only is set, the Settings menu cannot apply changes. To change resolution, run AlphaRes again.
FAQ
Why does Fortnite reset my resolution after every update?
Fortnite ships with a configuration reconciliation routine that runs during every patch installation. The routine reads GameUserSettings.ini, validates each entry against Epic’s recognized schema, and overwrites any value it considers non-standard. Custom stretched resolutions like 1600×1080 or 1440×1080 do not match the recognized presets, so reconciliation rewrites them to the system desktop default (typically 1920×1080). The fix is to set the Windows read-only attribute on the configuration file. With read-only set, Fortnite’s write attempt fails at the operating-system level and the custom values survive. The reconciliation runs only on patches and version-stamp changes, which is why the symptom presents as “resolution resets after every update” rather than after every launch.
Is this a Fortnite bug or intentional?
It is intentional. Epic’s reconciliation logic is designed to recover from broken configurations after schema changes, monitor disconnections, or driver migrations. The same code prevents Fortnite from launching at unsupported resolutions or with corrupted settings. The unintended side effect is that legitimate competitive setups with stretched or non-standard resolutions are also overwritten. Epic has not provided an in-game option to opt out of reconciliation, so the read-only attribute fix is the only reliable way to preserve custom resolutions across patches. The fix exploits a normal operating-system file attribute and does not modify Fortnite, the Epic launcher, or any anti-cheat boundary, which is why it is safe to use.
Why doesn’t editing the .ini file once work?
Editing GameUserSettings.ini in Notepad changes the file contents, but it does not change the file attributes. Without the read-only attribute set, Fortnite’s reconciliation routine has full write access to the file and overwrites the custom values on the next patch. The edit-then-launch sequence works for the current session because the values are read once at startup, but it does not survive the next reconciliation pass. The complete fix requires both steps: write the custom values, and lock the file with the read-only attribute. AlphaRes performs both steps in one Apply action; manual users must run attrib +R after the Notepad edit.
Does the read-only attribute survive Windows updates?
Yes, in normal cases. The read-only attribute is stored in NTFS metadata, not in any Windows-managed configuration store, so feature updates and quality updates leave it untouched. The attribute can be cleared by a deliberate file-system reset, by some third-party optimizer tools that “clean” file attributes, or by a Fortnite reinstall that deletes the entire WindowsClient folder. None of these are part of routine Windows updates. If a major Windows feature update (like 24H2) somehow disturbs the attribute, the verification procedure in this guide catches it: open File Properties and confirm Read-only is still ticked.
Will the fix survive a Fortnite reinstall?
No. A Fortnite reinstall (or an Epic Games launcher reinstall that removes Fortnite) deletes the entire %LocalAppData%\FortniteGame\Saved folder, including GameUserSettings.ini. The read-only attribute is a property of the file, so when the file is deleted, the attribute goes with it. After a reinstall, launch Fortnite once to let it create a fresh configuration file, then reapply AlphaRes (or the manual procedure) to lock the new file. The same applies to manual deletions of the file or the WindowsClient folder, which some forum posts incorrectly recommend as a “fix” for unrelated issues.
What if my antivirus or anti-cheat reverts the read-only flag?
Easy Anti-Cheat does not touch GameUserSettings.ini; the file is outside its protection boundary. Antivirus tools occasionally clear file attributes during scans, particularly older versions of Norton, McAfee, and certain CCleaner-style optimizer suites. If the read-only flag clears on a schedule that does not match Fortnite patches (for example daily or weekly), an antivirus or optimizer is the likely cause. The fix is to add %LocalAppData%\FortniteGame\Saved\Config\WindowsClient\ to the antivirus exclusion list, disable any “registry cleaner” or “attribute cleaner” feature in optimizer tools, and reapply AlphaRes. Windows Defender does not have this behavior and is safe to leave at default settings.
Can I use this fix without AlphaRes?
Yes. Method 2 (PowerShell) and Method 3 (File Explorer GUI) in this guide produce the same result as AlphaRes. The PowerShell command attrib +R "$env:LocalAppData\FortniteGame\Saved\Config\WindowsClient\GameUserSettings.ini" sets the read-only attribute after a manual Notepad edit. The File Explorer Properties dialog has a Read-only checkbox that does the same thing. The tradeoff is that manual editing exposes you to syntax errors that prevent Fortnite from reading the file at all, so AlphaRes remains the recommended path for most users. For scripted automation or locked-down corporate workstations where AlphaRes cannot be installed, the manual methods are the documented alternatives.
What if I want to change the resolution again later?
To change resolution after the fix is applied, run AlphaRes again. AlphaRes detects the read-only attribute, temporarily clears it, writes the new resolution values, and reapplies the read-only attribute, all in a single Apply action. No manual steps are required. If you are using the manual methods, run attrib -R on the file to clear read-only, edit the values in Notepad, save, then run attrib +R to relock. The Fortnite in-game Settings menu cannot change the resolution while read-only is set; this is the intended behavior of the fix and not a bug.
Does this fix work for resolutions other than stretched?
Yes. The fix is resolution-agnostic. The same read-only attribute mechanism works for retro 4:3 setups like 1024×768, ultrawide custom resolutions like 2560×1080, downscaled high-DPI rendering, or any value that does not match Epic’s recognized preset list. The reconciliation routine treats all non-preset values the same way: as candidates for overwrite. Locking the file with read-only blocks the overwrite regardless of the specific resolution. The only constraint is that your GPU and monitor must actually support displaying the chosen resolution; AlphaRes does not validate that part because it is outside the file-edit scope.
What about Mac or console Fortnite?
The read-only attribute fix is Windows-specific. Mac Fortnite stores configuration in a different path under ~/Library/Application Support and uses HFS+ or APFS attributes that work differently from NTFS. Console Fortnite (PlayStation, Xbox, Nintendo Switch) does not expose the configuration file to the user at all; resolution is fixed by the platform. AlphaRes is Windows-only by design. Mac players who want a stretched resolution have limited options, mostly involving display-side downscaling through a third-party utility. Console players cannot run stretched resolutions without external capture-card workarounds, which are unrelated to this guide.
Where to Go Next
Continue setting up your Fortnite stretched-res rig
- How to Apply a Stretched Resolution in Fortnite Using AlphaRes: the full five-step walkthrough with resolution recommendations and GPU scaling configuration.
- How to Install AlphaRes on Windows 10/11 (2026 Step-by-Step): SmartScreen handling, prerequisites, and first-launch verification.
- Will AlphaRes Get You Banned in Fortnite? Anti-Cheat Status: honest analysis of Easy Anti-Cheat compatibility and pro-player adoption.
- AlphaRes for Fortnite: Complete Guide (2026): the pillar reference covering features, install, safety, comparisons, and every cluster guide.