AlphaRes FAQ: Every Common Question Answered (2026)

The verified AlphaRes v1.1.0 binary lives on the official AlphaRes download page, which serves the x64 executable directly from the upstream release asset. The download page also lists the published SHA-256 hash so the file can be verified against tampering, the file size (533 KB), and the supported Windows versions (10 22H2 and 11 24H2 are both confirmed). Downloading from any other domain risks a clone build with altered behaviour, which is why every cluster article on this site links exclusively to the official download page rather than third-party mirrors. Hash verification takes one PowerShell command and is the cheapest insurance against a corrupted or modified binary.

AlphaRes ships as a single 533 KB executable with no installer, no MSI, no add-or-remove-programs entry, and no registry footprint. The download is the application. Double-click the EXE and the main window opens; close it and the application exits cleanly without leaving anything resident. The deliberate absence of an installer is part of the safety profile: a portable single-file tool has nothing to uninstall incorrectly, no service to leave running, and no registry hive to mis-edit. The full cold-start workflow including SmartScreen handling and first-launch verification is documented in the AlphaRes Windows install guide.

A short ASCII path with no spaces or Unicode characters is the safest choice. C:\Tools\alphares\ works for almost every setup. Avoid paths under OneDrive or any cloud-synced folder because the read-only attribute flip can interact badly with the sync agent and produce inconsistent state. Avoid paths inside C:\Program Files too, since AlphaRes is not an installed application and putting it there forces unnecessary admin elevation on every launch. The Downloads folder works for a one-time test but is not a good permanent home because browser sessions occasionally clear it. The install guide covers path recommendations in full.

For the standard workflow, no. AlphaRes writes to %LocalAppData%\FortniteGame\Saved\Config\WindowsClient, which is a per-user folder that does not require admin rights to modify. The tool launches without UAC elevation on a normal user account and applies its changes successfully. Admin rights become relevant only on hardened Windows installs where Group Policy locks down the user-data folder, or on systems where the read-only attribute flip is blocked at the policy layer. In those cases, right-clicking the executable and choosing Run as administrator resolves the issue. The install guide documents both flows.

Delete the executable. That is the entire uninstall procedure. Because AlphaRes has no installer, no registry keys, and no service, removing the file completes the removal. The only on-disk artifact of having used AlphaRes is the modified GameUserSettings.ini in the Fortnite config folder, which is the file the tool was supposed to write. To revert that file to its default state, clear the read-only attribute through Windows File Properties, then let Fortnite regenerate the file on the next launch. The clean removal experience is a direct consequence of the no-installer design and matches the install workflow in reverse.

Yes. AlphaRes v1.1.0 is verified working on Windows 10 22H2 and Windows 11 24H2. The tool calls only standard Win32 APIs that exist in both Windows generations, so the behaviour is identical across the two operating systems. Windows 10 users see the same SmartScreen prompt on first launch, the same UAC pattern, and the same INI write behaviour. Older Windows versions (Windows 7, Windows 8.1) are not officially supported because the upstream toolchain targets the modern Visual C++ runtime, but most readers asking this question are running 10 or 11. The install guide walks through both Windows generations.

Yes. AlphaRes v1.1.0 returns zero detections across all sixty-plus antivirus engines on VirusTotal, including Microsoft Defender, Kaspersky, BitDefender, ESET, and Sophos. The MIT-licensed source code is open and reviewable, and behavioural analysis confirms the tool makes exactly two file writes plus one attribute change before exiting. There is no networking code, no registry persistence, no driver, and no background process. The full security audit covering malware risk, account ban risk, and system stability risk is documented in the AlphaRes safety audit, with reproducible verification steps any reader can run on their own machine.

No documented bans across seven years of public use. AlphaRes does not inject into the Fortnite process, does not hook Easy Anti-Cheat, does not read game memory, and does not modify any file inside Epic Games or BattlEye directories. The tool writes a configuration file before the game launches and exits before the anti-cheat is loaded, which means the two never interact. Pro and tournament-prep players have used AlphaRes openly for years without bans. The full ban-risk analysis covering EAC compatibility, BattlEye behaviour, and the seven-year ban history sits in the ban-risk article.

