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

To install mods in X-Plane 11 or 12, extract the download, identify its type, and copy the complete add-on folder to Aircraft, Custom Scenery, Resources/plugins, or the aircraft’s liveries folder as appropriate. Install FlyWithLua scripts under FlyWithLua/Scripts. Restart X-Plane, then check Log.txt if nothing appears.

Use a package that explicitly supports your simulator version and operating system. An X-Plane 11 add-on is not automatically compatible with X-Plane 12, particularly when it contains an aircraft systems plugin, compiled code or flight-model changes. Our guide to checking X-Plane 11 add-on compatibility with X-Plane 12 explains what can usually be carried across and what needs an updated release.

How do I download mods or find extra aircraft?

Download X-Plane mods as archive files, save them to a temporary location such as your computer’s Downloads folder, and extract them before installation.

Our X-Plane freeware library organised by aircraft, scenery and add-on type includes extra aircraft and other downloadable mods. A browser download does not install anything into X-Plane automatically; the downloaded .zip, .rar or .7z file is only the package you must inspect and extract.

A screenshot or a short comment does not identify an installable package. Words such as “olha” (“look”), “dimmi” (“tell me”), “oui” (“yes”) or “我要這種” (“I want this kind”) still need the aircraft or scenery name, download filename and intended X-Plane version before the correct installation path can be established.

Before opening a package, check:

• Simulator version: look for explicit X-Plane 11 or X-Plane 12 support.
• Operating system: compiled plugins may support only certain systems or processor architectures.
• Required base product: a livery, sound pack or cockpit modification may require a separate aircraft.
• Dependencies: scenery can require object libraries, while scripts may require FlyWithLua or another plugin.
• Installation instructions: use the package author’s documented layout when it differs from the general paths below.

Plugins contain executable code, so use files from a source you trust. Do not follow instructions that require disabling operating-system security globally.

Where do X-Plane 11 and 12 mods go?

The correct destination depends on the add-on type, but every path starts inside the X-Plane installation you actually launch.

The X-Plane root is the folder containing the simulator application alongside directories such as Aircraft, Custom Scenery and Resources. X-Plane can be installed in a user-chosen location, and many simmers keep several copies for testing. Check the shortcut, launcher or application you use so you do not install the mod into an inactive copy.

Do not put third-party scenery in Global Scenery or overwrite files under X-Plane’s default scenery folders unless a package specifically documents that requirement. Ordinary downloaded scenery belongs in Custom Scenery.

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

The reliable method is to extract the package outside X-Plane, find the real add-on root, and copy that root without flattening its internal folders.

1. Close X-Plane. Plugins and scenery files can remain loaded while the simulator is running, so installation and removal are safest with it closed.
2. Read the included instructions. Confirm the supported X-Plane version, operating system, dependencies and any required base aircraft. If a trusted package uses an installer, verify that the installer is pointed at the correct X-Plane root.
3. Extract the archive completely. X-Plane cannot load a mod directly from a compressed archive. Extract it to a temporary folder where you can inspect everything inside.
4. Find the actual add-on folder. Downloads often have an outer wrapper containing screenshots, documentation and the folder that must be installed. For an aircraft, find the folder containing the .acf file. For scenery, locate each folder containing scenery data. Ignore documentation-only folders and system-generated folders such as __MACOSX.
5. Back up files that will be replaced. A standalone aircraft or scenery package is easy to remove. A cockpit, sound or systems modification may overwrite an existing aircraft, so duplicate that aircraft’s original folder first.
6. Copy the complete folder to its destination. Keep all internal files and subfolders together. Do not move an aircraft’s .acf file on its own or scatter loose plugin files directly into Resources.
7. Check for an extra folder level. A path such as Custom Scenery/Downloaded Package/Actual Airport/Earth nav data is usually one folder too deep. The actual airport should normally be a direct child of Custom Scenery. The same rule applies to global plugins under Resources/plugins.
8. Restart and test the relevant content. Select the aircraft, load the airport or activate the livery the mod was made for. A plugin may work in the background without adding a visible aircraft or menu.
9. Read Log.txt if it fails. This file is in the main X-Plane folder and records the latest session’s plugin, aircraft and scenery loading errors.

