How to Install XivAlexander on Windows (Portable vs Autoload)
XivAlexander is a standalone, open-source tool for Final Fantasy XIV that adjusts animation-lock timing on your own computer. It is not a Dalamud plugin, and you do not install it through a plugin installer. There are two ways to run it: portable mode, where you start the loader yourself each session, and autoload mode, where it starts automatically with the game. Portable mode is the better first choice for most players, because it is easier to remove and easier to test. This guide covers both, for the latest stable release, v1.14.9.3, on Windows 10 or 11, 64-bit only.
Before you start, confirm your system matches the requirements. XivAlexander v1.14.9.3 is Windows x64 only; the older 32-bit build was removed in this release. You need a normal FFXIV installation, the Visual C++ Redistributable packages that the game itself already requires, and a folder where you can extract files without Windows blocking them. Avoid extracting the tool into the game folder unless you are deliberately setting up autoload, and keep the extracted folder in one place so you can find the loader and the configuration file later.
Step 1: Download the stable release and verify it
Get v1.14.9.3 from the download page. The release file is XivAlexander_1_14_9_3_1bbf146.zip, about 5.07 MB. Do not download a testing build for everyday play: the testing release that appeared after 1.14.9.3 is not the stable release, even if its version number looks newer. Extract the zip into its own folder. Inside you should find XivAlexanderLoader64.exe, XivAlexander64.dll, and a configuration file. Before running anything, check the SHA-256 hash against the value on the download page, following How to Verify XivAlexander SHA-256 After Download. If the hash does not match, delete the file and download it again from the GitHub release, not from a re-upload.
Step 2: Portable mode (recommended first)
Portable mode leaves your game installation untouched. There are two routines, and both end with the loader attached to the running game. In the first routine, start FFXIV normally, log in, and then run XivAlexanderLoader64.exe and follow the loader prompts to apply it to the running game. In the second routine, run the loader first and then log in through the official launcher. Use only one routine at a time. When you close the game, the attachment ends. Nothing is left running in the background, and the next time you play without the loader, the game behaves exactly as it did before.
Step 3: Autoload mode (only if you want it every session)
Autoload mode is for players who have tested portable mode and want XivAlexander to start with the game automatically. The loader provides a setup option for automatic loading; use that option rather than copying files by hand if it is available to you. The manual method, described in the original documentation, is to copy XivAlexander64.dll into the game installation folder and rename the copy to d3d11.dll or dxgi.dll so the game loads it at startup. That manual method is also how conflicts with ReShade or GShade arise, because those tools use the same file names, so read XivAlexander with ReShade and GShade before you combine them. After any install, update, or uninstall step, restart a running game; changes do not reliably take effect on a game that was already open.
First-run checks
- Open the loader dashboard and confirm it reports the game as attached, rather than assuming it worked because the game opened.
- Test on a training dummy with a rotation you know well, and compare how weaving feels with and without the tool, as described in How to Check If XivAlexander Is Working.
- If your antivirus flags the loader, do not simply disable protection. Read XivAlexander Antivirus False Positive first, and verify the hash before adding any exclusion.
- If the loader cannot find your game, see XivAlexander Loader Cannot Find Game.
- If you later want the tool gone, follow How to Uninstall XivAlexander Completely instead of just deleting the folder while autoload is still configured.
Common mistakes
The most common mistakes are running a testing build as if it were stable, installing on a 32-bit system, extracting the zip into a temporary folder that gets cleaned up, and leaving autoload configured while also running the portable loader, which creates confusion about which copy is active. Another mistake is judging the tool after one dungeon run on a bad connection. XivAlexander changes animation-lock timing; it does not change your ping, your route to the data centre, or your rotation. If you are still clipping badly, work through XivAlexander Still Clipping at High Ping to separate a network problem from an animation-lock problem.
Frequently asked questions
Do I need XIVLauncher or Dalamud to use XivAlexander?
No. XivAlexander is standalone. It can run alongside XIVLauncher and Dalamud, but it does not require them. See How to Install XivAlexander with XIVLauncher if you use that launcher.
Should I use portable or autoload?
Start portable. Move to autoload only after portable mode works reliably for you and you understand how to turn autoload off again.
What if a FFXIV patch breaks it?
Stop and read XivAlexander Not Working After a Patch. Do not force an old build or old opcode definitions onto a new patch.
Installed correctly, XivAlexander should be boring: the loader attaches, your weaving window feels consistent, and the game otherwise behaves normally. If anything feels unstable, revert to portable mode or remove the tool and diagnose one change at a time.
Important: Final Fantasy XIV prohibits third-party tools that inject code into the game client or alter its network behaviour. XivAlexander is an unofficial, community tool, not affiliated with Square Enix. Using it carries a risk of account restriction. This guide is for information only; decide for yourself whether that risk is acceptable, and never use a third-party tool on an account you are unwilling to risk.