No. Easy Anti-Cheat scans the running Fortnite process and the loaded module list for suspicious behaviour. AlphaRes is not loaded into Fortnite, does not inject, and does not run while Fortnite is open. EAC has nothing to scan. The configuration file AlphaRes writes (GameUserSettings.ini) is the same file Fortnite itself writes during normal use; the only difference is the resolution values inside it. EAC does not validate the contents of GameUserSettings.ini against expected values. The detailed EAC compatibility analysis is in the ban-risk article.

The warning is from SmartScreen, which is a reputation system, not the antivirus engine. SmartScreen displays the blue Unverified Publisher dialog for any unsigned executable that has not yet accumulated download reputation among Defender clients. AlphaRes ships unsigned because Extended Validation code-signing certificates cost three to six hundred US dollars per year and are impractical for a free utility. The warning is the expected first-launch behaviour and does not contradict the clean VirusTotal result. The full SmartScreen mechanism plus the safe bypass is documented in the safety audit.

No. SmartScreen is a publisher-reputation gate, not a malware detector. The warning fires for any unsigned binary below a reputation threshold, which includes most free indie utilities at first launch. Microsoft’s own documentation confirms the gate is independent of the malware-scanning layer that runs separately in Defender. A clean VirusTotal scan and a SmartScreen prompt are not contradictory; the two systems answer different questions. The malware question is settled by the antivirus result; SmartScreen is only commenting on whether the publisher has a track record. The mechanism is explained in detail in the safety audit.

A narrowly-scoped file-level exclusion is safe and sometimes necessary. Defender’s machine-learning classifier occasionally re-quarantines small unsigned utilities even after the user has restored them, because the statistical pattern of the binary overlaps with some malware families. Adding the AlphaRes executable as a file exclusion (not a folder exclusion) prevents the cycle. Disabling Defender entirely is not advised; the exclusion targets only the AlphaRes binary and leaves the rest of the system fully protected. The full whitelist procedure including PowerShell automation is in the Defender whitelist guide.

AlphaRes performs two operations. First, it writes the ResolutionSizeX, ResolutionSizeY, FullscreenMode, and optional FrameRateLimit keys into GameUserSettings.ini under %LocalAppData%\FortniteGame\Saved\Config\WindowsClient. Second, if the read-only checkbox is ticked, it sets the Windows read-only file attribute on the INI file via the Win32 SetFileAttributes API. The combined effect is that Fortnite reads the custom resolution from the INI on launch, and Fortnite’s own update process is unable to overwrite the resolution because NTFS refuses the write. The mechanism is explained in plain English in the stretched resolution definition.

The read-only attribute is an NTFS file flag that instructs Windows to refuse write attempts against a file. When AlphaRes sets the flag on GameUserSettings.ini, the operating system itself blocks any process from modifying the file, including Fortnite during a patch. The protection is enforced at the filesystem layer, which is why it works without any background process or scheduled task running. The attribute persists across reboots, across Windows updates, and across Fortnite patches until something explicitly clears it. The full deep-dive on the mechanism is in the read-only lock guide.

No. AlphaRes does not touch the NVIDIA Control Panel, AMD Adrenalin, Intel Graphics Command Center, or any GPU-vendor configuration store. The tool only writes to a Fortnite configuration file. The GPU still negotiates its own scaling behaviour at the driver level, which is why some users see black bars after a stretched resolution change; that is a GPU scaling setting, not anything AlphaRes did. The desktop resolution remains unchanged after AlphaRes runs, and other applications continue to use whatever resolution Windows reports for the primary display. The driver-level alternative paths are compared in the NVCP comparison.

One file: GameUserSettings.ini located at %LocalAppData%\FortniteGame\Saved\Config\WindowsClient\GameUserSettings.ini. This is Fortnite’s own user-configuration store and is the same file the in-game settings menu writes to when the player changes any video option. AlphaRes touches the four resolution-related keys and leaves every other setting (input bindings, audio, accessibility, language) exactly as Fortnite wrote them. There is no second file, no shadow copy, no backup written elsewhere, and no temporary file left behind. The full inventory of what the tool reads and writes is documented in the safety audit.

The difference is the persistence layer. Manual INI editing writes the resolution successfully but does nothing about the read-only attribute, which means Fortnite overwrites the resolution on the next patch and the player has to repeat the edit. AlphaRes performs the same INI write and then flips the attribute in one click, locking the resolution against future patches. The manual approach also exposes the player to typos that can corrupt unrelated settings, while AlphaRes only touches the four resolution keys. The full method comparison is in AlphaRes vs Manual INI Edit.

