How do I install mods in DCS World?

To install most mods in DCS World, extract the archive and copy the mod’s actual folder to the correct location under Saved Games\DCS (or the active legacy DCS.openbeta profile). Aircraft, asset packs, liveries and missions use different subfolders. Change DCS’s main installation only when the mod author explicitly requires it.

Where do DCS World files and mods go?

DCS World separates its official installation files from user content stored in Windows Saved Games. Most community mods belong in the latter because updates are less likely to overwrite them and removal is simpler.

The usual profile is %USERPROFILE%\Saved Games\DCS. Long-running installations may instead retain %USERPROFILE%\Saved Games\DCS.openbeta. Because Windows can relocate Saved Games, pressing Win+R and entering shell:SavedGames is more reliable than assuming it is on the C drive.

If both DCS folders exist, launch the simulator and then check which folder has freshly modified files under Logs or Config. That is the active profile; the folder name alone is not conclusive.

Package structures vary, so the readme takes priority over this table. Our DCS World freeware library organised by add-on type can help distinguish missions, liveries, aircraft and utilities before installation.

How to install mods in DCS World step by step

A reliable installation depends on identifying the package’s real root folder rather than copying the downloaded archive blindly.

1. Launch DCS World once. This creates the user profile and its standard folders. Close DCS before copying or replacing files.

2. Read the package instructions. Check its required DCS modules, dependency packs, supported versions and uninstall notes. Most ordinary mods need only file extraction; treat an unexpected executable installer cautiously.

3. Find the active Saved Games profile. Use Saved Games\DCS or the legacy Saved Games\DCS.openbeta folder that received updated logs when DCS last ran.

4. Extract the archive fully. Do not put a ZIP, RAR or 7Z archive directly in a DCS folder. Open the extracted package and locate its readme and actual content.

5. Interpret the archive structure. If its top level contains folders such as Mods, Liveries or Missions, the package is usually arranged to merge with the active DCS profile. If the top level is a named aircraft folder containing entry.lua, that named folder normally goes under Mods\aircraft.

6. Copy the content to the specified destination. Create missing subfolders when necessary, but preserve the structure inside the mod. For a typical aircraft, the resulting path resembles Saved Games\DCS\Mods\aircraft\ModName\entry.lua.

7. Back up official files before any core change. If the instructions require the main DCS World install, record every added or replaced file. Core modifications are harder to reverse and can be overwritten by an update.

8. Restart and test the correct content type. Open missions through the Missions screen, select liveries on the aircraft for which they were made, and check aircraft or assets in the Mission Editor. Ordinary community ZIP mods are not installed through DCS’s official module-management system.

How can I spot an incorrectly nested mod folder?

The folder containing the mod’s working files must sit at the level expected by DCS. For many aircraft mods, Mods\aircraft\ModName\entry.lua is plausible, while Mods\aircraft\DownloadedArchive\ModName\entry.lua has an unnecessary wrapper folder.

A mistake we see constantly is copying the first folder produced by extraction even though it contains only another folder and a readme. Open each level and find the directory that actually contains files such as entry.lua, description.lua, Shapes or the supplied content folders.

Saved Games or the main DCS install

Saved Games is the correct default whenever the mod supports it.

• Choose Saved Games for most community aircraft, asset packs, liveries, missions, kneeboards and user scripts. These files are isolated from the official installation and are easier to remove.
• Use the main install only when required for older cockpit, sound, effect, shader or interface replacements that alter official files.
• Use a mod manager for numerous core changes if it can stage and reverse the exact files involved. It does not make an incompatible mod compatible, but it can make rollback less error-prone.

A Saved Games installation is safer, but it does not guarantee that a mod will survive every DCS update. Changes to DCS APIs, models or scripting behaviour can still break community content.

Why is my DCS World mod not showing up?

Wrong profile selection, double nesting and incorrect destinations account for most missing DCS World mods.

1. Confirm the active profile. Check the timestamp on Logs\dcs.log. Files copied to an unused DCS or DCS.openbeta folder will not load.

