Best 7 Fortnite Custom Resolution Tools (2026 Tested and Ranked)

AlphaRes has the strongest safety profile of the dedicated utilities. The current v1.1.0 build registers zero detections on a VirusTotal cross-scan across more than sixty antivirus engines, the binary is a single 533 KB portable file with no installer, and the runtime behavior is limited to writing two configuration files in the user’s local data directory. There are no network connections, no process enumeration, no driver installs, and no kernel hooks. NVIDIA Control Panel and AMD Adrenalin are first-party and therefore inherently trusted, but they live at the driver layer and are out of scope for the Fortnite-config persistence problem. CRU is also clean on VirusTotal, but its driver-level scope and the risk of black-screening a display make it a heavier choice than the application-layer alternatives. Tools sourced from unmaintained GitHub mirrors or generic download portals should be avoided regardless of historical reputation; without current scan coverage and an active maintainer, the safety story cannot be verified.

Both tools target the same problem and both write the resolution into the same Fortnite config file. The decisive difference is the read-only lock step. AlphaRes flips the Windows read-only attribute on GameUserSettings.ini as part of the apply step, which means Fortnite cannot rewrite the file on its next launch and the custom resolution survives every patch in the chapter. Forknife performs the resolution write but does not include the lock step in its standard workflow; the user has to set the read-only attribute manually through File Explorer Properties to get the same persistence. AlphaRes also has a faster recent update cadence and a published cross-scan history. Forknife remains a credible second choice for users who already have it installed and are comfortable adding the manual lock step, but new installs typically settle on AlphaRes for the zero-touch persistence. The full head-to-head with twenty-two compared aspects is at the AlphaRes vs Forknife guide linked above.

CRU itself has not been associated with Fortnite bans, and Easy Anti-Cheat does not flag it as a cheat or a code injector. CRU operates at the EDID and registry layer, not at the game-process layer, so it does not touch the Fortnite executable, the Easy Anti-Cheat module, or any process memory associated with either. The risk with CRU is a different one entirely: a misconfigured custom timing can blank the primary display until a Safe Mode boot and a CRU reset script restores the original EDID block. That risk is real and not theoretical; the project’s own documentation includes a recovery utility specifically for that scenario. Players who want a Fortnite-specific stretched resolution rarely need CRU’s full capability; the application-layer methods (AlphaRes, Forknife, manual ini edit) cover the same outcome with zero display-init exposure. CRU is appropriate when a non-standard refresh rate or a non-standard timing has to be added at the monitor level, not for routine Fortnite resolution changes.

NVIDIA Control Panel and Fortnite operate at different layers. The Control Panel adds a custom resolution to the Windows display-mode list at the driver level, which makes the mode selectable in any application. Fortnite separately stores the active resolution selection inside GameUserSettings.ini in the user’s local data directory. When Fortnite ships a patch, the patch process frequently rewrites that config file, either to apply new default values or to migrate the schema for new settings. The rewrite reverts the active resolution to a default selection, even though the custom mode is still defined and selectable in Windows. The fix from the NVCP side is to reopen Fortnite’s video settings and reselect the custom resolution after each patch. The fix from the AlphaRes side is the read-only attribute, which prevents the rewrite at the file-system level so the custom resolution stays selected across every patch in the chapter.

The manual ini edit is permanent only if the read-only attribute is set on the file after the edit. Without the read-only flag, Fortnite rewrites the file on the next patch (or sometimes after a settings reset triggered by a crash) and the custom values are lost. The full manual procedure has two steps: edit the ResolutionSizeX and ResolutionSizeY values in Notepad and save the file, then right-click the file in File Explorer, choose Properties, tick the Read-only checkbox at the bottom of the General tab, and click OK. With both steps done, the resolution survives every patch. AlphaRes automates exactly this workflow into a single click, which is why the tool exists; the manual route remains valid for players who want zero binaries on the system.

Every tool worth using is free. AlphaRes ships under the MIT license at zero cost. Forknife is free. CRU is free and donation-supported. NVIDIA Control Panel and AMD Adrenalin come bundled with the GPU drivers at no additional cost. The manual GameUserSettings.ini edit method requires no software at all beyond Notepad, which is built into Windows. The category to be careful with is the “free with bundlers” pattern, where the tool itself is free but the installer offers to install a browser extension, a system optimizer, or a toolbar alongside the resolution utility. Those bundlers are how the project is monetized and they are typically the source of the worst antivirus warnings on tools in the long tail. The five maintained options above all avoid that pattern; the “abandoned forks” category does not, which is the main reason it sits at the bottom of the ranking.