Fortnite’s update process rewrites GameUserSettings.ini when certain patches modify the configuration schema. Without the read-only attribute, the rewrite includes the resolution keys and any custom values the player set are silently replaced with whatever Fortnite considers the default for the current monitor. The behaviour is not malicious; it is the standard schema-migration pattern used by many games. The fix is to lock the file so the rewrite cannot occur, which is exactly what AlphaRes does. The full root-cause explanation and the permanent fix are documented in the resolution reset fix guide.

Three resolutions cover the overwhelming majority of competitive use cases. 1600x1080 is the modern default for ranked play and balances horizontal stretch against FOV compression. 1440x1080 is the classic four-by-three derivative used at scrim and tournament prep where maximum model width is the goal. 1750x1080 is the gentle option for players new to stretched resolution who want a small visibility boost without the full FOV trade. The full ranked list with FPS uplift, FOV impact, and pro adoption rates is in the Chapter 7 stretched resolutions guide.

Yes, most competitive Fortnite pros run a stretched resolution. The exact split varies by region and event, but a publicly tracked majority of FNCS-tier and Cash Cup players use either 1600x1080 or 1440x1080 at the time of writing. The motivation is a combination of slight FPS uplift on demanding rigs, larger player-model width for build-fight visibility, and the muscle-memory advantage of running the same resolution across thousands of hours of practice. The current pro list with names, configurations, and team affiliations is in the Fortnite pro stretched resolution list.

Yes, but the size of the boost depends heavily on whether the system is GPU-bound or CPU-bound. On a GPU-bound rig (the bottleneck is the graphics card), reducing horizontal pixel count from 1920x1080 to 1600x1080 typically yields a ten to fifteen percent FPS uplift in Fortnite Performance Mode. On a CPU-bound rig, the uplift is smaller because the CPU is rendering the same number of game objects regardless of pixel count. Players on lower-tier GPUs see the largest gains. The full per-GPU benchmark data is in Does Stretched Resolution Boost FPS.

Yes. Fortnite measures field of view diagonally and adjusts horizontal FOV based on the rendered aspect ratio. Switching from native 1920x1080 (16:9, hFOV around 106 degrees) to 1600x1080 (around 4:2.7, hFOV around 96 degrees) reduces horizontal FOV by roughly ten degrees while keeping vertical FOV constant. The trade is more pixels per visible enemy in exchange for less peripheral visibility, which is the core argument for and against stretched resolution. The full per-resolution FOV measurements are in Stretched Resolution FOV in Fortnite.

For a 240Hz panel paired with a midrange GPU (RTX 4060 to RTX 4070 class), 1600x1080 is the practical sweet spot because it sustains the 240 FPS frame ceiling more consistently than native while keeping FOV compression moderate. Higher-end GPUs (RTX 4080 and above) can run native 1920x1080 at 240Hz without issue and have less to gain from the resolution swap. Lower-end GPUs benefit from the more aggressive 1440x1080 at 240Hz. The full per-refresh-rate guidance is in Best Stretched Resolutions for 240Hz and 360Hz.

On a sub-60-FPS rig (GTX 1050, integrated graphics, older laptop GPUs), 1280x1080 or 1440x1080 deliver the largest measured FPS uplift because the rig is heavily GPU-bound and pixel count translates almost linearly into frame rate. The FPS gain at this tier can reach twenty-five to forty percent compared to native 1920x1080, which is the difference between an unplayable build fight and a playable one. The trade-off in FOV is more painful on a small monitor but the FPS gain usually outweighs it. The full low-end recommendations are in Best Stretched Res for Low-End PCs.

It depends on the desired internal render resolution. On a 1440p panel, running stretched values like 2304x1440 or 2133x1440 produces the same visibility benefit at native panel pixel count, while running classic 1600x1080 on a 1440p panel forces the monitor to upscale and adds blur. The cleaner approach on 1440p is to scale the stretched ratio up to match the panel rather than down. The same logic extends to 4K panels. The full guidance for higher-resolution panels is in Best Stretched Resolutions for 1440p and 4K.

Seven causes account for nearly every “AlphaRes will not open” report. SmartScreen blocking the launch is the most common, followed by Defender quarantining the binary, missing Visual C++ Redistributable, corrupted download, restricted user account, long path or special characters in the file location, and misconfigured compatibility mode. Each has a specific fix that takes under five minutes. The recommended diagnostic flow is to check SmartScreen and Defender first because they cover roughly seventy percent of cases. The full seven-fix walkthrough with symptom-to-fix mapping is in AlphaRes Will Not Open Fixes.

