Skip to content
Linux & Gaming Tested on Real Linux Rig

How to Install WoW Addons on Linux & Steam Deck (CurseForge & WowUp Fix)

Fix CurseForge and WowUp not detecting World of Warcraft on Linux or Steam Deck. Exact Steam Proton, Lutris, and Flatpak prefix path guide.

16-bit SNES pixel art Linux gaming monitor and handheld receiving glowing golden and teal addon rune icons from an arcane spellbook
On This Page (5 sections)

Getting World of Warcraft running on Linux or Steam Deck is the easy part — the real headache starts when you open CurseForge or WowUp and the app stares back with "No World of Warcraft installation found."

The reason is simple: on Linux, Battle.net installs WoW inside a hidden Wine or Steam Proton prefix (compatdata), and Flatpak/AppImage file pickers hide dotfiles (folders starting with .) by default. Here is how to locate your exact prefix path and connect your addon manager cleanly once and for all.

Why CurseForge & WowUp Cannot Auto-Detect WoW on Linux

On Windows, every addon manager checks C:\Program Files (x86)\World of Warcraft. On Linux, your Battle.net install lives inside whichever compatibility prefix you used to install it:

  • Steam (Non-Steam Game / Steam Deck): Hidden inside ~/.local/share/Steam/steamapps/compatdata/<APP_ID>/pfx/drive_c/Program Files (x86)/World of Warcraft/
  • Lutris: Usually inside ~/Games/battlenet/drive_c/Program Files (x86)/World of Warcraft/
  • Bottles / Flatpak Steam: Sandboxed inside ~/.var/app/... (which native apps or Flatpak addon managers may not have permission to browse until granted)

Step 1: Locate Your Real WoW Prefix Path

Choose the launcher you use to run Battle.net below:

Steam assigns a random numeric ID to every non-Steam shortcut (like Battle.net). Run this command in Konsole / Terminal to locate the exact compatdata folder automatically:

find "$HOME/.local/share/Steam/steamapps/compatdata" -maxdepth 6 -type d -name "World of Warcraft" 2>/dev/null

If you installed Steam as a Flatpak, check the Flatpak Steam path instead:

find "$HOME/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/compatdata" -maxdepth 6 -type d -name "World of Warcraft" 2>/dev/null

Lutris keeps prefixes clean and visible by default. Check your standard Games directory:

ls -d "$HOME/Games/"*"/drive_c/Program Files (x86)/World of Warcraft" 2>/dev/null

If your addon manager refuses to navigate deep .local or .var folders, create one clean symbolic link in your home folder. Replace /YOUR/EXACT/PATH/World of Warcraft with the path printed above:

mkdir -p "$HOME/Games"
ln -s "/YOUR/EXACT/PATH/World of Warcraft" "$HOME/Games/WoW-Link"

Now both CurseForge and WowUp only ever have to point to ~/Games/WoW-Link — zero hidden-folder hunting.

Step 2: Set Up CurseForge or WowUp on Linux

Both native Linux managers work great on Kubuntu KDE Wayland, SteamOS Desktop Mode, and other distros. Pick the one that fits how you manage addons:

Feature CurseForge (Linux AppImage) WowUp (CurseForge Build / AppImage)
Native Linux Support Official .AppImage (no Wine needed) Official .AppImage (no Wine needed)
Full CurseForge Catalog Yes (100% direct access) Yes (use the WowUp with CurseForge build)
Extra Sources (Wago / GitHub) CurseForge only CurseForge + Wago + GitHub + WoWInterface
Lightweight & Fast Medium Very lightweight

Connecting the Folder Inside CurseForge or WowUp

  1. Download the official Linux .AppImage (CurseForge or WowUp with CurseForge), right-click → Properties → Permissions → Allow executing file as program (or run chmod +x *.AppImage).
  2. Launch the manager, select World of Warcraft, and click Manually Locate Game (or Add Folder).
  3. Browse to your World of Warcraft folder (or ~/Games/WoW-Link) — select the root World of Warcraft directory, not the Interface/AddOns folder inside it, so the manager automatically detects _retail_, _classic_era_, and _classic_.

Step 3: Verify Addons Load In-Game

After installing your first addon (for example, a bag organizer to pair with our WoW Extra Backpack Slots & Cheapest Early Bags Guide):

  1. Confirm the addon folder landed inside <WoW Path>/_classic_era_/Interface/AddOns/ (or _retail_/Interface/AddOns/).
  2. Launch World of Warcraft through Battle.net and click the AddOns button at the bottom-left of the Character Select screen.
  3. If you added an addon while already logged into Azeroth, type /reload in chat (note: brand-new addon folders require a full game exit and relaunch before /reload will see them).

Frequently Asked Questions

Do I need to run CurseForge or WowUp through Wine or Proton on Linux?

No. Both CurseForge and WowUp ship official native Linux AppImages. Running the native Linux client is faster, avoids Wine glitches, and only needs the path to your Wine/Proton World of Warcraft folder.

Why does CurseForge say "No game found" when I select the AddOns folder?

Addon managers look for the parent World of Warcraft folder containing _retail_, _classic_era_, or _classic_ (and .flavor.info). Selecting Interface/AddOns directly is too deep — step back up two levels to the main World of Warcraft folder.

Can I manage Retail and Classic Era addons at the same time on Linux?

Yes. As long as both flavors are installed inside the same Battle.net prefix, pointing CurseForge or WowUp at the root World of Warcraft directory automatically detects every installed flavor in a dropdown menu.

Why didn't /reload load the new addon I just installed?

World of Warcraft only scans for newly created folders inside Interface/AddOns when the game client starts up. /reload refreshes changes to already-loaded addons, but a brand-new addon requires exiting WoW completely and launching it again.