ElvUI's Forever compatibility is not confirmed here. Tukui lists ElvUI 16.01, updated November 3, 2026, but a current general version number does not establish that its release supports Forever. Before replacing your interface or importing a profile, look for an explicit Forever statement on the exact package you intend to use.
ElvUI is a full interface replacement with configurable modules, rather than a preset for Blizzard's default UI. Its core, optional plugins and shared profiles need separate compatibility checks. Installing a profile cannot add game-version support to an unsupported core.
Decide whether you need ElvUI itself
ElvUI is built around changing several interface systems in a coordinated way. Its general module structure includes action bars, unit frames, nameplates, bags, chat, tooltips, maps and information panels. That explains its appeal when you want a consistent layout across the screen.
It also makes it a larger commitment than moving a single frame. If your goal is only to reposition one element, write down that requirement first. You can assess whether a full replacement is worth configuring without assuming you need every module.
The descriptions of modules below explain ElvUI's design. They are not a promise that those modules, their old menu labels or their former combat features work in Forever.
Verify the core before choosing a profile
The author version page is a release reference, not confirmation of Forever compatibility.
Use three separate checks, in this order:
- Core package: confirm that the release names Forever as a supported game branch. A WoW-wide description, recent update date or Retail patch number does not answer this.
- Optional plugins: identify every additional plugin a layout needs. A plugin listed in Tukui's community directory is an extension of ElvUI, with its own features and requirements.
- Profile: check the intended game branch and the required core and plugin versions. A screenshot shows an appearance, not whether that profile can reproduce it on your client.
Tukui's own ElvUI page and the project's release information are the places to check the package identity. Do not use an old developmental download simply because a forum reply calls it the newest build. In particular, a January discussion about 12.0 and Midnight does not confirm a November Forever release.
Until the core check is satisfied, keep your working layout. There is little value in spending time tuning an import whose required foundation has not been established.
Give each interface feature one owner
ElvUI's modular approach matters if you also use separate interface addons. In the general ElvUI setup model, you disable the corresponding ElvUI module when another addon handles that feature. For example, the documented pairing for Plater is to disable ElvUI's NamePlates module.
| Feature you want to replace | ElvUI module involved | Decision to make |
|---|---|---|
| Enemy nameplates | NamePlates | ElvUI or a separate nameplate addon |
| Action bars | ActionBars | ElvUI or your bar replacement |
| Chat presentation | Chat | ElvUI or your chat addon |
| Player and group frames | UnitFrames | Which addon owns those frames |
Make that decision only after checking the chosen addons for Forever. Disabling overlapping modules can address competing layouts; it cannot make an unsupported addon compatible.
Treat imports as configuration changes
Once you have an explicitly supported build, preserve your existing settings before testing someone else's layout. ElvUI's general profile system distinguishes ordinary profiles from private settings, such as character-specific choices. A profile import should not be assumed to carry every setting shown in an author's screenshot.
The documented profile tools include creating profiles, copying settings, importing, exporting and resetting individual modules. Pay attention to the destination of a copy: replacing the current profile is different from switching to a saved one.
Start with a small change that you can recognize, such as the placement of one frame. Confirm that it survives your next session before building a more elaborate layout around it. Then add optional plugins individually, keeping enough information to return to the previous arrangement.
Plan a layout before changing settings
A useful ElvUI plan begins with the information you actually need to see. Write down the few elements you struggle to read in your current layout: perhaps your own health, the selected target or the action buttons you use most. This gives you a reason to change a module instead of copying every choice in someone else's setup.
Separate presentation from behavior. Font size and frame position describe how information is displayed. Aura filtering, advanced nameplate rules and combat-related automation can depend on information the client makes available. A visual match to a screenshot does not settle the second group.
For a supported build, make a small layout plan before testing an imported profile:
- Identify the frames that must remain readable while you move or fight.
- Decide where the central gameplay area needs to stay clear.
- Identify which existing addons already own the features you want to keep.
- List the optional plugins a proposed layout needs.
- Choose one visible change to assess first, with a way to restore the previous arrangement.
Do not use a layout's density as a measure of its quality. An arrangement that hides a control you need or makes important text harder to read has failed your purpose, even if it resembles the author's image.
Evaluate a supported import in small stages
If you later obtain a release explicitly supporting Forever, begin with the core package before adding extensions. Establish that you can open its options and identify the enabled modules. The general ElvUI commands are /ec or /elvui for options, but the supported package's own instructions should determine the workflow you follow.
Next, test the profile without optional additions that are not required for the comparison. Check the positions and sizes you intended to change. If a frame does not match the example, identify whether the example depends on a plugin, a private setting or another game branch before trying unrelated fixes.
Keep imports and copies distinct. Copying another profile into the current one is a change to the destination; switching between existing profiles is a different action. Name a working configuration clearly and retain its export before experimenting with a replacement.
When a problem is limited to one module, record that scope. A misplaced chat panel, an unreadable unit-frame label and a combat display that cannot obtain the information it expects need different decisions. Resetting or replacing the entire layout can erase the comparison you need to understand the change.
For a support request, retain the exact core version, enabled plugin names, affected module and action that produced the problem. Include whether it happens with the core alone or only with the proposed profile. That description is more actionable than a screenshot of the finished screen without the versions behind it.
Recognize instructions for another WoW branch
Older ElvUI guides include systems, screenshots and setup paths from other WoW releases. They remain useful for understanding terms such as modules, tags and profiles, but their exact feature lists should not be carried into Forever.
Be especially careful with advanced aura filtering, nameplate rules and automated combat displays. Forever has restrictions on computational combat addons, and a historical ElvUI feature description does not establish what is currently available.
Your decision can stay simple: use ElvUI when the exact release and the features you need are explicitly supported. If that evidence is absent, keep the interface you can already use and revisit the package before investing in a profile migration.