Skip to content
X-Plane 12 min read 1.5k views

What are the best free add-ons for X-Plane 12?

Adam McEnroe
In short

Best free X-Plane 12 add-ons for aircraft, XP12 plugins, weather and scenery, with installation help and clear 757-300 advice.

The best free add-ons for X-Plane 12 are the Zibo 737-800X, AviTab, BetterPushback, XChecklist, FlyWithLua NG, SimHeaven X-World, AutoOrtho and OpenSceneryX. Choose XP12-native releases, install one package at a time, and check Log.txt; compatibility and correct scenery order matter more than building the longest add-on list.

Best X-Plane 12 add-ons by category

These are the strongest starting points for free X-Plane 12 mods, covering aircraft, XP12 plugins, visual tools and scenery without loading the simulator with unnecessary dependencies.

CategoryBest free choicesWhat they improve
Free aircraftZibo 737-800X, Sparky 747-400, Aerobask Robin DR401, Rotorsim EC135Airliner systems, long-haul operations, light-aircraft flying and helicopters
XP12 plugins and utilitiesAviTab, BetterPushback, XChecklist, FlyWithLua NGDocuments and maps, pushback planning, interactive checklists and script support
Weather and visual toolsX-Plane 12 real weather, HeadShake, X-Camera's free modeLive conditions, restrained cockpit movement and improved camera control
ScenerySimHeaven X-World, AutoOrtho, Ortho4XP, OpenSceneryXBuildings and roads, photographic ground imagery, terrain tiles and airport dependencies

Best aircraft add-ons for X-Plane 12

The Zibo 737-800X is the best all-round freeware airliner for XP12, but a different aircraft makes more sense for long-haul, general aviation or helicopter flying.

Flying typeRecommended freewareChoose it whenCompatibility check
Boeing short and medium haulZibo 737-800XYou want detailed 737 procedures, a functioning flight-management system and regular airline operationsUse the dedicated XP12 package and follow its full-install and update instructions. Install it outside the default Laminar Research folder.
Long-haul wide-bodySparky 747-400You prefer four-engine long-haul flying and accept that freeware systems may remain under developmentDownload the XP12 branch or package rather than assuming an older aircraft build is interchangeable.
Light general aviationAerobask Robin DR401You want straightforward VFR touring and training rather than airliner-level cockpit managementSelect the release explicitly offered for X-Plane 12; older editions can have different avionics and flight-model behaviour.
Helicopter flyingRotorsim EC135You want a freeware twin-engine helicopter and are prepared to configure collective, pedals and control sensitivity properlyUse the XP12-labelled edition and read its plugin requirements before loading it.

Free aircraft quality varies sharply. A model can appear in the aircraft menu yet still have broken displays, sounds or flight dynamics, so an explicit XP12 release matters more than the age or visual quality of its screenshots. Our X-Plane freeware aircraft and add-on library provides more aircraft, scenery and utility options beyond this shortlist.

Best 757-300 payware or freeware mod for X-Plane 12 in 2025/2026

Compatibility-checked answer: there is no credible, complete native XP12 freeware Boeing 757-300 that we would recommend for serious flying in 2025/2026. Downloads based on old X-Plane versions may load, but that does not establish correct 757-300 systems, flight dynamics, displays or plugin compatibility.

The established payware route is the FlightFactor 757 Professional Extended product line, provided the exact package being sold explicitly includes the 757-300 and lists X-Plane 12 support. Do not assume that a base 757-200 package automatically supplies the stretched variant.

Before purchasing, verify the exact included variants, native XP12 support, operating-system and processor compatibility, update method, activation limits and support status. Read the seller's refund policy as well: downloadable aircraft are often non-refundable once delivered or activated.

Best XP12 plugins and utilities

AviTab, BetterPushback and XChecklist provide the most useful everyday functions without trying to alter X-Plane 12's core rendering or flight model.

  • AviTab: Adds an in-cockpit tablet for maps, documents and supported aircraft integrations. It does not automatically include every chart or briefing source.
  • BetterPushback: Lets airliner pilots plan and control a pushback path. Avoid running another pushback or ground-service controller at the same time.
  • XChecklist: Displays interactive checklists, but it needs a suitable checklist file written for the aircraft being flown.
  • FlyWithLua NG: Runs compatible Lua utilities. It is a framework, not a performance upgrade, and an old script that changes private datarefs can fail after an XP12 update.

Install only plugins that solve a problem you actually have. Our focused guide to useful XP12 plugins for charts, cameras, checklists and scripting explains the main choices without treating every optional utility as essential.

Best free weather and visual tools for X-Plane 12

X-Plane 12's built-in real-weather system is the safest free weather choice; use plugins for camera and presentation improvements rather than replacing the simulator with old XP11 weather scripts.

  • Built-in real weather: Start here before adding anything. It avoids conflicts between competing cloud, visibility and atmosphere controls.
  • HeadShake: Adds restrained movement during taxi, turbulence and touchdown. Disable other camera-motion effects first, and consider leaving it off in VR if the movement is uncomfortable.
  • X-Camera free mode: Provides more deliberate cockpit and exterior camera control. Some advanced functions require registration, so check which features are included before planning a setup around it.
  • FlyWithLua visual scripts: Use only scripts explicitly maintained for XP12. Scripts that overwrite private lighting, cloud or atmosphere datarefs are particularly likely to become ineffective or unstable.

