Find the MSFS aircraft file location on PC, including Community and Official folders, custom paths, MSFS 2020/2024 differences and console limits.
On PC, Microsoft Flight Simulator (MSFS) stores manually installed aircraft packages in the active Community folder. Locally downloaded Microsoft and Marketplace aircraft use simulator-managed Official package storage. The parent path changes with the MSFS version, storefront and custom installation; console package files are not available through normal file access.
Where MSFS stores each type of aircraft
The aircraft location depends on who supplied the package and which version of Microsoft Flight Simulator is running.
| Aircraft type | Location | What to expect |
|---|---|---|
| Manually installed freeware or third-party add-on | [InstalledPackagesPath]\Community | Usually one or more package folders containing files such as manifest.json and layout.json. |
| MSFS 2020 default or Marketplace aircraft | [InstalledPackagesPath]\Official\OneStore or [InstalledPackagesPath]\Official\Steam | Folder names may be internal product identifiers, and protected content may not be editable. |
| MSFS 2024 Microsoft or Marketplace aircraft | Simulator-managed package storage | Some content is streamed rather than retained as a complete conventional aircraft folder. |
| Simulator application files | Microsoft Store, Xbox app or Steam application directory | This is generally not where manually installed aircraft belong. |
With the default MSFS 2020 locations, the Community folder is commonly found at %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community for the Microsoft Store/Xbox app edition, or %APPDATA%\Microsoft Flight Simulator\Packages\Community for Steam. These examples stop being reliable once the Packages directory has been moved.
Do not assume that the large application directory under WindowsApps or the Steam library is the aircraft folder. Our explanation of the difference between the application and writable Packages locations covers that common mix-up.
How do I find the active MSFS aircraft folder?
The InstalledPackagesPath entry in UserCfg.opt is the most reliable way to identify the Packages folder actually used by the simulator.
- Close Microsoft Flight Simulator. This prevents package scanning or configuration changes while you inspect the folders.
- Locate
UserCfg.opt. Its location varies between Microsoft Store, Xbox app, Steam and simulator versions; use our steps for finding UserCfg.opt and its package-path setting. - Open the file in a text editor. Find
InstalledPackagesPath, normally near the end, and note the path that follows it. - Open that path in File Explorer. The active
Communityfolder is directly beneath it. In MSFS 2020, locally installed official content is beneathOfficial. - Check the package root. A conventional Community package normally exposes
manifest.jsonandlayout.jsonnear its top level. One product can contain separate aircraft, livery and shared-library packages.
For MSFS 2024, use the active path rather than copying an MSFS 2020 directory from another guide. Our MSFS 2024 package-location instructions explain its separate application and content locations.
Why can’t I find a particular installed aircraft?
An aircraft can appear in the simulator without existing as a plainly named folder inside Community.
- Marketplace aircraft belong to managed content storage: they are not normally placed in
Community, even when made by a third-party developer. - MSFS 2024 can stream content: a complete local aircraft package may not exist until the simulator downloads or caches what it needs.
- Package names differ from aircraft names: search for the developer or product identifier as well as the cockpit’s displayed aircraft name.
- A livery is not the base aircraft: its package may contain only texture and configuration references to another installed package.
- Old Community folders remain after moving Packages: this is a mistake we see constantly. Only the folder beneath the active
InstalledPackagesPathis scanned. - ZIP files and extra wrapper folders are not valid installations: the simulator must be able to reach the package manifest at the expected level. Our aircraft package installation checks show the correct folder structure.
Can I edit or move installed aircraft files?
Community packages can usually be moved or backed up while MSFS is closed, but official and Marketplace packages should be left under simulator control.
Direct edits to managed packages may fail because the content is protected, split across dependencies or restored during an update. For modifications, use a separate Community package rather than changing the original aircraft files.
Can console users access MSFS aircraft files?
Xbox and PlayStation users cannot browse the MSFS Community or Official package folders through normal console file access.
Aircraft on Xbox Series X|S must be installed and managed through the simulator’s supported content system. The same restriction applies to MSFS 2024 on PlayStation 5 and PS5 Pro; MSFS 2020 was not released for PlayStation.