What counts as an ElvUI addon?
People use “ElvUI addons” to describe three different things: the folders shipped in the ElvUI archive, optional plugins that extend ElvUI, and unrelated World of Warcraft addons that happen to share the same interface. Those categories have different download sources, update schedules and failure modes. Treating them as one package is a common reason for duplicate files, Lua errors or an ElvUI setup that appears to be missing after an update.
The base ElvUI package owns the interface framework, configuration panels, unit frames, action bars, chat, nameplates and many other modules. A plugin may add a skin, a preset, a layout, a profile workflow or an integration with another addon, but it does not automatically replace the base package. An external addon such as Details!, BigWigs or Plater is its own project even when an ElvUI skin or profile can interact with it.
Which ElvUI addon folders are required?
A normal current ElvUI archive contains three folders that should be kept together in the active client's Interface/AddOns directory. The outer ZIP or GitHub wrapper directory is not itself the AddOns folder. World of Warcraft should be able to see the TOC files directly under each addon folder.
Do not download one folder from a different release just because its name looks familiar. The base folder, libraries and options panel are versioned as one package. If you replace only one of them, the game may show missing options, dependency warnings or errors that look like a profile problem.
| Folder | Role | What to do |
|---|---|---|
| ElvUI | Main interface modules and saved settings | Install the folder from the selected release |
| ElvUI_Libraries | Shared libraries used by the base modules | Keep it beside ElvUI at the same release |
| ElvUI_Options | Configuration and in-game options panels | Install it with the base package |
| Outer ZIP wrapper | Archive container, not an addon | Do not copy the wrapper as the final folder |
Optional ElvUI plugins and companion addons
Optional plugins are useful when you want a theme, an installer, extra profile handling or a specific integration. ToxiUI is one example: it is a plugin and preset built on ElvUI, so it needs a compatible ElvUI base rather than replacing it. The ToxiUI guide records its separate release and installation requirements.
Companion addons are broader than ElvUI plugins. A damage meter, boss-mod addon, nameplate addon or media pack may have an ElvUI profile or skin, but it still has its own author, source and update process. Use the project's official site, GitHub, CurseForge or another clearly identified distribution page. Do not assume that a file is official because its filename contains “ElvUI”.
| Category | Example use | Install and update separately? |
|---|---|---|
| ElvUI plugin | Theme, preset or extra ElvUI module | Yes; match the plugin to the ElvUI version |
| Companion addon | Details!, BigWigs, Plater or another WoW utility | Yes; follow that project's release notes |
| Profile or media pack | Imported layout, fonts or textures | Usually; verify dependencies and backup first |
| Random repack | Unknown ZIP or executable from a mirror | No; do not use without verifiable provenance |
How to install ElvUI addons without a folder mistake
Close World of Warcraft before replacing addon code. If you already have a working layout, export the ElvUI profile and copy the WTF folder first. Saved variables normally survive a clean addon replacement, but a backup gives you a way back when a plugin changes a profile or a client folder is selected incorrectly.
For the base package, use the site's ElvUI installation guide for the Retail and Classic directory names. The key check is the final path: it should look like .../Interface/AddOns/ElvUI/, .../ElvUI_Libraries/ and .../ElvUI_Options/, not .../AddOns/ElvUI-v15.18/ElvUI/.
- 1
Choose one verified release
Use the current Tukui distribution or the matching public Git tag. Do not combine folders from different ElvUI versions.
- 2
Back up settings
Export the active profile and copy WTF before changing addon files. Keep the backup until the new setup has been tested in game.
- 3
Extract the archive
Open the ZIP and locate ElvUI, ElvUI_Libraries and ElvUI_Options. Remove only the outer wrapper level when the archive adds one.
- 4
Copy the three core folders
Place all three folders directly under the active Retail or Classic Interface/AddOns directory.
- 5
Add optional projects one at a time
Enable the base UI first, then add a plugin or companion addon separately so a new error has a clear cause.
Compatibility checks after installing addons
An addon can be technically installed and still be wrong for the client you launch. Check the AddOns screen at character selection, confirm that the correct Retail or Classic directory is active and read the dependency text before changing profiles. A missing entry usually points to path depth, a disabled folder or the wrong client branch rather than a corrupted profile.
If a Lua error appears after adding an optional project, disable the newest plugin first and reload. Then update the base ElvUI package and the companion addon from their own sources. This staged approach is more useful than deleting WTF or repeatedly merging old and new addon folders.
| Symptom | Likely cause | First action |
|---|---|---|
| ElvUI is not listed | Wrong client path or an extra wrapper folder | Check the active folder and final AddOns depth |
| Options are missing | ElvUI_Options is absent or from another release | Reinstall the three matching core folders |
| Lua errors after a plugin | Plugin or dependency is outdated | Disable the newest optional addon and update separately |
| Profile looks reset | A different profile was selected | Restore the exported profile before deleting saved variables |
| Frames overlap after an import | Scale, resolution or profile assumptions changed | Check UI scale and test a clean profile |
Updating or removing ElvUI addons safely
The safest update is a clean replacement of addon folders after a backup. The site's ElvUI update guide explains why you should replace old code instead of merging files from several releases. Keep WTF during a normal update because it contains saved variables; remove it only when you deliberately want to reset settings and understand the consequence.
When removing a plugin, switch to a normal ElvUI profile first, disable the plugin at the character screen and test the base UI. Then remove only that project's folders. If the theme or layout remains, the profile may still be selected even though the plugin code is gone. For profile backups and imports, use the site's ElvUI profiles guide.
- Keep one exported profile and one full WTF backup.
- Replace matching addon folders instead of merging old and new code.
- Update ElvUI, plugins and companion addons as separate projects.
- Test the base UI before enabling a large group of optional addons.
- Do not describe a mirror, repack or executable as official without a verifiable source.
ElvUI Addons FAQ
Does ElvUI include other WoW addons?
The ElvUI release contains its own core folders. Addons such as Details!, BigWigs and Plater are separate projects, even when an ElvUI skin or profile can integrate with them.
Do I need ElvUI_Libraries and ElvUI_Options?
Yes for a normal current installation. Keep ElvUI, ElvUI_Libraries and ElvUI_Options together from the same verified release and place them directly in the active AddOns folder.
Do I need ToxiUI to use ElvUI?
No. ToxiUI is an optional plugin and preset. Install the compatible ElvUI base first, and use ToxiUI only when you want its separate theme and companion-addon workflow.
Can I use other addons with ElvUI?
Usually, yes, but compatibility is project- and client-specific. Add one optional addon at a time, read its dependencies and disable the newest addition first when an error appears.
Why does ElvUI not appear in the AddOns list?
Check that you opened the correct Retail or Classic client folder, removed the outer ZIP wrapper and copied all three core folders directly under Interface/AddOns. Then restart the game.
Is ElvUI v15.18 the latest version?
It was the highest public tag verified on August 1, 2026, with a July 7, 2026 commit date. Version data can change, so check Tukui and the public repository before calling it current.
Sources and version check
The version context was checked against the official Tukui ElvUI distribution page and the public ElvUI v15.18 repository tag. The direct v15.18 source archive was checked as a ZIP download on August 1, 2026. Recheck those first-party sources before making a later version claim.