The most common cause is that the read-only attribute on GameUserSettings.ini was set on a previous run, AlphaRes is now trying to overwrite the file to apply new values, and Windows is refusing the write because of the existing attribute. The tool reports success but the changes do not actually land. The fix is to clear the read-only attribute through Windows File Properties first, then re-apply the new values, then re-tick the read-only checkbox. The full root-cause analysis and the permanent fix workflow are in AlphaRes Settings Not Saving.

If Fortnite is overwriting a resolution that AlphaRes set, the read-only attribute did not actually flip. The most common reason is that the user did not tick the read-only checkbox in AlphaRes before clicking Apply, which means the tool wrote the resolution but skipped the lock step. The second most common reason is that the attribute flip silently failed because of a hardened user account that lacks attribute-modification rights on the user-data folder. The fix is to verify the attribute via File Properties and run AlphaRes as administrator if it failed. The full diagnostic flow is in Fortnite Resets My Resolution After Update.

Black bars appear when the monitor or GPU is letterboxing the stretched resolution rather than scaling it to fill the panel. This is a GPU scaling setting, not an AlphaRes issue. The fix is to set the GPU driver scaling mode to Full Panel or Fill (the exact name varies by vendor) so the lower-pixel-count image stretches across the whole monitor. NVIDIA exposes this in NVIDIA Control Panel under Adjust desktop size and position; AMD exposes it in Adrenalin under Display; Intel exposes it in Graphics Command Center. The full per-vendor walkthrough is in Fortnite Black Bars Fix.

Windows 11’s display scaling behaviour interacts differently with stretched resolutions than Windows 10 did, and the symptom is usually a Fortnite window that renders the HUD and player models larger than expected. The cause is typically the per-application DPI scaling override or the system-wide scale factor not matching the rendered resolution. The fix is to right-click the Fortnite shortcut, choose Properties, navigate to Compatibility, and set the High DPI scaling override to Application. The full Windows 11 zoom fix flow is in Stretched Resolution Zoomed on Windows 11.

Crashes immediately after a resolution change usually trace to one of three causes: a stale DirectX shader cache that needs clearing, a Performance Mode interaction with the new render dimensions, or a GPU driver issue that surfaces only at non-native resolutions. The fix order is to clear the shader cache via Windows Storage settings, toggle Performance Mode off and back on inside Fortnite, and update the GPU driver. The full crash-after-resolution-change diagnostic flow with seven verified fixes is in Fortnite Crashes After Stretched Resolution.

AlphaRes locates Fortnite by walking the standard user-data path under %LocalAppData%\FortniteGame. If that folder is missing, redirected, or empty, the tool reports a detection failure. The most common causes are a Fortnite install in a non-default Epic Games launcher path, a folder redirection in a corporate or school profile, or a fresh Fortnite install that has not been launched yet (the user-data folder is created on first launch). Launching Fortnite once before running AlphaRes resolves most cases. The full six-fix walkthrough is in AlphaRes Not Detecting Fortnite.

Yes. The realistic substitute set includes Forknife (a richer-UI custom resolution tool), NVIDIA Control Panel custom resolutions (driver-level, NVIDIA-only), AMD Adrenalin GPU scaling (driver-level, AMD-only), Custom Resolution Utility (system-wide EDID-level), and manual editing of GameUserSettings.ini. Each tool fills a different scope. AlphaRes wins on the combination of Fortnite-specificity, lock persistence, cross-GPU compatibility, and minimal footprint. The full seven-tool ranked comparison with safety, persistence, FPS impact, and Chapter 7 compatibility scoring is in Best 7 Fortnite Custom Resolution Tools.

AlphaRes wins on lock persistence and footprint; Forknife wins on workflow surface. Forknife exposes a richer UI with named presets and quick-switching between configurations, which suits players who frequently swap between two or three resolutions. AlphaRes accepts a smaller workflow in exchange for the read-only attribute guarantee that survives Fortnite patches. For a player who picks one resolution and locks it for an entire chapter, AlphaRes is the cleaner pick. For a player who swaps resolutions weekly, Forknife reduces friction. The twenty-two-aspect head-to-head is in AlphaRes vs Forknife.

