Find out which MSFS 2020 add-ons work in MSFS 2024, what commonly breaks, and how to test Community packages safely without damaging either install.
Many Microsoft Flight Simulator 2020 add-ons work in Microsoft Flight Simulator 2024, but compatibility is not guaranteed. Simple scenery, airports and some liveries often transfer successfully; complex aircraft, utilities and packages using custom code commonly require a dedicated update. Test every add-on separately and prefer explicit developer support.
MSFS 2024 was designed to retain broad support for 2020-format content, but backward compatibility is a capability, not certification that every package will work. An add-on can appear in the aircraft or airport list and still fail during normal use.
Which MSFS 2020 add-ons usually work in MSFS 2024?
Static scenery and other packages built mainly from models and textures have the best chance of working without modification.
| Add-on type | Typical prospect | Main compatibility risk |
|---|---|---|
| Landmarks and basic scenery | High | Changed terrain or default objects may create clashes. |
| Airport scenery | Medium to high | Elevation errors, duplicate buildings, jetway faults and changed airport layouts. |
| Liveries | Medium to high | The base aircraft, model variant or texture mapping may have changed. |
| Simple aircraft | Medium | Gauges, sounds, animations and flight behaviour may not transfer completely. |
| Complex aircraft | Low without a confirmed update | Custom avionics, EFB functions, systems code, failures and aircraft-specific dependencies. |
| Missions and activities | Low to medium | Dependence on changed mission logic, triggers, objectives or interface behaviour. |
| External utilities | Variable | Changed simulator interfaces, installation paths, connectors or process detection. |
| Camera, weather and interface mods | Low to medium | Direct reliance on simulator behaviour that changed between versions. |
Use this as a triage rule rather than a guarantee. Trial scenery and liveries first; wait for confirmed MSFS 2024 support before relying on a study-level aircraft, mission pack or operational utility.
Why do some MSFS 2020 add-ons break in MSFS 2024?
Add-ons break when they depend on systems, data or interfaces that MSFS 2024 handles differently from MSFS 2020.
- Custom aircraft code: bespoke avionics, tablets, navigation logic, sound systems, gauges and failures may need to be rebuilt or adjusted for 2024.
- Changed default scenery: revised terrain, airports and world data can expose old exclusions or produce duplicate terminals, floating objects and runway steps.
- Aircraft dependencies: a livery or modification may refer to a particular base-aircraft package, model name or variant that is not identical in 2024.
- External connections: utilities using simulator interfaces may need a newer connector, installer or 2024-specific profile.
- Old conversions: abandoned packages and add-ons already converted from much older simulators carry a higher risk than maintained MSFS SDK projects.
MSFS 2024 is a separate simulator rather than an in-place update. Our practical comparison of MSFS 2020 and MSFS 2024 explains the underlying changes without assuming that shared technology means universal add-on support.
How should I move and test MSFS 2020 add-ons in MSFS 2024?
Move only the latest version of one package at a time into the correct MSFS 2024 location, then test it in a repeatable flight before adding anything else.
Can I copy the whole MSFS 2020 Community folder?
No. Do not copy the entire Community folder in one operation or point both simulators at the same live folder.
The mistake we see most often is transferring hundreds of packages and then trying to identify which one caused a loading hang, crash to desktop or broken cockpit. Keep the working 2020 installation untouched and treat 2024 as a separate environment.
- Manually installed Community packages: copy or extract them individually into the MSFS 2024
Communityfolder. - Marketplace content: install and manage it through the simulator rather than copying files from an official-content directory.
- External utilities: use an installer or release that explicitly supports MSFS 2024. Copying an old program folder rarely updates its connectors or configuration.
For a conventional Community package, the folder containing files such as manifest.json and layout.json belongs directly inside Community. An extra nested folder is a common reason an add-on does not appear at all. The package-layout explanation in our MSFS 2020 mod-installation guide provides useful background, although 2024 must use its own folder path.
Safe add-on test procedure
A clean, one-at-a-time test is the only reliable way to distinguish genuine compatibility from an add-on that merely reaches the loading screen.
- Check the support status. Obtain the latest legitimate release and read its requirements, dependencies and MSFS 2024 notes. If the developer supplies a distinct 2024 package, use that one.
- Back up the working files. Preserve the original package and do not overwrite your known-good MSFS 2020 installation with a 2024-specific update.
- Establish a clean baseline. Start MSFS 2024 without the package and confirm that the same aircraft, airport and flight load normally.
- Add one package. Restart the simulator after installing it. Do not add a livery, airport, aircraft and utility together.
- Test the functions that matter. At an airport, inspect runway levels, markings, taxiway signs, stands, jetways and duplicate objects. In an aircraft, check cold-and-dark start-up, displays, flight-plan entry, controls, autopilot, sounds, animations, landing and shutdown.
- Remove it after a clear fault. Relaunch the same test without the package. If the problem disappears, the add-on or one of its dependencies is the likely cause.
- Build up gradually. Only combine packages after each has passed alone. If a fault appears in a batch, return to single-package testing.
Separate libraries prevent version mix-ups
Use separate package libraries, Community folders and add-on-manager profiles for MSFS 2020 and MSFS 2024.
The simulators can reside on the same physical drive, but they should not share one live package directory. A 2024-native update may replace files that an older 2020 build still needs. Our storage guide for keeping both simulator installations organised covers drive choice and folder separation in more detail.
Common incompatibility symptoms and fixes
An add-on is not truly compatible unless its normal functions work without crashes, severe faults or conflicts.
- The add-on does not appear: verify the correct 2024 Community path, remove any extra nested folder and check that required base aircraft or libraries are installed.
- The simulator hangs or crashes: remove the most recently added package, restart and test again. Also check that old and new editions of the same airport or aircraft are not both active.
- Cockpit displays are black or switches are dead: this usually indicates incompatible systems or gauge code. A developer update is more likely to fix it than changing graphics settings.
- Autopilot, EFB or navigation functions misbehave: treat the aircraft as incompatible even if basic hand-flying works.
- Runways or buildings float, sink or duplicate: disable overlapping airport, mesh or landmark packages and keep only one edition of the airport active.
- A livery is missing or distorted: confirm that it targets the exact aircraft and model variant installed in MSFS 2024.
- An external utility opens but does not connect: install its supported 2024 release and select the correct simulator profile or connector. Do not assume an MSFS 2020 executable will detect 2024 automatically.
- Loading times or performance deteriorate sharply: remove the package and repeat the same scenario. A sudden change that disappears after removal points to the add-on or a conflict.
If a package only partly works, classify it as incompatible until it is updated. Being usable for a quick screenshot is not the same as being stable for a full flight.
Marketplace and Xbox compatibility
Marketplace distribution does not by itself prove that an MSFS 2020 add-on is fully compatible with MSFS 2024.
Marketplace availability, entitlement and updates are controlled through the in-sim content system and can differ by product or platform. Use the version offered for MSFS 2024 and look for explicit compatibility information; do not manually move Marketplace files from an official package directory.
On PC, manually obtained Community packages can be isolated and tested as described above. Xbox does not provide the normal writable Community-folder workflow, so users are limited to add-ons made available through the in-sim ecosystem. If an Xbox product has not been released or enabled for MSFS 2024, there is no manual PC-style installation workaround.
Our rule is straightforward: simple static content is reasonable to trial, but custom-coded or operationally essential add-ons should have confirmed MSFS 2024 support. A successful load screen is never enough proof for an aircraft or utility you depend on.