Do not stack multiple cloud controllers, visibility scripts and colour presets. Establish a stock-weather baseline, add one tool and compare it under the same airport, time and weather conditions. We cover the trade-offs in our comparison of X-Plane 12 weather add-ons.

Best X-Plane 12 scenery and airport add-ons

Use a custom airport for local detail, X-World for buildings and roads, orthophoto for photographic ground imagery, and mesh for terrain shape; these packages improve different layers and cannot be substituted for one another.

Scenery typeFree recommendationWhat it changesMain caveat
AirportsXP12 Global Airports; MisterX6 KPDX and KBOS as custom freeware examplesRunways, taxiways, terminals, lighting and airport objectsGlobal Airports is included with XP12. KPDX and KBOS have older-X-Plane lineage, so check for an XP12 update or test them as legacy scenery before relying on them.
Object librariesOpenSceneryX and MisterX LibrarySupply objects referenced by freeware airportsLibraries do not improve every airport by themselves. Install them only when required, and keep them updated.
Buildings and roadsSimHeaven X-WorldAdds regional overlays with more representative buildings, roads, vegetation and infrastructureInstall the correct regional package and preserve the component order specified with it. X-World does not provide photographic ground textures.
Streamed imageryAutoOrthoStreams and caches orthophoto tiles instead of storing complete regions in advanceIt needs platform-specific setup, cache space and a dependable connection. Uncached areas can initially appear soft or cause loading pauses.
Locally stored imageryOrtho4XPBuilds orthophoto tiles and associated terrain locallyIt needs substantial storage and more preparation, but it is not dependent on streaming during a flight.
Terrain meshOrtho4XP-generated mesh; HD Mesh Scenery v4 as a legacy alternativeChanges terrain elevation, coastlines and land-class placementOnly one base mesh normally displays for a given tile. HD Mesh Scenery v4 is not a native XP12 product, so compare it carefully with XP12's default terrain before keeping it.

KPDX and KBOS remain useful examples of detailed freeware airport design, but airport scenery is not automatically native to XP12 simply because it loads. Check runway alignment, terrain flattening, jetways, exclusion zones and night lighting. If the custom airport performs worse than the maintained Gateway version included with XP12, remove it and use the default.

For imagery, choose AutoOrtho when storage is limited and reliable streaming is available. Choose Ortho4XP when you want predictable offline tiles and can spare the disk space. Our X-Plane 12 scenery layering guide explains how X-World, orthophoto and mesh fit together.

What order should scenery use in scenery_packs.ini?

Entries near the top of Custom Scenery/scenery_packs.ini have higher priority, so airports and overlays must sit above the imagery or mesh they are intended to cover.

  1. Custom airports and local landmarks: Put detailed airport packages near the top.
  2. Airport overlays: Place any separately supplied airport overlay beneath its associated airport unless its instructions specify otherwise.
  3. Regional overlays: Place X-World components and Ortho4XP overlays below airports, retaining the package's internal order.
  4. Orthophoto imagery: Put AutoOrtho or Ortho4XP photo tiles below airports and overlays.
  5. Base mesh: Put standalone mesh packages at the bottom. Two competing meshes do not combine; the higher-priority mesh wins for that tile.

Object libraries are dependencies rather than scenery layers and are usually less sensitive to priority, but duplicate or outdated libraries can still cause conflicts. Avoid running two regional overlays for the same area unless their documentation says they are designed to work together.

Free versus payware X-Plane 12 add-ons

Freeware is the sensible choice for utilities, object libraries, overlays, orthophoto tools and several excellent aircraft, while payware becomes more compelling when you need deeper aircraft systems, supported updates or highly detailed airports.

  • Choose freeware for AviTab, pushback, checklists, X-World, orthophoto creation and dependency libraries. The Zibo 737-800X also proves that a complex airliner does not have to be payware.
  • Consider payware for a particular aircraft variant unavailable as credible freeware, professionally supported avionics, high-detail hub airports or products requiring licensed sounds and data.
  • Check before installing or buying: Confirm explicit XP12 compatibility, supported operating systems and processor architectures, required libraries, update arrangements and whether the package is still maintained.
  • Read the refund policy: Payware being advertised for X-Plane does not necessarily mean it is native to X-Plane 12, and digital-download refund restrictions can be strict.

Which free X-Plane 12 add-ons should I install first?

Install according to the flying you do, not according to the length of somebody else's plugin list.

  • Airliner setup: Begin with the Zibo 737-800X, then add AviTab, XChecklist and BetterPushback individually.
  • VFR setup: Start with a light aircraft and one X-World region. Add a small orthophoto area only after the overlay works correctly.
  • Low-maintenance setup: Use AviTab and XChecklist, relying on XP12 Global Airports and built-in real weather.
  • Scenery-focused setup: Test one custom airport first, then its required libraries, followed by the regional overlay and finally imagery.
  • Scripted setup: Install FlyWithLua NG only when a specific XP12-compatible script requires it.

