See which MSFS 2020 mods work in MSFS 2024, which need updates, and how to test aircraft, scenery and liveries safely before migrating.
Many Microsoft Flight Simulator 2020 mods work in Microsoft Flight Simulator 2024, but compatibility is not guaranteed. Simple scenery and liveries are the strongest candidates; complex aircraft, avionics, utilities and packages with custom code often need a 2024 update. Keep separate Community folders and test each package individually.
Which MSFS 2020 mods work in MSFS 2024?
Compatibility depends on what the package changes, not merely whether MSFS 2024 can detect it. A mod appearing in the aircraft or airport menu does not prove that its instruments, sounds, animations and dependencies work correctly.
| MSFS 2020 content | Likely compatibility | Main risks in MSFS 2024 |
|---|---|---|
| Airport and scenery packages | Often compatible | Duplicate objects, elevation problems, changed exclusions and conflicts with streamed or updated scenery |
| Liveries | Often compatible when the aircraft model is unchanged | Different model variants, texture mapping, registration systems or 2024-native aircraft versions |
| Simple aircraft | Mixed | Flight-model, sound, effect, animation and cockpit-instrument differences |
| Complex aircraft and avionics | Update commonly required | Custom gauges, WASM modules, model behaviours, external components and simulator API changes |
| Utilities and traffic tools | Update commonly required | External applications, injectors, data connections and dependencies may need explicit 2024 support |
| Activities, missions and career modifications | Generally poor candidates | MSFS 2024 uses different activity and career systems |
Liveries deserve separate checking because compatibility follows the exact aircraft model rather than its marketing name. Our checks for moving MSFS 2020 liveries into 2024 explain the model and texture-mapping issues.
If both a legacy package and a native MSFS 2024 edition exist, use the native edition. Keep the 2020 package only when its author explicitly identifies it as compatible and no separate 2024 build is required.
How do I test a 2020 mod safely in MSFS 2024?
The safest method is to establish a clean, working simulator and introduce one package at a time. Copying an entire MSFS 2020 Community folder makes it much harder to identify the package causing a crash or loading problem.
- Keep the installations separate. Do not point MSFS 2024 at the Community folder used by MSFS 2020. Shared folders and broad symbolic links can expose both simulators to incompatible files.
- Start with an empty MSFS 2024 Community folder. Launch the simulator and confirm that the same aircraft, airport or flight works without add-ons.
- Check for a native update. Replace the old package if its author supplies a version specifically intended for MSFS 2024.
- Extract the package correctly. The package root should normally contain files such as
manifest.jsonandlayout.json. A common mistake is an extra nested directory, producingCommunity\package-name\package-name\manifest.jsoninstead ofCommunity\package-name\manifest.json. - Add one mod and restart the simulator. Test the feature the package actually changes, including cockpit systems, night lighting, sounds, animations and approaches where relevant.
- Add the remaining packages in small groups. If a fault appears, remove the latest group and reintroduce its packages individually.
Do not try to make an old mod compatible simply by editing its manifest version. That may affect detection, but it does not update custom code, aircraft systems, models or dependencies.
Why is an MSFS 2020 mod missing or broken in 2024?
A missing package is usually installed in the wrong Community folder, still compressed, nested too deeply or dependent on content that is not installed. A package that appears but malfunctions is more likely to have a genuine compatibility problem.
- Not listed: confirm that you used MSFS 2024's active Community location rather than the folder belonging to MSFS 2020.
- Pink or missing textures: the package may reference absent textures, an incompatible aircraft model or another required package.
- Aircraft loads with blank instruments: custom avionics, gauges or code probably require an updated build.
- Airport has duplicated buildings or uneven ground: the scenery may conflict with MSFS 2024's streamed airport, terrain or exclusions.
- Simulator crashes while loading: remove the package and verify the same flight with an empty Community folder before investigating other causes.
For installation faults rather than true incompatibility, follow our troubleshooting steps for MSFS 2024 mods that do not appear or load.
What about Marketplace purchases and console mods?
Marketplace content should be installed through MSFS 2024's own content library when a compatible version is available. Do not manually copy protected Marketplace package files from the 2020 installation; ownership does not by itself guarantee that a product has a compatible 2024 edition or the same entitlement on every platform.
Manual Community-folder installation is a PC feature. Xbox Series X|S and PlayStation 5 users cannot copy ordinary PC mods into the simulator and must use content distributed for their console through the in-simulator Marketplace. Our guide to console and PC mod-installation limits explains that distinction in detail.