Where Does Prepar3D Keep Config, Flights and Add-ons?
Prepar3D splits config across Roaming, Local and ProgramData, with flights and add-ons in Documents.
Last updated
Prepar3D spreads its files across five standard roots, all documented by Lockheed Martin. Day-to-day settings live in %APPDATA%\Lockheed Martin\Prepar3D v6 (Prepar3D.cfg), shaders cache in the Local twin, and shared scenery and add-on registration in %PROGRAMDATA%\Lockheed Martin\Prepar3D v6.
Your own files live in Documents: saved flights and flight plans in Prepar3D v6 Files, XML add-ons in Prepar3D v6 Add-ons. Add-on installers should register there through add-ons.cfg instead of touching Program Files, which updates overwrite without asking.
Where Prepar3D stores this, by platform
%APPDATA%\Lockheed Martin\Prepar3D v6
Prepar3D.cfg and per-user state. Shaders in the Local twin, shared scenery and add-ons.cfg in the ProgramData twin, flights in Documents\Prepar3D v6 Files. Back up Documents plus any registered add-on folders before updates.
Frequently asked questions
How do I fully uninstall Prepar3D v6?
Delete the generated folders (Roaming, Local and ProgramData trees) after backing up add-ons, then uninstall. The uninstaller leaves runtime files behind, and Lockheed documents exactly which folders to remove by hand.
Where do I install a third-party aircraft the correct way?
Register it in add-ons.cfg under %PROGRAMDATA%\Lockheed Martin\Prepar3D v6 with its own PATH entry, pointing at a folder outside the install. Never drop third-party files into Program Files; updates wipe them.
Notice an outdated path? Let us know.