Find X-Plane 12-compatible add-ons and learn how to verify versions, dependencies, operating-system support and installation folders before downloading.
You can find X-Plane 12-compatible add-ons in our main X-Plane aircraft, utility and add-on library and its focused aircraft and scenery categories. Before downloading, check that the listing explicitly names X-Plane 12, read every dependency and operating-system requirement, and never assume that an X-Plane 11 package will work unchanged.
Where can I download compatible X-Plane 12 add-ons?
Start with a library that identifies the intended simulator version on each file page. Our X-Plane collection covers aircraft, scenery, utilities, repaints and other freeware, but the individual description—not merely its category—determines whether a package supports X-Plane 12.
For airports, mesh and photoreal terrain, use the dedicated X-Plane scenery download collection. Aircraft require a little more care because a repaint, panel update or sound pack is not a flyable model; our guide to finding complete freeware aircraft packages explains how to distinguish them.
Do not treat a recent upload date as proof of compatibility. The description or included documentation should expressly say X-Plane 12, or state that the same package supports both X-Plane 11 and 12.
How do I check whether an add-on is really compatible?
- Confirm the simulator version. “For X-Plane” is too vague. Look for an explicit X-Plane 12 compatibility statement rather than relying on screenshots or the upload category.
- Read the dependency list. Scenery may require separate object libraries, while scripts can require a particular host plugin. Missing dependencies can produce blank scenery, error messages or features that do nothing.
- Check the operating system. Aircraft models and scenery are often platform-independent, but compiled plugins may provide binaries for only Windows, macOS or Linux. Mac processor support and Linux filename case sensitivity can also matter.
- Identify the exact parent product. Liveries, sound packs and cockpit modifications must match the named aircraft package and sometimes a particular revision of it. Matching the real aircraft type is not enough.
- Inspect the installation instructions. The package should identify its destination folder. Do not copy every file into the X-Plane root or overwrite simulator files merely because an archive contains several directories.
- Install one add-on at a time. Launch X-Plane after each installation so a conflict or missing dependency can be traced to the package that introduced it.
Can X-Plane 11 add-ons work in X-Plane 12?
Some X-Plane 11 add-ons work in X-Plane 12, but there is no blanket compatibility. Basic scenery and liveries are more likely to transfer than complex aircraft, graphics modifications or compiled plugins, all of which may depend on changed systems, rendering behaviour or plugin interfaces.
A package advertised only for X-Plane 11 should be treated as unsupported until its documentation says otherwise. We cover the differences and practical checks in our detailed X-Plane 11-to-12 add-on compatibility explanation.
Where do X-Plane 12 add-ons go?
The correct destination depends on the package type, and its included instructions take priority over a generic folder map.
| Add-on type | Usual destination | Key check |
|---|---|---|
| Aircraft | Aircraft | Keep the supplied aircraft folder intact, including its .acf file and companion resources. |
| Scenery | Custom Scenery | Place the actual scenery package here, not an unnecessary outer archive folder. |
| Global plugin | Resources/plugins | Confirm that its compiled binary supports your operating system and X-Plane 12. |
| Aircraft-specific plugin | Inside the aircraft package | Do not move it into the global plugin folder unless the instructions require that. |
| Livery | The matching aircraft’s liveries folder | Confirm that it was made for that exact aircraft package. |
Why is a compatible add-on not appearing?
The usual causes are an archive that was never extracted, a folder nested one level too deep, a missing library, incorrect scenery order or an incompatible plugin binary. For scenery, inspect scenery_packs.ini; airports and overlays normally need to sit above any mesh package they depend upon.
After reproducing the problem once, close X-Plane and inspect Log.txt in the simulator’s main folder. Search for the package or plugin name and messages containing “error”, “failed” or “not found”. Remove only the add-on being diagnosed, correct the reported dependency or folder problem, and then test again.