AlphaRes and CRU operate at different layers and solve different problems. AlphaRes is a Fortnite-specific application that writes a chosen resolution into Fortnite’s config file and locks it. CRU is a generic Windows utility that adds a custom resolution to the monitor’s reported display modes by editing the registry-stored EDID block, which the GPU driver reads at display init. CRU’s resolution becomes available system-wide; AlphaRes’s resolution is Fortnite-specific. CRU has no awareness of Fortnite and cannot prevent Fortnite from reverting its config; AlphaRes does exactly that. The two tools can coexist on the same system, with CRU defining the available display modes and AlphaRes locking Fortnite’s selection within them, but most players need only one or the other. For a Fortnite-only stretched resolution, AlphaRes is the right pick; for a system-wide custom mode that affects every application, CRU is the right pick.

Yes, with a small caution. The cleanest stack is a GPU panel (NVIDIA Control Panel or AMD Adrenalin) defining the custom mode at the driver level, plus AlphaRes locking Fortnite to a chosen resolution at the application level. The two layers do not fight each other because they touch different files and different system layers. Mixing AlphaRes and Forknife on the same install is redundant rather than harmful; both write the same two values to the same file, and whichever ran last wins. CRU on top of AlphaRes is the most aggressive stack and is appropriate only when a non-standard timing or refresh rate has to be added at the EDID level, which most Fortnite players do not need. The general rule is to use the smallest tool stack that produces the wanted result. For the vast majority of competitive Fortnite setups, that is AlphaRes alone or AlphaRes plus the GPU panel’s scaling option set to Full Panel.

AlphaRes itself is GPU-agnostic. It does not interact with the GPU driver at all; it writes Fortnite’s config file at the application layer, which works identically on NVIDIA, AMD, and Intel hardware. There is no need for an AMD-specific equivalent because the same binary handles both vendors. What AMD users sometimes confuse for an “AMD AlphaRes” is the AMD Adrenalin GPU Scaling feature, which is the AMD analog to NVIDIA’s Control Panel custom-resolution dialog. Adrenalin defines the custom mode at the driver level; AlphaRes locks Fortnite’s selection at the application level. The two layers stack: an AMD player who wants set-and-forget persistence runs Adrenalin to define the custom mode (if the wanted resolution is not already in Windows’ display-mode list) and then runs AlphaRes to write and lock that resolution into Fortnite’s config. Neither step is duplicated, and both contribute to the final outcome.

Pros optimize for time-on-task and predictability, both of which favor AlphaRes. The read-only lock removes the per-patch reapplication step, which on a typical Chapter 7 season is four to five wasted setup sessions a player no longer has to do. The single-binary footprint keeps the system clean for stream captures and tournament rigs that are reset between events. The clean cross-scan history makes the tool defensible if a tournament admin or anti-cheat audit asks what is running. The MIT license means the source can be reviewed if a sponsor’s IT requires it. None of those properties is unique on its own; AlphaRes wins on the combination. NVIDIA Control Panel is first-party but loses persistence; Forknife is close but lacks the lock step; CRU is powerful but heavyweight and risky. The default pro setup that minimizes tournament-day surprises lands on AlphaRes plus the GPU panel’s Full Panel scaling option, which is exactly the stack documented across the rest of this site.

Nothing breaks. NVIDIA Control Panel adds the custom resolution to Windows’ display-mode list at the driver level, and that mode remains available regardless of what AlphaRes does at the Fortnite-config layer. Installing AlphaRes after NVCP is the supported migration path for players who got the resolution working through the panel and now want patch-resistant persistence. The recommended workflow is to leave the NVCP custom resolution in place, run AlphaRes, set the same width and height in the AlphaRes interface, tick the read-only checkbox, and click Apply. Fortnite’s config is now locked to that resolution, and the NVCP-defined mode continues to be the underlying display mode the GPU is rendering into. If the NVCP mode is later removed, Fortnite will fall back to the closest available mode at next launch, but the AlphaRes lock prevents the config file from being rewritten by Fortnite itself.

The maintained tools (AlphaRes, Forknife, NVCP, AMD Adrenalin, CRU) all track Fortnite changes either through their own release cycles or through the GPU driver update channel. AlphaRes ships verified releases tied to Fortnite chapter rollovers; the current v1.1.0 build is Chapter 7 verified and does not need an update mid-chapter. NVCP and Adrenalin update with the GPU driver, which most players already do on Game Ready or Adrenalin Edition release schedules. CRU updates rarely because the EDID format does not change. The category that needs vigilance is the abandoned-fork tail: tools without a release in the past twelve months should be assumed broken on the current Chapter 7 build, even if they nominally still launch. The simplest safety check is to look at the project’s release history before installing; anything older than twelve months for a Fortnite-specific tool is a red flag.