How do I install FlyWithLua in X-Plane 12?

Install a FlyWithLua build that explicitly supports X-Plane 12 as a global plugin, then place compatible Lua scripts in its Scripts folder.

1. Choose the correct FlyWithLua package. It must support X-Plane 12 and your operating system. For X-Plane 11, use a build intended for that simulator instead of assuming the same package will work.
2. Extract the download. Locate the real FlyWithLua folder inside the archive.
3. Install the framework. Copy that folder to X-Plane 12/Resources/plugins. The final path should be Resources/plugins/FlyWithLua, not Resources/plugins/FlyWithLua/FlyWithLua.
4. Start X-Plane once. Check Log.txt and X-Plane’s loaded-plugins information to confirm that FlyWithLua itself started successfully.
5. Install the script. Close X-Plane and copy the script’s .lua files to Resources/plugins/FlyWithLua/Scripts. If the script includes modules, configuration files or other folders, preserve the structure specified in its instructions.
6. Load a flight and verify the result. Many scripts do not take effect until an aircraft and flight have loaded. If the script is stopped, disabled or moved into a quarantine folder, inspect the FlyWithLua messages and Log.txt before trying another version.

FlyWithLua and a FlyWithLua script are separate parts: the framework is the plugin, while the .lua file supplies a particular feature. Installing only the script cannot work. A script written around old datarefs or commands may also fail in X-Plane 12 even when FlyWithLua itself loads correctly.

How do I install plugins in X-Plane 12?

A global X-Plane 12 plugin is installed by copying its complete plugin folder into Resources/plugins and restarting the simulator.

If the archive contains a path such as Resources/plugins/Plugin Name, copy Plugin Name into your existing Resources/plugins directory. Keep its platform subfolders, binary files and data together; copying only a loose plugin binary is a common reason it fails to load.

An aircraft-specific plugin is different. It must remain inside that aircraft’s own plugins folder and should not be moved into the global plugin directory. It loads only when that aircraft is selected.

If a plugin is absent after restarting X-Plane, check Log.txt for an unsupported operating system, processor architecture, missing runtime component or blocked binary. Some plugins work without adding a visible menu entry, so the log is a better test than the menu alone.

How do aircraft, scenery and liveries differ?

Aircraft, scenery and liveries use separate loading systems, so placing every download in one general “mods” folder will not work.

Extra aircraft

An extra aircraft should remain as one complete folder containing its .acf file and all supplied objects, sounds, liveries and aircraft-specific plugins.

Install that folder under Aircraft. You may organise aircraft into category subfolders, but do not separate the .acf file from its supporting content. If the aircraft is missing from the selector, remove filters, confirm the .acf file exists and check that you installed it in the X-Plane copy being launched.

Airports, overlays, libraries and meshes

Each actual scenery package normally belongs directly inside Custom Scenery, but one download can contain several installable folders with different priorities.

For airport package roots, mesh conflicts and scenery_packs.ini placement, follow our detailed X-Plane 12 scenery installation and load-order instructions. If the log reports missing objects or library paths, use our explanation of installing required scenery libraries in X-Plane rather than repeatedly reinstalling the airport.

Scenery that uses an installer, creates file links or streams imagery can be an exception to the normal copy-and-paste method. Follow that package’s own instructions and do not rearrange generated folders afterwards.

Liveries and aircraft modifications

A livery belongs inside the exact base aircraft for which it was painted and will not work as a standalone aircraft.

The usual path is Aircraft/Aircraft Name/liveries/Livery Name. Similar variants of the same aircraft can use different texture layouts, so matching the manufacturer and model name is not enough; confirm the specific add-on and variant.

Sound packs, cockpit replacements and systems patches often merge into an existing aircraft instead. If they are installed as a neighbouring folder, nothing will change. Back up the aircraft before allowing files to be replaced.

Do I need to edit scenery_packs.ini?

Edit Custom Scenery/scenery_packs.ini only when scenery is disabled, covered by another package or loading in the wrong priority.