AlphaRes wins on cross-GPU compatibility, persistence, and Fortnite-specificity. NVIDIA Control Panel works only on NVIDIA cards, applies the resolution at the driver level so it reaches the desktop and other applications too, and can be wiped by driver updates. AlphaRes is vendor-agnostic, scoped to Fortnite only, and locked at the filesystem layer. NVCP is the right pick when a system-wide custom resolution is genuinely wanted; AlphaRes is the right pick when only Fortnite needs the resolution. The full method comparison is in AlphaRes vs NVIDIA Control Panel.

The two tools operate at different scopes. CRU writes EDID-level monitor configurations that affect everything Windows reports for the panel, including the desktop and any application that reads the monitor’s resolution list. AlphaRes writes Fortnite-specific INI keys that affect only the game. CRU is the right pick when the player wants a custom resolution available system-wide for screen recording, content creation, or other applications. AlphaRes is the right pick for the standard competitive Fortnite workflow where the desktop should remain at native and only Fortnite needs the stretched value. The full comparison is in AlphaRes vs CRU.

Use AlphaRes. The manual INI edit writes the resolution successfully but does nothing about the read-only attribute, which means Fortnite overwrites the resolution on the next patch. The player ends up repeating the edit every patch cycle, which is the recurring problem AlphaRes was built to solve. Manual INI edit also exposes the player to typos that can corrupt unrelated settings. The only legitimate niche for the manual approach is locked-down PCs where utilities cannot be installed at all. The full method comparison with persistence and error-risk analysis is in AlphaRes vs Manual INI Edit.

The Fortnite settings menu only exposes resolutions Windows reports as supported by the connected monitor, which means stretched values like 1600x1080 usually do not appear in the dropdown at all. Even when a custom resolution is selected via the dropdown, the value can be reset by patches that touch the configuration schema. AlphaRes bypasses both limitations: it writes the exact value the player wants regardless of whether Windows considers it a valid mode, and it locks the file against patches. The full reset-fix walkthrough that explains the dropdown’s limitations is in Fortnite Resets My Resolution.

Yes. AlphaRes is free under the MIT license. There is no cost, no trial, no premium tier, no upgrade prompt, no advertisement layer, and no telemetry. The download is the full application and remains the full application forever. The MIT license also makes the source code available for any third party to review, fork, or redistribute, which is part of the safety profile that the audit relies on. The full license breakdown including what “free” actually means in practice for streaming, content creation, and commercial use is in Is AlphaRes Free.

No. There is no paid tier, no premium edition, and no commercial fork sold by the upstream maintainer. Any website, store listing, or marketplace claiming to sell a paid AlphaRes build is misrepresenting the project; the only legitimate distribution is the free MIT-licensed binary served from the official download page. Players who encounter a paywall when trying to download AlphaRes should treat it as a red flag and source the binary from the official page instead. The licensing details are documented in Is AlphaRes Free.

Yes. The MIT license explicitly permits commercial use, modification, and redistribution. Streamers, content creators, esports organisations, and tournament hosts can use AlphaRes during paid streams, sponsored content, and event broadcasts without any licensing fee or attribution requirement beyond the standard MIT notice. The tool’s behaviour is identical regardless of how the player is using it, so a sponsored streamer running AlphaRes sees exactly the same experience as a casual player. The commercial-use specifics including the full MIT terms are in Is AlphaRes Free.

The MIT license is one of the most permissive open-source licenses in common use. It permits use, copy, modification, merging, publishing, distribution, sublicensing, and sale of the software, both for free and for profit. The only requirement is that the original copyright notice and license text are preserved in any redistribution. There is no copyleft clause, no requirement to share modifications, and no patent grant complications. For a player just running the tool, the practical effect is that there are no usage restrictions whatsoever. The full license analysis sits in Is AlphaRes Free.

The upstream maintainer has not published a public donation channel as of mid-2026. The project is maintained as a free MIT-licensed utility without monetisation, which is part of the trust profile the safety audit relies on (no monetisation pressure means no incentive to add telemetry, ads, or upsell flows). Players who want to support the broader stretched-resolution ecosystem are best served by sharing accurate information, reporting bugs through the project’s public communication channels, and avoiding the clone domains that misrepresent the tool. The honest editorial review of the project is in the AlphaRes 2026 review.