How do I install mods in X-Plane 11 and 12?

To install mods in X-Plane 11 or 12, extract the download, identify whether it is an aircraft, scenery pack, plugin, script or livery, then copy the actual add-on folder to its matching X-Plane directory. Restart the simulator and check Log.txt if the mod does not appear or load.

Use packages that explicitly state support for your X-Plane version; an X-Plane 11 add-on is not automatically compatible with X-Plane 12. Our X-Plane freeware collection organised by add-on type is a useful starting point when choosing aircraft, scenery and utilities.

Where do X-Plane 11 and 12 mods go?

X-Plane 11 and 12 use the same core add-on folders, all found inside the main X-Plane installation directory.

The X-Plane root is the folder containing Aircraft, Custom Scenery, Resources and the simulator application. Multiple X-Plane copies are common, so confirm that this is the installation you actually launch. PC users who cannot find it can follow our guide to locating and choosing the X-Plane 12 installation folder.

How do I install an X-Plane mod step by step?

The safest procedure is to extract the package away from X-Plane, inspect its structure, then copy only the real add-on folders to their proper destinations.

1. Read the supplied instructions. Check the required X-Plane version, operating system, scenery libraries, base aircraft and companion plugins. If the package has its own installer, follow its instructions and point it to the correct X-Plane root.
2. Extract the archive completely. Do not place a .zip, .rar or .7z archive directly in X-Plane. The simulator reads the extracted files and folders, not the compressed download.
3. Identify the actual add-on root. Downloads often contain a wrapper folder holding screenshots, documentation and one or more installable folders. For aircraft, locate the folder containing the .acf file. For scenery, find each folder containing scenery data rather than copying an outer download wrapper.
4. Back up anything that will be overwritten. Standalone packages are easy to remove, but a sound pack, cockpit modification or systems patch may replace files inside an existing aircraft. Copy that aircraft's original folder before merging the update.
5. Copy the mod to its matching directory. Keep the package's internal structure intact. Do not move an aircraft's .acf file by itself or scatter individual plugin files directly into Resources.
6. Check for accidental extra nesting. Scenery packs and global plugins normally need to be direct children of their destination folders. A path such as Custom Scenery/Download Name/Actual Scenery/Earth nav data is usually one level too deep. Aircraft can be organised into category subfolders, but patches and bundled resources must retain the structure expected by the aircraft.
7. Restart X-Plane. A full restart is particularly important for plugins. Load the relevant aircraft or location and note any warnings shown during start-up.
8. Inspect the result and the log. Aircraft should appear in the aircraft selector, liveries under their base aircraft, and scenery only at its intended location. Plugins may add a menu entry or work in the background. If something fails, inspect Log.txt before changing more files.

How do aircraft, scenery, plugins and liveries differ?

Each add-on type uses a different loading system, so a correct folder destination is only part of the installation.

Aircraft and aircraft patches

A standalone aircraft should remain as one complete folder containing its .acf file and supporting content. If several .acf variants are supplied, keep them together unless the instructions say otherwise.

Updates, sound packs and cockpit or systems modifications often belong inside an aircraft you already have. Installing such a patch as a neighbouring folder will not modify the aircraft. Our aircraft-specific installation walkthrough covers aircraft folder structure and common selection-menu problems in more detail.

Scenery packs and libraries

Every actual scenery pack normally sits directly inside Custom Scenery. A large airport download may contain separate airport, overlay and mesh folders; each may need to be copied separately and then ordered correctly.

If the airport pavement appears but buildings or other objects are missing, check its readme for required libraries. Install only the dependencies named by the package. OpenSceneryX is a common example, and our OpenSceneryX installation guide explains its placement and verification.

Imagery tools, installers and scenery that create links or stream data are exceptions to the ordinary drag-and-drop method. Follow their supplied instructions rather than treating them as a single airport folder.

Plugins and FlyWithLua scripts

A global plugin belongs in Resources/plugins as a complete folder. It may contain separate binaries for different operating systems or processor architectures, along with data files that are required for it to load.

Aircraft-specific plugins remain inside that aircraft's folder and load only with the aircraft. FlyWithLua scripts go in Resources/plugins/FlyWithLua/Scripts, but a script cannot work unless a compatible FlyWithLua installation is already present.

