ElvUI Download FAQ: Install & Compatibility Answers

Download and source questions

ElvUI is a complete WoW interface replacement maintained by the Tukui community. Use Tukui for the current packaged download and the public GitHub repository to verify source tags and issue history.

• The current verified release is 15.18.
• ElvUI is not a traditional installer or executable.
• A third-party mirror should not be called official without verifiable provenance.
• The current archive contains ElvUI, ElvUI_Libraries and ElvUI_Options.

Compatibility questions

Tukui release metadata lists supported interface numbers. As of the check date, ElvUI 15.18 lists 12.0.7, 5.5.4, 1.15.8 and 2.5.6, covering the current Retail and supported Classic branches represented elsewhere on this site.

Setup and command questions

Type /ec to open ElvUI configuration. On first login, complete the setup wizard before importing a profile. If another addon changes the same frames or bars, disable overlapping modules in one addon rather than letting both control the same UI element.

Dependencies and companion addons

The packaged ElvUI directories must stay together. Optional projects such as ElvUI Enhanced, Eltruism, profile packs, floating-combat-text addons or WeakAuras are separate downloads with their own compatibility requirements. Diagnose base ElvUI first before enabling companions.

ElvUI download FAQ for current version checks

This ElvUI download FAQ for current version checks begins with where the package comes from. Tukui is the first-party packaged distribution, while tukui-org/ElvUI is the public source repository. At the July 16, 2026 check, Tukui reported ElvUI 15.18 with a July 7 update date, and the repository included the matching v15.18 tag. Future visitors should compare that value with Tukui because “latest” is time-sensitive.

Use the ElvUI download FAQ for current version checks to keep addon releases separate from WoW patch and interface numbers. Tukui's metadata listed interfaces 12.0.7, 5.5.4, 1.15.8 and 2.5.6 for the current multi-client package. A query such as ElvUI 11.2.0 can therefore be ambiguous: it may refer to a WoW patch rather than an addon release. This site displays both number systems and avoids creating a file link when a requested version cannot be verified.

The ElvUI download FAQ for current version checks also confirms that ElvUI should be downloaded as a ZIP archive, not an executable installer. Direct historical links on this site resolve to real public Git tags and use a 15-second confirmation. A public tag proves source provenance but does not guarantee that an old build supports a current client.

ElvUI download FAQ for Retail, Classic and macOS

The current ElvUI archive can support several live branches because it includes shared code and client-specific TOC metadata. Installation location decides which client loads it. Retail normally uses _retail_/Interface/AddOns, progression Classic commonly uses _classic_/Interface/AddOns, and Classic Era uses _classic_era_/Interface/AddOns. Open the selected client's location from Battle.net instead of guessing.

ElvUI works on macOS because WoW addons use Lua and data files rather than Windows-only executable code. On a MacBook or iMac, use Show in Finder for the selected WoW client, extract the ZIP and copy ElvUI, ElvUI_Libraries and ElvUI_Options into Interface/AddOns. The same wrapper-folder and wrong-client mistakes that affect Windows installations can also occur on macOS.

Private-server compatibility is not implied by a live branch name. A server using 1.12, 3.3.5a or another historical client may require a legacy build or maintained fork. Match the documented interface and server requirements. Do not use the current package only because the server describes itself as Vanilla, Wrath or Mists of Pandaria.

ElvUI download FAQ about installation and dependencies

A correct installation contains three sibling addon directories: ElvUI, ElvUI_Libraries and ElvUI_Options. GitHub archives add an outer directory such as ElvUI-15.18; open that wrapper before copying files. WoW needs to find the TOC directly under the ElvUI directory. If the addon is missing at character selection, check the active client, folder depth and all three core directories.

The Libraries and Options directories are required parts of the core package. Optional projects such as Eltruism, ElvUI Enhanced, profile packs, SharedMedia, WeakAuras and floating-combat-text addons are separate. They can depend on particular ElvUI releases and should be enabled only after base ElvUI loads without errors. A profile import also does not install those dependencies automatically.

Type /ec to open ElvUI settings and /reload to reload the interface. Complete the initial setup before importing a profile. If an error appears, disable optional plugins, verify that all three core directories came from one release and test a clean profile. These checks preserve useful evidence before any saved variables are reset.

ElvUI download FAQ about updates, old versions and profiles

Profiles normally survive an update because ElvUI saves them under WTF rather than Interface/AddOns. Back up WTF, close WoW, delete only ElvUI, ElvUI_Libraries and ElvUI_Options, and copy the three fresh directories. Do not merge releases because removed files can remain. Do not delete WTF during a routine update because that resets profiles and many other addon settings.

Use an old version only when an archived client or controlled diagnostic requires it. Confirm a real public tag, match its TOC interface to the client and install all three folders from that tag. Searches for ElvUI 14.5, 14.1.2 or 5.16 do not automatically prove those official tags exist. The archive page explains unverifiable queries and links only to evidence-backed versions.

Export important ElvUI profiles before major changes and record the release, game branch, resolution, scale and required plugins. Community profile screenshots can depend on fonts, WeakAuras and media packs outside ElvUI. The practical conclusion of this ElvUI download FAQ is consistent across tasks: verify the source, choose the correct client, preserve WTF, keep core folders on one version and test base ElvUI before adding extensions.

Keep the downloaded archive outside Interface/AddOns after installation and label it with the source tag and verification date. If a later update fails, that record shows which package previously worked without mixing old and new folders. Reopen the active client location from Battle.net before restoring it, because a moved or duplicated WoW installation can make a correct rollback appear ineffective.