How do I update X-Plane 12 to the latest version?

To update X-Plane 12, close the simulator, back up any modified default files, then run the X-Plane 12 Installer and choose Update X-Plane. Steam installations update through Steam instead. Keep beta updates disabled unless you accept add-on breakage, and verify that you are updating the correct installation folder.

Which X-Plane 12 updater should I use?

The correct update method depends on how your copy of X-Plane 12 is managed.

Do not use the standalone installer on a Steam-managed copy. The updater also works as a repair tool, as explained in our installer and repair walkthrough for PC and Mac.

Updating with the X-Plane 12 Installer

Installer-managed copies are updated by scanning the selected X-Plane folder and replacing outdated or missing stock files.

1. Close X-Plane and related tools. Stop utilities that mount, read or write files inside the installation so that nothing is locked during the update.
2. Back up personal changes. Updates normally preserve custom content, but save manually edited stock files and irreplaceable data such as control profiles and logbooks. Any alteration made directly to a default aircraft, plugin or scenery file may be overwritten.
3. Run a recent X-Plane 12 Installer. Choose Update X-Plane. If the installer is missing or cannot connect, obtain a fresh copy from the official source used for your purchase.
4. Select the installation root. Choose the folder containing the X-Plane executable and folders such as Aircraft, Custom Scenery and Resources. A mistake we see constantly is selecting one of those subfolders rather than the X-Plane 12 root.
5. Choose the release channel. Leave the beta option off for the latest stable release. Enable it only if you deliberately want a test build.
6. Allow the scan and download to finish. If the installer finds modified stock files, replacing them gives you the clean files supplied with the selected release. Keep a separate copy of any edits you still need.
7. Launch and verify the build. Check the build number displayed by X-Plane or recorded near the beginning of Log.txt. Test a default aircraft at a default airport before diagnosing add-on problems.

Each X-Plane installation is independent. If you keep separate stable, beta or development copies, the installer updates only the folder you selected.

Updating the Steam edition

Steam copies should be updated only through Steam, which normally downloads the newest build assigned to the selected release branch.

1. Exit X-Plane 12. Check that it is no longer running in the background.
2. Open the Steam download queue. Resume any paused X-Plane 12 update and allow it to finish before launching the simulator.
3. Check the branch selection. In X-Plane 12's properties, select no beta branch if you want the latest stable release. Menu wording may vary slightly between Steam client versions.
4. Verify installed files if necessary. Steam's file-verification function repairs missing or corrupted stock files. It can also replace stock files you have edited, so back those up first.

If no update appears, restart Steam, check that downloads are not paused and confirm that sufficient free disk space is available. Steam may need extra temporary space while unpacking an update.

Should I install the latest X-Plane 12 beta?

Use the stable release for normal flying; install a beta only when you are prepared to test unfinished changes and troubleshoot compatibility.

A beta can be newer than the recommended public build, but that does not make it the best choice for an established add-on setup. Aircraft systems, third-party plugins, weather tools and graphics behaviour may change during testing. Keeping a separate X-Plane copy for beta testing protects a known-working stable installation.

To return to stable, disable beta updates in the installer or leave the Steam beta branch, then run the update or file-verification process again. This restores the stock files belonging to the stable channel.

What does an X-Plane 12 update not update?

An X-Plane update refreshes simulator files supplied with that build, but it does not maintain every third-party component around the simulator.

• Add-on aircraft, plugins and scenery: update these using the method supplied with each add-on. Do not assume compatibility merely because X-Plane starts successfully.
• Custom navigation data: an application update does not guarantee that data in Custom Data matches the desired AIRAC cycle. Follow our separate X-Plane navdata update steps when procedures or waypoints are missing.
• Unselected global scenery regions: a core update does not automatically install regions that were never selected. Manage those through the standalone scenery installer or Steam's content controls, depending on the installation type.
• X-Plane 11: the X-Plane 12 updater does not convert or replace an X-Plane 11 installation.
• External applications and device drivers: traffic clients, mapping tools, headset software and graphics drivers are maintained separately.

Why won't X-Plane 12 update?

Most failed X-Plane 12 updates come from selecting the wrong copy, using an outdated installer, lacking write permission or having insufficient disk space.

The installer says X-Plane is up to date

Check the selected folder and the build recorded in that copy's Log.txt. Users with several installations often update one copy and then launch another through an old desktop shortcut. Also confirm whether the version you expect is a beta while your installer is set to stable.

The download stalls or files fail verification

Close the updater, confirm the destination has free space and write permission, then retry with a fresh installer. Check whether security software has quarantined or blocked the updater rather than permanently disabling protection. On Steam, clear any paused-download condition and run file verification.

Do not delete the entire installation as a first response. Both the standalone installer and Steam can replace damaged stock files while normally leaving unrelated custom folders in place.

X-Plane crashes after the update

Start by testing a default aircraft without third-party plugins. Move only third-party plugin folders out of Resources/plugins, leave stock components untouched, and reintroduce the add-ons in small groups. The final lines of Log.txt often identify the plugin or aircraft loaded immediately before the failure.

Review our guidance on X-Plane mod folders and compatibility checks before restoring older add-ons. Never copy an entire pre-update stock folder back over the updated installation, because that can silently revert files the new build requires.