2. Inspect the folder depth. Remove an unnecessary outer wrapper so the actual mod folder sits directly under Mods\aircraft or Mods\tech.

3. Check the content type. A livery does not belong in Mods\aircraft, and a mission will not appear as a flyable module. A controller or head-tracking profile may need importing through another menu or application.

4. Verify dependencies and compatibility. Some community aircraft require a particular official module or another asset pack. Older mods may stop loading after DCS changes.

5. Test it without editor filters. Aircraft and assets may be limited by country, coalition or declared service dates. The Mission Editor’s historical unit filter can therefore hide an installed unit. An aircraft that cannot be assigned as Player or Client may be AI-only rather than broken.

6. Read the DCS log. Open Saved Games\DCS\Logs\dcs.log, or the equivalent path in the active profile, and look for the mod name, Lua errors or missing files. Remove the last installed add-on if DCS began failing immediately after it was added.

For a missing livery, also confirm that its parent folder uses the unit identifier expected by the package and that description.lua is inside the individual livery folder rather than one level too deep.

Multiplayer, Steam and standalone differences

Steam and standalone DCS World use the same general Saved Games mod structure, while multiplayer compatibility depends on the mod and server.

Do DCS World mods work in multiplayer?

Some DCS World mods work online, but the server mission and its integrity-check rules determine whether they can be used.

• Core-file replacements are the most likely to fail a multiplayer integrity check.
• Saved Games content is less intrusive, but its location alone does not guarantee server acceptance.
• Custom aircraft and assets must be supported by the server mission, and required packages generally need to be present wherever the mission expects them.
• Local liveries may work without changing the simulation, but other players may not see them unless they also have the same files.

Steam and standalone use the same mod folders

Most community mods install under the Windows Saved Games profile regardless of which DCS edition launches the simulator. The difference matters only when instructions require changes to the main installation, whose location and repair method vary between editions.

If you are deciding which edition to maintain, our practical comparison of Steam and standalone DCS World covers the differences beyond mod placement.

Not every DCS World file belongs in the Mods folder

Controller mappings, head-tracking profiles and helper utilities may be imported through DCS or their associated software rather than copied under Mods.

For example, our downloadable TrackIR 5 profile for DCS World is a profile for the head-tracking software, not an aircraft mod. Follow the package’s extraction and loading instructions instead of placing it in Mods\aircraft.

DCS controller profiles also deserve care. A supplied profile may be loaded from the Controls screen, while utilities that modify Scripts\Export.lua can share that file with other tools. Do not overwrite or delete it without checking what is already there.

How do I remove a DCS World mod?

Remove the exact folders and file changes added by the mod, then repair official files if it altered the main installation.

1. Close DCS World. Keep the original archive and readme available so you can identify every installed file.

2. Delete isolated Saved Games content. Remove the mod’s folder from Mods\aircraft, Mods\tech, Liveries, Missions or its documented destination. Do not delete shared parent folders containing other add-ons.

3. Undo script edits carefully. If a utility added a line to Scripts\Export.lua, remove only that utility’s line. Other applications may depend on the same file.

4. Restore the official installation. Remove extra files identified by the mod’s instructions, then use DCS’s repair facility or Steam’s installed-file verification to restore replaced official files. A repair may not identify every unsupported extra file.

5. Restart and test. Confirm that DCS loads and the removed content is gone. If a removed shader or graphics mod leaves visual corruption, deleting the fxo and metashaders2 folders from the active Saved Games profile can help; DCS rebuilds them on the next launch.

Keeping a modded DCS install recoverable

Installing one add-on at a time makes faults and conflicts much easier to isolate.

• Keep the original archive and readme so dependencies, file locations and removal steps remain available.
• Record core-file changes rather than relying on memory after an update.
• Test after every installation before adding the next package.
• Remove or disable core mods before updating, then reinstall them only after confirming compatibility.
• Protect personal data such as Config\Input, missions and logbook files before renaming or resetting an entire DCS Saved Games profile during troubleshooting.