Find MSFS camera definition files, saved custom-view configs and the correct Community or Official package path in Microsoft Flight Simulator.
On PC, Microsoft Flight Simulator aircraft camera definitions are normally stored in cameras.cfg inside the aircraft package at SimObjects\Airplanes\<aircraft>. That package is under the active Community or Official folder. Saved custom views use a separate per-user cameras.cfg; Xbox and PlayStation do not expose these files.
Where is cameras.cfg in the MSFS aircraft package?
For locally installed aircraft in Microsoft Flight Simulator 2020 and 2024, the usual relative paths are:
<Packages path>\Community\<package>\SimObjects\Airplanes\<aircraft>\cameras.cfg<Packages path>\Official\<store branch>\<package>\SimObjects\Airplanes\<aircraft>\cameras.cfg
Common MSFS 2020 official branch names include OneStore and Steam. Folder names and capitalisation can vary, and a package containing several aircraft variants may have a separate cameras.cfg for each one. Our explanation of how installed MSFS aircraft folders are organised covers the package structure in more detail.
A livery-only package often has no camera file because it inherits the base aircraft's configuration. Some converted or unusually structured add-ons may place [CAMERADEFINITION.n] sections in aircraft.cfg instead, so search for that section name if cameras.cfg is absent.
How do I find the active Packages folder?
The reliable method is to read InstalledPackagesPath in UserCfg.opt rather than guessing from the simulator's application directory. The location changes with the store edition, simulator generation and any custom package path chosen during installation.
- Locate UserCfg.opt. Follow our instructions to find UserCfg.opt and read its package-path setting.
- Open InstalledPackagesPath. This should lead to the package root containing
CommunityandOfficial. - Select the correct package branch. Manually installed add-ons normally use
Community; Microsoft and Marketplace content normally usesOfficial. - Open the base aircraft package. Continue through
SimObjects\Airplanesand open the aircraft's own folder. - Search for the definition. Look for
cameras.cfg, then search configuration files for[CAMERADEFINITION.if it is not present.
Are saved custom camera views stored in the same file?
No. Package-supplied camera definitions and user-saved custom views can both be named cameras.cfg, but they have different purposes and locations.
| Configuration | Purpose | Expected location |
|---|---|---|
Package cameras.cfg | Default cockpit, external and showcase camera definitions supplied with the aircraft | Inside the aircraft package under SimObjects\Airplanes\<aircraft> |
User cameras.cfg | Custom camera positions saved by the player | Inside the simulator's per-user profile under SimObjects\Airplanes\<aircraft> |
aircraft.cfg | Possible camera sections in converted or non-standard packages | Beside the aircraft's other configuration files |
For Microsoft Store installations, the user file is typically below a package-profile path ending in LocalCache\SimObjects\Airplanes\<aircraft>\cameras.cfg. Steam installations normally use the simulator's roaming profile with the same SimObjects\Airplanes suffix. MSFS 2020 and MSFS 2024 maintain separate profile trees.
The per-user file may not exist until at least one custom camera has been saved for that aircraft. Save a view, exit the simulator normally, then search the simulator profile for recently modified files named cameras.cfg.
Why is the camera definition file missing?
A missing file usually means the wrong package or profile location is being inspected, not that every camera definition has disappeared.
- The aircraft is only a livery. Find the base aircraft package from which it inherits its systems and cameras.
- The wrong Packages folder is open. Custom installations can leave older, inactive copies elsewhere on the drive.
- The aircraft is streamed or protected. Some MSFS 2024 content and protected Marketplace packages are not available as ordinary editable files.
- No custom view has been saved. The simulator has no reason to create the per-user camera file yet.
- AppData is hidden. Enable hidden items or enter the profile path directly in File Explorer.
- The definitions are in another configuration file. Search the package contents for
CAMERADEFINITIONrather than relying only on the filename.
The mistake we see most often is editing an inactive duplicate of the package. If a valid-looking change has no effect, confirm the package path and check whether another copy of the same add-on is taking priority.
Can I edit or reset cameras.cfg safely?
Unprotected camera configuration files can be edited on PC, but close Microsoft Flight Simulator and make a backup first. Direct edits inside Official can be replaced by an update, while malformed sections may stop a camera definition from loading.
- Change only the active aircraft variant's file.
- Preserve the configuration section structure and numbering.
- Rename the per-user
cameras.cfgto reset custom views without immediately destroying the backup. - Keep repeatable aircraft modifications in a separately maintained Community add-on when the aircraft's licence and package design permit it.
If the aim is simply to save, switch or reset viewpoints, file editing is usually unnecessary. Our MSFS camera-control reference explains cockpit, external, drone and custom-view commands.