ElvUI Retail Download for World of Warcraft

Which ElvUI download works with Retail?

Use the current package from Tukui. You do not need a separate “Retail-only” archive: the distribution includes the ElvUI folders and the metadata needed by supported clients.

• Install into World of Warcraft/_retail_/Interface/AddOns.
• Confirm the three ElvUI folders are directly inside AddOns.
• Close WoW before replacing addon files.
• Keep the WTF folder because it contains your profiles and settings.

Retail installation checklist

1. 1

   Download the verified tag

   Click the download button and confirm the v15.18 public source archive.

2. 2

   Extract the archive

   Open the ZIP and locate ElvUI, ElvUI_Libraries and ElvUI_Options.

3. 3

   Copy to _retail_

   Move all three folders into the Retail AddOns directory.

4. 4

   Enable at character select

   Open AddOns, verify all three entries are enabled, then enter the game.

Retail update notes

Update ElvUI after a major WoW patch, when Tukui publishes a new release, or when the in-game version check reports that your package is behind. Delete the old ElvUI addon folders before copying the replacements; do not delete WTF during a normal update.

Verify the ElvUI Retail download before copying files

The ElvUI Retail download decision should be based on the current Tukui release metadata and the interface number used by the live Retail client. At the July 16, 2026 check, Tukui reported ElvUI 15.18, updated July 7, with Retail interface 12.0.7 in its supported patch list. The public repository also contains a matching v15.18 tag. Those two pieces of evidence connect the published release number to a stable source archive without relying on an expiring signed URL or an unexplained third-party mirror.

Retail changes frequently around expansion launches, pre-patches and major content updates. An article that only says “latest” can become misleading as soon as Tukui publishes another release. This page therefore displays the version, interface, update date and verification date together. Before installing later, compare the displayed value with the Tukui ElvUI page. If a newer release exists, use the newer supported package rather than the archived v15.18 link preserved in this build of the site.

The current archive supports several WoW branches, but the ElvUI Retail download does not need to be a separate Retail-only ZIP. Retail reads the mainline TOC metadata while Classic clients read their corresponding files. Correct installation location determines which metadata WoW sees.

Use the correct folder for an ElvUI Retail download

Battle.net can keep Retail and multiple Classic clients under the same World of Warcraft directory. The ElvUI Retail download belongs under World of Warcraft/_retail_/Interface/AddOns. It does not belong in _classic_, _classic_era_ or the top-level Interface directory. Use Battle.net's Show in Explorer or Show in Finder command for the selected Retail client to avoid editing a second installation left on another drive.

After extracting the ZIP, open its outer wrapper and copy ElvUI, ElvUI_Libraries and ElvUI_Options directly into AddOns. A correct path ends with a TOC file immediately inside the addon directory. If the result looks like AddOns/ElvUI-15.18/ElvUI/..., WoW cannot find it because the actual addon is nested one directory too deep. If only the main folder was copied, the configuration interface or shared libraries may fail even though ElvUI appears in the AddOns list.

Close WoW before replacing files and remove old ElvUI directories rather than merging the new archive over them. A clean replacement prevents obsolete modules from surviving an update. Keep WTF untouched because it contains account, realm and character saved variables.

Configure the ElvUI Retail download after first login

When the ElvUI Retail download loads for the first time, complete the built-in installation sequence before importing a community profile. The sequence applies recommended console variables, chat setup, UI scale and layout defaults. These choices establish a known base configuration. Type /ec to reopen the ElvUI settings window and /reload after changes that require a user-interface reload.

A profile string changes ElvUI settings but does not install every asset visible in a creator's screenshot. Fonts, textures, WeakAuras, SharedMedia packs, combat-text addons and optional ElvUI plugins remain separate dependencies. If an imported layout looks wrong, compare screen resolution and UI scale, then review the creator's dependency list. Do not downgrade the base addon merely because a profile created on another display does not align immediately.

Test essential interactions after setup: action bars should respond outside combat, unit frames should update, bags and maps should open, and the options panel should list modules without dependency errors. Run this test before enabling additional plugins. A clean base test makes later conflicts much easier to isolate.

Maintain the ElvUI Retail download through WoW patches

Retail interface updates can affect protected actions, unit-frame events, nameplates and Blizzard frame skins. Check for a new ElvUI Retail download after a major WoW patch and whenever Tukui announces compatibility work. Back up the WTF folder before a large transition, particularly if several characters share profiles or if the installation uses extensive plugin settings. An exported ElvUI profile provides an additional portable backup but does not replace a full WTF copy.

For a routine update, exit WoW, delete ElvUI, ElvUI_Libraries and ElvUI_Options from the Retail AddOns folder, and copy the three directories from the new package. Preserve WTF. On the next launch, verify the displayed version and test base ElvUI with optional extensions disabled if errors appear. Update extensions independently because their release schedules may differ from core ElvUI.

If a patch-day error remains with every optional plugin disabled, confirm the issue against Tukui release notes and the public issue tracker. Include the Retail build, ElvUI version and a reproducible error rather than only a screenshot. Returning to an old release should be a controlled diagnostic step, not the default response to a new game API.

Keep a short maintenance note beside the ElvUI Retail download archive with the verification date, installed version and any required plugins. That record makes it easier to distinguish a core update from a profile or extension change when troubleshooting later.

After the final test, remove duplicate ZIP files from the active AddOns directory and store one known-good archive outside the game folder. WoW ignores most ZIP files, but leaving installers and unpacked wrappers beside live addons makes later path checks confusing. Label the retained archive with the Retail build and date, then confirm that Battle.net still points to the same installation before the next update.