How do I install mods in Microsoft Flight Simulator 2020?

To install most Microsoft Flight Simulator 2020 mods on PC, close the simulator, extract the downloaded archive, and place the add-on’s actual package folder inside the active Community folder. Check that manifest.json and layout.json are directly inside that package folder, then restart MSFS. Marketplace items install through the simulator instead.

Which MSFS 2020 mods go in the Community folder?

Standard aircraft, liveries, airports, scenery, missions, sounds and effects packages normally belong in Community. In MSFS 2020, “mod” and “add-on” are often used for the same thing, but not every download uses the same installation method.

If a download supplies specific instructions, those take precedence over the general Community-folder method. Do not force a traffic tool, launcher or external utility into Community unless its documentation tells you to.

You can find aircraft, scenery and utilities in our MSFS freeware library. Check that a listing explicitly supports Microsoft Flight Simulator 2020; an add-on made only for MSFS 2024, FSX, Prepar3D or X-Plane is not automatically compatible.

Marketplace packages are easier to install and update, while manual packages give you direct control over their files. Our Marketplace-versus-manual comparison explains when each option makes sense.

How to install MSFS 2020 mods on PC

For a standard manual package, extract it, identify the real package root, and copy that folder into the active Community directory.

1. Check compatibility and dependencies

   Read the supplied instructions and confirm that the mod supports MSFS 2020 on PC. A livery may require a separate aircraft, while some scenery packages depend on an additional library.

2. Close Microsoft Flight Simulator

   Do not change package files while the simulator is running. Closing MSFS also ensures that the new package is scanned during the next start.

3. Extract the download

   Unpack the ZIP, RAR or 7z archive to a temporary location. Copying the compressed archive itself into Community will not install it.

4. Find the actual package folder

   A standard package usually has manifest.json and layout.json at its first level. Ignore outer download folders containing screenshots, documentation or another folder with the real package inside.

5. Open the active Community folder

   Use the packages location selected by your MSFS installation. Steam, Microsoft Store and custom installations can use different directories.

6. Copy the package folder

   Place the whole package folder inside Community. If an archive contains several separate package folders, copy each package root rather than the wrapper around all of them.

7. Restart MSFS and verify the add-on

   Aircraft should appear in the aircraft selector, liveries beneath their required aircraft, and airports or scenery at the relevant location. Remove any active search or category filter before deciding that an aircraft is missing.

The same method applies to most third-party aircraft. Our aircraft-specific installation walkthrough shows how to recognise the correct package folder for that type of add-on.

Where is the Community folder in MSFS 2020?

The active Community folder is inside the packages location recorded by MSFS, which may differ from the folder containing the simulator’s main programme files.

These are common defaults, not guaranteed locations. If you selected another packages directory during installation, the custom location is the one MSFS reads.

The reliable check is the simulator’s UserCfg.opt file. For Microsoft Store installations it is commonly under %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache; for Steam it is commonly under %APPDATA%\Microsoft Flight Simulator. Open UserCfg.opt in a text editor and find InstalledPackagesPath. Open the path shown on that line, then open its Community folder.

You can paste paths beginning with %LOCALAPPDATA% or %APPDATA% into the File Explorer address bar. Do not place ordinary manual mods in Official; that area is managed by MSFS and its content system.

How should an MSFS package folder be structured?

A standard package is at the correct depth when manifest.json and layout.json sit immediately inside its own folder.

Correct:

• Community\publisher-addon\manifest.json
• Community\publisher-addon\layout.json

Usually wrong:

• Community\download-wrapper\publisher-addon\manifest.json

In the second example, publisher-addon is the folder that belongs in Community. The extra wrapper is the installation mistake we see most often. Do not flatten the package by placing its individual files directly in Community, either.

Why is my mod not showing up in MSFS 2020?

A missing mod is usually caused by an unextracted archive, an extra wrapper folder, the wrong Community directory or an incompatible package.

• The archive was not extracted: remove the ZIP, RAR or 7z file and copy the unpacked package folder instead.
• The package is one folder too deep: move the folder containing manifest.json and layout.json directly into Community.
• You used the wrong Community folder: verify InstalledPackagesPath in UserCfg.opt, especially after reinstalling MSFS or changing drives.
• MSFS was not restarted: close it fully and launch it again after changing packages.
• The simulator is in Safe Mode: Safe Mode deliberately disables third-party Community content. Start in Normal Mode when testing the add-on.
• The package targets another simulator: MSFS 2024-only, FSX, Prepar3D and X-Plane files cannot be treated as MSFS 2020 packages.
• A dependency is missing: check the documentation for a required base aircraft, scenery library or other package.
• Two versions are installed: remove old and duplicate copies so only one version remains in Community.
• A simulator update broke compatibility: an older package may need an update from its developer before it will load correctly again.
• The extraction failed: if the extraction tool reports missing files or an excessively long path, extract to a short temporary location and try again.
• The add-on has no obvious menu entry: scenery normally appears only at its geographical location, and a livery appears under the aircraft it was made for.

Normal Community packages do not require manual registry changes or edits to Content.xml. Avoid applying unrelated fixes unless the add-on’s own instructions specifically require them.

What should I do if MSFS crashes after installing a mod?

Remove the newest package first and restart MSFS; if the problem continues, test with the entire Community folder empty.

Move its contents to a temporary folder outside the simulator rather than deleting everything. If MSFS starts normally, return packages in small groups until the faulty or incompatible add-on is identified. Install one new package at a time in future so the cause is obvious.

If MSFS still fails with Community empty, the manual mod is unlikely to be the cause. Continue with our PC launch troubleshooting checklist.

How do I update, disable or uninstall an MSFS mod?

Manual mods are managed by replacing or removing their package folders while Microsoft Flight Simulator is closed.

• To update a mod: remove the old package folder, copy in the new version, and restart MSFS. Replacing the complete folder avoids obsolete files being left behind.
• To uninstall a mod: delete its package folder from Community, then restart the simulator.
• To disable a mod temporarily: move its folder somewhere outside Community. Merely renaming it inside Community may not stop MSFS from scanning it.
• For Marketplace content: update or remove it through the simulator’s content-management system rather than deleting managed files manually.

Keep downloaded archives and backups outside Community, and retain only one installed version of each package. This prevents duplicate package conflicts and makes troubleshooting far easier.

Can you install MSFS 2020 mods on Xbox?

Xbox consoles cannot use ordinary manual Community-folder mods because users do not have access to the required package directory.

On Xbox, add-ons must be distributed through Microsoft Flight Simulator’s own Marketplace and content system. The manual PC procedure above applies to Windows installations, including MSFS obtained through the Xbox app, but not to an Xbox console.