Learn whether Prepar3D aircraft can be converted to MSFS 2020, what must be rebuilt, why folder copying fails, and when permission is required.
Prepar3D aircraft add-ons cannot usually be converted to Microsoft Flight Simulator 2020 with a one-click tool. A proper port requires the editable source model, permission from the copyright holder, and substantial redevelopment with the MSFS SDK. Copying a compiled Prepar3D aircraft folder into the Community folder will not work.
Why are Prepar3D aircraft incompatible with MSFS 2020?
Prepar3D and Microsoft Flight Simulator 2020 use different aircraft models, rendering systems, cockpit frameworks and package structures. Their common Flight Simulator ancestry means some configuration concepts and filenames look familiar, but that does not make the finished add-ons interchangeable.
Prepar3D aircraft may depend on compiled MDL models, platform-specific material definitions, XML or C++ gauges, custom DLL modules and Prepar3D-specific SDK functions. MSFS 2020 expects aircraft packaged and built for its own SDK, normally with native glTF models, MSFS behaviours and compatible instrument code. Our explanation of the technical differences between Prepar3D and Microsoft Flight Simulator covers the wider platform split.
An aircraft inherited from FSX may offer more usable source material than a Prepar3D-native product, but it still is not automatically compatible. The same limitations affecting legacy FSX aircraft and gauges in modern MSFS generally apply.
Is there a one-click P3D-to-MSFS converter?
No universal converter can turn a completed Prepar3D aircraft into a fully working MSFS 2020 aircraft. A utility might translate geometry or configuration data, but it cannot automatically recreate cockpit systems, animations, avionics, materials, flight dynamics and sounds correctly.
A compiled .mdl file is also not equivalent to the original 3D project. Even where geometry can be inspected or translated, authoring data, animation logic, material setup and level-of-detail work may be missing. Complex airliners and military aircraft with custom systems are effectively redevelopment projects rather than simple conversions.
What must be rebuilt for a proper conversion?
A legitimate conversion starts with editable source files and treats the Prepar3D aircraft as reference material for a new MSFS package.
| Aircraft component | Realistic conversion work |
|---|---|
| 3D model | Re-export the editable source in an MSFS-native format, then check scale, origins, LODs, collision geometry and visibility conditions. |
| Textures and materials | Reuse licensed artwork where suitable, but rebuild material assignments and any required PBR texture maps. |
| Animations | Retag or recreate control surfaces, landing gear, switches, doors, lights and cockpit interactions using MSFS behaviours. |
| Gauges and systems | Rewrite unsupported XML logic, C++ gauges and Prepar3D DLL modules against frameworks supported by MSFS. |
| Flight model | Use existing values only as a reference, then configure and test the MSFS flight, engine, fuel and contact-point definitions. |
| Sounds | Licensed recordings may be reusable, but the aircraft's sound package and events normally need rebuilding. |
For developers who own the source and rights, the broad process is:
- Check the licence and source files. Confirm that modification is allowed and that the editable model, textures, sounds and system code are available.
- Create an MSFS SDK project. Build the correct aircraft package structure rather than manually renaming or moving Prepar3D folders.
- Export the visual model. Rework materials, LODs, animations, attachment points and cockpit behaviours for MSFS.
- Rebuild the systems. Replace incompatible gauges, modules and avionics code instead of attempting to load Prepar3D binaries.
- Configure the aircraft. Recreate the flight model, engines, fuel system, electrical system, cameras, effects and sounds as required.
- Test every operating state. Check cold-and-dark starts, cockpit controls, autopilot behaviour, lights, doors, ground handling and aircraft loading before distribution.
Can I copy a Prepar3D aircraft into the Community folder?
No. The MSFS 2020 Community folder loads compatible MSFS packages; it does not convert files placed inside it. A copied Prepar3D aircraft will usually be ignored, fail to appear in the aircraft selector, or load with missing models and unusable systems.
Obtain a native MSFS release or an authorised port, then follow our instructions for installing MSFS aircraft packages. If a package advertised specifically for MSFS still does not appear, check the common causes of missing add-on aircraft, including nested folders and missing dependencies.
Can a converted Prepar3D aircraft be shared?
A converted aircraft can be distributed only when its licence or copyright holder permits derivative work and redistribution. Freeware is not automatically open source, and purchasing payware does not grant permission to extract, modify or republish its models, textures, sounds or code.
Private modification may also be restricted by the product licence. Encrypted or protected files should not be bypassed, and an aircraft must not be uploaded without the necessary rights. The clean route is explicit permission from the original developer, ideally accompanied by the editable source assets.
Should you convert the aircraft or replace it?
Most users should choose a native MSFS aircraft rather than attempting a conversion. Rebuilding is sensible only when the rights and source assets are available and the work can be tested to MSFS standards.
- Choose a native replacement if you are an end user, have only compiled Prepar3D files, or need complex avionics and systems.
- Plan a full redevelopment if you are the original developer or have written permission, editable source files and experience with the MSFS SDK.
- Do not proceed when the aircraft is encrypted, its licence forbids modification, or ownership of the underlying assets is unclear.