ElvUI Download for MoP Classic

How to install ElvUI for MoP Classic

Close the game, extract the current package and copy the three ElvUI addon folders into the progression Classic client's Interface/AddOns directory. Confirm the path in Battle.net if you maintain several WoW installations.

1. 1

   Select the MoP Classic client

   Use Battle.net's game version menu and open the install location.

2. 2

   Open Interface/AddOns

   Create the AddOns directory only if the client has not created it yet.

3. 3

   Copy the three ElvUI folders

   Keep ElvUI_Libraries and ElvUI_Options beside the main ElvUI folder.

MoP Classic compatibility

The relevant compatibility evidence is the Tukui API patch list, which includes 5.5.4 for the current release. Expansion names can remain in search results long after a patch changes, so this page displays the interface number and verification date instead of relying only on “MoP”.

After the first login

Follow the ElvUI setup wizard to choose scaling, layout and role defaults. Import a profile only after the base installation loads without errors, so profile-specific problems are easier to isolate.

Verify the ElvUI download for MoP Classic

The ElvUI download for MoP Classic should match Blizzard's current progression client rather than an original 5.4 private-server client. At the July 16, 2026 verification, Tukui reported ElvUI 15.18 with interface 5.5.4 in its supported patch list, and the public repository exposed the matching v15.18 tag. That interface evidence is the reason this page identifies the current archive as the starting point for Mists of Pandaria Classic.

Search results can combine old Mists of Pandaria addon packages, current Classic guides and private-server downloads. Expansion artwork and a familiar version name do not prove compatibility. Blizzard's progression client can include technical changes and backported systems that were not part of the original expansion. Check the interface value, release date and source repository before replacing a working installation. If Tukui publishes a version newer than 15.18, the newer supported release should replace the static archive linked by this July verification.

The same current ElvUI archive supports multiple branches through client-specific TOC metadata. MoP Classic reads the appropriate metadata when its own AddOns directory contains the three core folders. No separate executable or special installer is required.

Install the ElvUI download for MoP Classic correctly

Select Mists of Pandaria Classic in Battle.net and use Show in Explorer or Show in Finder to open that exact install location. Progression Classic commonly uses _classic_/Interface/AddOns, but the path should be confirmed from the launcher because custom installations and future branch changes can differ. Copying files into Classic Era or Retail will not update the MoP Classic client even when those directories are beside one another.

Open the archive wrapper and copy ElvUI, ElvUI_Libraries and ElvUI_Options directly into AddOns. WoW should see each TOC file one directory below AddOns. Remove an outer folder such as ElvUI-15.18 instead of placing that wrapper in the game directory. Keep all three core folders from the same ElvUI download for MoP Classic; mismatched libraries or options modules can cause dependency and configuration errors.

If an older installation exists, back up the branch's WTF folder, close WoW and delete only the three old ElvUI core directories. Copy the fresh directories rather than merging. Saved profiles remain under WTF, while stale addon code is removed by the clean replacement.

Configure ElvUI for MoP Classic roles and systems

Complete ElvUI's first-login setup before importing a profile. Choose the appropriate role layout, confirm UI scale and let the setup configure chat and baseline console variables. MoP Classic includes class resources, group content and encounter information that can make unit-frame and aura visibility especially important. A predictable base profile lets the player verify those systems before installing a complex community layout.

Open settings with /ec and test action bars, player and target frames, party or raid frames, bags, maps, nameplates and chat. A profile created for Retail can reference modules or frame behavior that differs in MoP Classic, while a profile created at another resolution can place elements outside the visible area. Import into a copied profile and review the creator's required fonts, media packs and plugins separately.

WeakAuras, SharedMedia, combat text and ElvUI extensions are not contained in a basic profile string. Install them one at a time after the base ElvUI download for MoP Classic loads without errors. This sequence gives every problem a clear change to trace instead of turning setup into several simultaneous unknowns.

Update and troubleshoot the ElvUI download for MoP Classic

Check for an updated ElvUI package after every MoP Classic client patch and before assuming an interface error is caused by a profile. Back up WTF, exit the game, replace the three core folders and verify the addon version at character selection. Do not delete saved variables during a normal update. Keep the previous archive until the new package has loaded and completed a full play session without repeated Lua errors.

If the addon is missing, confirm the selected client directory and remove an extra archive wrapper. If it is marked out of date, compare the client build with interface 5.5.4 and revisit Tukui for a newer release. If only the configuration window fails, inspect ElvUI_Options and ElvUI_Libraries. If gameplay errors remain, disable optional plugins and test a fresh profile with base ElvUI.

Do not replace the current ElvUI download for MoP Classic with an original 5.4 archive simply because both mention Mists of Pandaria. The interface families are not interchangeable. Use a legacy build only for a documented archived client, and obtain it from a verifiable public tag or a server-maintained compatibility source.

Progression characters often use different layouts for leveling, dungeons and raids. After updating, test vehicle bars, stance or form bars, party frames, raid frames and encounter auras before removing the previous backup. These systems can reveal a profile or plugin problem that is not visible while standing in a city. Record the working ElvUI version beside exported profiles so future MoP Classic changes can be compared against a known configuration. Keep that note with the archive and update it whenever a required plugin changes.

If Battle.net performs a scan or moves the game, reopen the MoP Classic location from the launcher before reinstalling. Compare the active executable path with the folder that contains ElvUI, ElvUI_Libraries and ElvUI_Options. A second, abandoned World of Warcraft directory can look complete while receiving no updates. Verifying the live path avoids repeating the download when only the destination was wrong.