Liveries

A livery belongs to the exact aircraft for which it was painted. Put its folder under Aircraft Name/liveries; do not install it as a separate aircraft.

Similar aircraft variants do not necessarily share texture layouts. If a paint scheme does not appear, check that it matches the correct model and that its folder is not nested twice. Capitalisation also matters on case-sensitive file systems.

Do I need to edit scenery_packs.ini?

You only need to edit Custom Scenery/scenery_packs.ini when scenery loads in the wrong order, is disabled or conflicts with another package.

X-Plane adds newly recognised scenery after a launch, but complex installations may still need manual ordering. Quit the simulator before opening the file in a plain text editor. As a general priority:

• Custom airports: place them near the top and above the simulator's global airports.
• Global airports: keep them below custom airports so a default airport does not take priority over its replacement.
• Landmarks and overlays: place them above orthophoto and base-mesh packages.
• Orthophoto scenery: place it below airports and overlays.
• Base meshes: keep them near the bottom because they can suppress scenery below them.

Library order is normally less important than airport and mesh order, but the library must be installed, enabled and readable. Any entry beginning with SCENERY_PACK_DISABLED will not load. If the scenery author specifies a different sequence, use that sequence instead of the generic order above.

Why is my mod not showing up in X-Plane?

Start with Log.txt in the main X-Plane folder, because it records missing scenery assets, rejected plugins, unsupported files and load failures from the latest session.

Reproduce the problem, quit X-Plane and then read the log before launching again; the file is recreated on subsequent starts. Search for the add-on name and terms such as Error, Failed or not found.

• No aircraft in the selector: confirm that an .acf file exists, clear any selector filters and check that you installed it in the X-Plane copy being launched. The aircraft may also use an unsupported or incompatible file format.
• Aircraft appears but displays or systems are dead: an aircraft-specific plugin probably failed to load, or the package requires an uninstalled dependency.
• Airport has runways but no buildings: one or more object libraries are usually missing. The log normally names the missing library paths.
• Scenery is absent or covered by other terrain: check that its folder is a direct child of Custom Scenery, then inspect scenery_packs.ini for a disabled entry or incorrect priority.
• Plugin does not provide its expected menu or function: check for an operating-system, processor-architecture or X-Plane-version mismatch. Copying only a loose plugin binary instead of its whole folder can produce the same result.
• FlyWithLua script does nothing: verify that FlyWithLua itself loads, then check its messages and Log.txt for a stopped or incompatible script.
• Livery is missing: confirm the base aircraft and variant, then check the path under its liveries folder and remove any accidental duplicate folder level.

A mistake we see often is reinstalling the whole simulator before checking the path and log. A bad add-on installation rarely damages X-Plane itself; temporarily moving the suspect package out of its destination folder is a faster isolation test.

Does Windows, macOS or Linux change the process?

The main folder layout is the same on Windows, macOS and Linux, but plugin loading is platform-dependent.

A plugin must include a binary compatible with the operating system and processor architecture in use. Windows may block downloaded files, macOS security controls may prevent an untrusted binary from loading, and Linux may require correct execute permissions and exact filename capitalisation. Do not disable operating-system security globally; verify that the package is trusted and follow its platform-specific instructions.

X-Plane version matters as well. Scenery and simple liveries are often easier to carry between X-Plane 11 and 12 than aircraft systems, flight-model modifications or compiled plugins, but compatibility should never be assumed. If a download provides separate builds, install the one labelled for your simulator.

How do I uninstall an X-Plane mod cleanly?

A standalone X-Plane mod normally uninstalls by deleting or moving out the folder that was added.

• Aircraft: remove its folder from Aircraft.
• Scenery: remove each associated folder from Custom Scenery; delete any stale entry from scenery_packs.ini with X-Plane closed.
• Global plugin: remove its complete folder from Resources/plugins.
• FlyWithLua script: remove the relevant script from the Scripts folder.
• Livery: remove that paint scheme's folder from the aircraft's liveries directory.

If the mod merged with or replaced files in another package, restore your backup or reinstall the original package. Do not delete general X-Plane preference files in an attempt to remove a mod unless its documentation identifies a specific file that it created.