ElvUI Download for World of Warcraft

ElvUI download compatibility and installation checks

ElvUI download compatibility and installation checks should begin with the World of Warcraft client you actually launch, not only with an expansion name remembered from an older guide. ElvUI has its own release number, while every WoW branch publishes an interface number that addon metadata uses for compatibility. At the July 16, 2026 verification, ElvUI 15.18 listed Retail interface 12.0.7, Mists of Pandaria Classic 5.5.4, Classic Era 1.15.8 and TBC Anniversary 2.5.6. Showing those values together prevents a common mistake: treating a WoW patch number such as 11.2.0 as though it were an ElvUI version.

Before using the download button, complete the ElvUI download compatibility and installation checks by opening Battle.net and noting the selected game version. Retail, progression Classic and Classic Era can be installed side by side, and each has a separate Interface/AddOns directory. The same current archive can contain metadata for several supported branches, but WoW only reads addon files from the folder belonging to the active client. If ElvUI does not appear on the character-selection AddOns screen, checking that directory is more useful than immediately trying an older release.

Players using an archived client or private server need a different process. Start with the exact client build and then look for a verifiable historical Git tag. A filename from a forum post is not reliable version evidence. The version archive on this site links only to tags that can be matched to the public ElvUI repository and labels old builds as legacy or unsupported.

• Use the ElvUI download compatibility and installation checks for every supported live client.
• Match the client folder before copying addon files.
• Use a historical tag only when an older client genuinely requires it.

What the ElvUI download contains

The ElvUI download is a ZIP archive rather than a Windows or macOS installer. A working package exposes three directories: ElvUI, ElvUI_Libraries and ElvUI_Options. The main directory contains the interface modules, the libraries directory supplies shared code, and the options directory provides the in-game configuration interface. All three belong directly inside the selected WoW client's Interface/AddOns folder. Leaving one directory behind can produce missing settings, dependency warnings or Lua errors even when the main ElvUI entry appears enabled.

A GitHub tag archive normally adds an outer directory such as ElvUI-15.18. Open that wrapper before copying files. WoW needs to see a path like AddOns/ElvUI/ElvUI_Mainline.toc or the equivalent client TOC; it cannot discover the addon when the actual folders remain one level deeper. This directory-depth issue explains many reports that an ElvUI download was completed but nothing appeared in game.

ElvUI replaces major parts of the default interface, including action bars, bags, chat, maps, nameplates, tooltips and unit frames. It does not automatically include every font, WeakAura, media pack or third-party plugin shown in a community profile screenshot. Install the base package first, complete the initial setup and confirm that /ec opens the configuration panel before adding optional profile packs or companion addons.

Keep an ElvUI download current without losing profiles

A current ElvUI download matters most after a major WoW patch, because Blizzard interface changes can break calls used by older addon code. Check the Tukui release page or public repository when the game updates, when ElvUI reports an available version, or when reproducible Lua errors begin immediately after a client patch. This page records the last verified version and date so visitors can judge the freshness of the information instead of trusting an undated “latest” label.

Profiles normally survive an update because saved variables live under the WTF directory rather than inside Interface/AddOns. Even so, copy the WTF folder before a major update. Then close WoW, delete only ElvUI, ElvUI_Libraries and ElvUI_Options from AddOns, and copy the fresh directories from the new archive. Replacing the folders cleanly is preferable to merging files because a merge can leave obsolete modules that no longer exist in the current release.

If the interface fails after an update, disable optional ElvUI plugins and test the base package with a new profile. Confirm that all three core directories came from the same ElvUI download and were installed in the active client. Restoring the backup is safer than downloading an unverified older ZIP. The update and profile guides provide a more detailed recovery workflow for players who maintain several layouts or game branches.

Verify ElvUI after Battle.net moves the game

After a repair or game move, reopen the active client location from Battle.net and compare the executable path, three addon folder dates and displayed ElvUI version. This prevents a correct archive in an inactive WoW copy from being mistaken for a failed download.

Keep one verified ElvUI recovery archive

Store the confirmed package outside AddOns with the WoW branch, ElvUI tag and date in its name. Remove duplicate ZIP files only after important characters and profiles pass combat, group and reload checks.