Create an MSFS 2020 mod with the official SDK. Learn project setup, package building, Community testing and fixes for mods that do not load.
To create a mod for MSFS 2020, use the PC simulator's SDK and Developer Mode. Start a project, add a package and the right asset group for scenery, aircraft or other content, build it, then test the compiled package through the Community folder. Never edit the Official folder.
What do you need to make an MSFS 2020 mod?
You need the Windows PC version of Microsoft Flight Simulator 2020, its matching SDK, Developer Mode and suitable asset-creation software. Authoring is not available on Xbox, and Xbox cannot load loose Community packages.
Enable Developer Mode under Options - General Options - Developers. This adds the development toolbar containing tools such as the Project Editor, Scenery Editor and package builder. Our detailed SDK installation and Developer Mode walkthrough covers the initial setup.
The external software depends on the mod. Liveries need an image editor capable of producing the required DDS textures; new models need compatible 3D modelling and SDK export tools; aircraft systems may involve XML, HTML, JavaScript or WASM development.
Which mod type should you start with?
A livery or small scenery package is the best first MSFS 2020 mod because either teaches the package system without requiring a complete aircraft model and systems simulation.
| Mod type | Difficulty | Main work |
|---|---|---|
| Livery | Beginner | Edit an authorised paint kit, export textures and create the aircraft configuration package. Follow our livery texture and configuration workflow. |
| Airport or scenery | Beginner to intermediate | Place objects, polygons and other scenery elements, then compile them into a BGL package. Our practical start-to-finish scenery example shows the complete process. |
| Aircraft configuration change | Intermediate | Override supported configuration or system files through a separate package without altering the installed aircraft. |
| Complete aircraft | Advanced | Create the model, levels of detail, animations, materials, flight model, cockpit, systems, effects and sounds. |
How do you build an MSFS 2020 mod?
- Create a separate workspace. Keep the source project outside both
CommunityandOfficial. A short local path with normal Latin characters also avoids many tool and permissions problems. - Start a project. Open the Project Editor from the Developer Mode toolbar and create a project with a unique, stable name. Do not reuse another add-on's package name.
- Add a package and asset group. Select the asset group appropriate to the content, such as scenery or a SimObject. Asset groups tell the package builder which source files to process and where their compiled output belongs.
- Create the assets. Work in the relevant in-sim editor or an external graphics, audio or modelling application. Keep editable source files separate from the files intended for the simulator.
- Build the package. Run the project build command and inspect the Developer Console. Resolve red build errors rather than assuming the package is usable because some objects appeared during editing.
- Test the compiled output. Copy only the built package folder to the active Community folder, remove any older copy and restart the simulator. The active folder varies between installations, so use our instructions for checking the Community location and correct package nesting.
- Perform a cold test. Close the source project and launch MSFS 2020 normally. Test the package with an otherwise empty Community folder, because a project loaded in Developer Mode can hide missing files and dependencies.
What should the finished package contain?
The distributable package root should contain manifest.json, layout.json and the compiled content folders required by that mod. The exact content structure differs between scenery, SimObjects, materials and other package types.
Let the package builder create or update layout.json whenever the payload changes. This file inventories the packaged files; a stale layout is a common reason why a new texture, model or configuration file is ignored.
Do not distribute the project workspace, temporary build folders or editable source assets unless you deliberately intend to release a development kit. A correctly nested installation should resemble Community/publisher-package/manifest.json, not Community/publisher-package/publisher-package/manifest.json.
Common reasons an MSFS mod does not appear
- Wrong Community folder: MSFS installations can have more than one folder named Community. Confirm the active packages path rather than relying on a path copied from another installation.
- Source files were installed: the Project Editor files are not the finished mod. Install the compiled package produced by the build process.
- The package is one folder too deep:
manifest.jsonandlayout.jsonmust be in the package root. - The layout is stale: rebuild the package after adding, removing or changing files instead of copying a changed file into an old build.
- An old version remains installed: delete the previous package before copying the replacement so obsolete files cannot survive the update.
- There is a package-name or object-ID collision: use identifiers unique to your project. Duplicating another mod's identifiers can cause one package to override the other.
- A dependency is missing: test against a clean Community folder, then add declared dependencies deliberately. Do not assume another unrelated add-on will always be installed.
- The project references local source paths: a package that works only while its source project is loaded is incomplete. Test the compiled build after Developer Mode has been closed.
Packaging, copyright and platform limits
An MSFS 2020 mod should add or override content through the virtual package system; it should not replace files inside Official. Direct edits are vulnerable to simulator updates, cannot be packaged cleanly and may trigger a repair or redownload.
Use original assets, properly licensed material or an authorised paint kit. Do not redistribute Microsoft aircraft models, stock textures, another developer's work or decrypted Marketplace content. Referencing an installed package as a dependency does not grant permission to copy its files.
Community-folder mods are for PC. Xbox users can only obtain add-ons delivered through supported in-simulator channels, which require a separate publishing and approval process rather than a downloadable folder.