X-Plane creates or updates entries after recognising scenery. Close the simulator before editing the file in a plain-text editor, and remember that entries higher in the file take priority over entries below them.

• Custom airports: keep them above the simulator’s global airports.
• Global airports: keep them below custom replacement airports.
• Landmarks and overlays: place them above orthophoto and base-mesh packages.
• Orthophoto scenery: keep it below airports and overlays.
• Base meshes: place them near the bottom because a mesh can suppress scenery beneath it.
• Disabled entries: any line beginning with SCENERY_PACK_DISABLED will not load.

Library position is usually less significant than airport and mesh priority, but the library must be installed, enabled and readable. Always use a scenery author’s documented sequence when it differs from this general order.

Why is my mod not showing up or “it’s not there”?

A missing mod is usually installed in the wrong X-Plane copy, nested one folder too deeply, incompatible with the simulator or unable to find a required dependency.

Reproduce the problem, quit X-Plane and open Log.txt before starting another session. Search for the add-on name and terms such as Error, Failed and not found. The log is rewritten on later launches, so inspect it while it still represents the failed test.

• Aircraft is absent: find its .acf file, check aircraft-selector filters and confirm the installation path. An outer wrapper folder is acceptable only if X-Plane can still reach the aircraft folder beneath it.
• Aircraft loads but displays or systems are dead: its aircraft-specific plugin probably failed, was blocked or requires a missing component.
• Airport has runways but no buildings: missing scenery libraries are the most likely cause. The log normally identifies the unresolved asset paths.
• Scenery is covered by default terrain: inspect scenery_packs.ini for the wrong priority, a disabled entry or a competing mesh.
• Plugin has no visible effect: confirm that it supports your X-Plane version, operating system and processor. Then check whether it is designed to run without a menu.
• FlyWithLua script does nothing: verify that FlyWithLua loads first, then test the script by itself. Remove other scripts temporarily if several are changing the same datarefs.
• Livery is missing: select the correct base aircraft and variant, then remove any duplicated folder level under liveries.

Why did nothing change after installation?

If your result is “nothing changed” or “ничего не изменилось.”, first test the mod in the exact aircraft, livery, location or flight condition it affects.

A scenery package changes only its covered area, a livery appears only under its intended aircraft, and some plugins activate only after a flight has loaded. For a patch, confirm that its files were merged into the existing aircraft rather than installed beside it. Change one thing at a time; temporarily moving the suspect package out is a faster isolation test than reinstalling X-Plane.

Does Windows, macOS or Linux change the installation?

The core X-Plane folder layout is the same on Windows, macOS and Linux, but compiled plugins must match the operating system and processor architecture.

• Windows: security controls or protected folders can block downloaded binaries or prevent files from being written. Confirm that extraction completed and that your account can write to the X-Plane folder.
• macOS: system security may block an untrusted plugin binary. Verify the package first and use the operating system’s normal approval process rather than disabling protection globally.
• Linux: filename capitalisation, execute permissions and required system components can affect plugin loading. Paths that differ only by upper- and lower-case letters are not interchangeable.

A mistake we see constantly is reinstalling the entire simulator before checking the active X-Plane path and Log.txt. A failed third-party add-on rarely requires a complete X-Plane reinstall.

How do I uninstall an X-Plane mod cleanly?

Uninstall a standalone X-Plane mod by closing the simulator and removing the complete folder or script that was added.

• Aircraft: remove its folder from Aircraft.
• Scenery: remove every associated package from Custom Scenery; with X-Plane closed, delete its stale scenery_packs.ini line if one remains.
• Global plugin: remove its complete folder from Resources/plugins.
• FlyWithLua script: remove the relevant script and any script-specific support files from the FlyWithLua folders.
• Livery: remove that paint scheme’s folder from the base aircraft’s liveries directory.

If a patch overwrote or merged with existing aircraft files, restore your backup or reinstall the unmodified aircraft. Do not delete all X-Plane preferences to remove one mod unless its documentation identifies a specific preference or configuration file that it created.