Will X-Plane 11 add-ons work in X-Plane 12?

Some X-Plane 11 airports work in X-Plane 12, but aircraft, plugins and scripts need explicit compatibility checks and should not be presumed safe.

  • Aircraft: An older aircraft may load while retaining broken displays, sounds, flight dynamics or aircraft-specific plugins. Prefer a dedicated XP12 package.
  • Plugins: The plugin must support XP12, the operating system and the computer's processor architecture. Check Log.txt if it does not appear in the Plugins menu.
  • Scenery: Airports transfer more readily than aircraft, but changed terrain, vegetation and assets can produce floating buildings, duplicate objects or missing details.
  • Lua scripts: Treat scripts that alter private datarefs as version-specific. A script can run without displaying an error while no longer producing its intended result.

Keep an untouched copy before testing older content. Never overwrite an XP12 aircraft with files from an XP11 package simply because their folder names match.

How do I install free X-Plane 12 add-ons?

Extract each package, identify its actual root folder and place it in the destination for that add-on type.

  1. Confirm native compatibility. Look for an explicit X-Plane 12 statement and check operating-system, processor and dependency requirements.
  2. Extract the archive fully. Do not run an aircraft or plugin directly from a compressed file. Inspect the resulting directory for an extra wrapper folder.
  3. Install aircraft correctly. Put aircraft under X-Plane 12/Aircraft. The aircraft's main directory should contain its .acf file. Keep third-party aircraft outside Aircraft/Laminar Research.
  4. Install global plugins correctly. Put them under X-Plane 12/Resources/plugins. Aircraft-specific plugins must remain inside that aircraft's own plugins folder.
  5. Install scenery correctly. Put each scenery package under X-Plane 12/Custom Scenery, preserving multi-part package names and structure.
  6. Install every listed library. Missing OpenSceneryX or MisterX Library assets can leave an airport empty or prevent it from loading correctly.
  7. Set scenery priority. Close X-Plane before editing Custom Scenery/scenery_packs.ini. Keep airports above overlays, imagery and mesh.
  8. Test one addition. Load the relevant aircraft or location, close X-Plane normally and inspect X-Plane 12/Log.txt before installing anything else.

Log.txt is rewritten when X-Plane starts, so preserve it immediately after the failed session. Search for the add-on's folder name, missing resources and plugin-loading errors rather than reading only the final few lines.

How should I manage updates and add-on conflicts?

A small amount of version control prevents most broken-aircraft and plugin-conflict problems.

  • Record versions: Keep the downloaded archive, release date and installation notes until the add-on has been tested.
  • Back up configuration: Save working copies of scenery_packs.ini, aircraft preferences and custom checklist files before major changes.
  • Use clean updates: When the developer calls for a full install, replace the old package rather than merging folders. Restore liveries and personal files only afterwards.
  • Disable before deleting: Move a suspect plugin outside Resources/plugins, move an aircraft outside Aircraft, or disable the relevant scenery entry while testing.
  • Change one item at a time: Do not update the simulator, five plugins and an aircraft immediately before a planned flight.
  • Reconfirm compatibility: After a major XP12 update, check that aircraft-specific plugins, Lua scripts and visual tools still declare support.

Why is an X-Plane 12 add-on missing or broken?

Most failed add-ons result from an extra folder level, an unsupported plugin binary, a missing scenery library or incorrect priority in scenery_packs.ini.

  • Aircraft missing from the menu: Locate its .acf file. If it is buried inside two identically named folders, move the real aircraft folder up one level.
  • Plugin missing from the menu: Check Log.txt for loading failures, operating-system security blocks or an unsupported architecture. Confirm that the plugin itself is not nested too deeply.
  • Airport has empty areas: Look for missing-resource messages and install every object library named in the airport documentation.
  • Orthophoto is hidden: Move its overlay above the photo tile and keep the custom airport above both. Check that another higher-priority mesh is not masking the tile.
  • Buildings appear twice: Two overlays or an airport without suitable exclusions are probably covering the same area. Disable one overlay and reload the location.
  • Scenery causes stutters: Dense X-World objects and streamed AutoOrtho tiles load different parts of the system. Disable one package at a time to identify whether object density, storage, network delivery or memory is responsible.
  • X-Plane crashes after plugin changes: Remove the newest plugin first and retest with the same aircraft and airport. Bulk installation makes this diagnosis needlessly difficult.

The most dependable XP12 setup is not the one containing the most add-ons. A focused collection of native packages, installed cleanly and checked in Log.txt, is easier to update and far less likely to fail before a flight.

AI Assistant New

Still stuck? Ask Fly Away

Ask Fly Away is our AI flight-sim assistant. Ask your exact question and get a direct, step-by-step answer in seconds — free to try.

Ask Fly Away Free preview · unlimited for PRO members