Why You Must Reliably Backup Your MSFS Setup Before It’s Too Late

Microsoft Flight Simulator (MSFS) has grown into one of the most robust and moddable consumer simulation platforms ever created. With thousands of hand-crafted scenery packages, realistic aircraft modifications, custom airport configurations, and deeply personalized controller and display settings, your MSFS installation can represent hundreds of hours of curation and fine-tuning. A single Windows update, graphics driver instability, SSD failure, or even a broken add-on can wipe out that entire ecosystem in seconds. That is why a proactive, layered backup strategy for your MSFS settings and add-ons is not optional — it is a core part of being a responsible simmer.

This guide expands the standard manual copy approach into a complete system of reliable, versioned backups that protect every critical component: the Community folder, the Official folder (which can be rebuilt), the roaming configuration files, your custom snapping views, key bindings, and even your marketplace purchase cache. You will learn the best manual methods, automation scripts, third-party tools, and cloud-based solutions, as well as step-by-step restoration instructions to get you back in the cockpit as fast as possible.

What Exactly Needs to Be Backed Up?

Before selecting a method, you must know precisely which files and folders define your unique MSFS setup. Missing even one file can mean losing all your controller profiles or facing a blank “Community” folder after a reinstall.

The Community Folder (The Most Critical)

Your Community folder contains every third-party add-on: aircraft, liveries, airports, scenery enhancements, ATC enhancement packs, and camera mods. Its default location depends on whether you installed MSFS from the Microsoft Store/Xbox Game Pass (UWP version) or Steam.

  • Steam version: %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community
  • Microsoft Store / Game Pass version: %APPDATA%\Microsoft Flight Simulator\Packages\Community

If you changed your community folder to another drive (many users do), simply find that location by opening MSFS → General Options → Data → “Community folder location”. That path is what you must back up.

The Official Folder (Less Critical, Still Useful)

The Official folder holds base sim files, Asobo/Marketplace purchased content, and world updates. Its default location is within the same parent Packages folder as the Community folder. Because official content can always be re-downloaded from the marketplace, you can skip this folder — but backing it up can save a massive download if your internet is slow or if a world update becomes temporarily unavailable.

Roaming Settings and Key Bindings

The files stored under %APPDATA%\Microsoft Flight Simulator contain your entire configuration: graphics quality presets, control axis calibrations, custom keyboard/mouse/joystick bindings, camera snap views, and online-linked data. These files include:

  • UserCfg.opt – paths and general preferences.
  • Rolling Cache – a dynamic cache file (often very large, avoid backing up).
  • All .flt files – saved flight states (optional).
  • All Customization.json or settings XML files.

You must also back up any controller configuration saved in the InputProfiles subfolder (if present). Without those, every axis curve and button assignment would need to be re-calibrated from scratch.

Marketplace Licenses and Cache

Marketplace purchases are tied to your Xbox/Microsoft account. A full reinstall will re-download your purchased items automatically — but the cached local copies (inside a hidden folder under your main MSFS install) can be backed up to avoid a long re-download if you are restoring to the same machine.

The Best Manual Backup Method (Step-by-Step)

Even the most complex automation systems started with the manual method. This is the simplest, most reliable way to guarantee you have a complete copy of your personal MSFS universe.

Step 1: Shut Down MSFS Completely

Always close MSFS before touching any backup or restore operation. If the simulator is running, files may be locked or in an inconsistent state, causing corruption.

Step 2: Backup the Community Folder

Navigate to your Community folder path (as described above). Right-click the folder → Copy. Then go to an external drive, a network location, or a second internal hard drive. Right-click → Paste. That is your baseline add-on backup. For versioning, rename the folder with the date: Community_Backup_2025-01-15.

Step 3: Backup the Roaming Configuration Folder

Go to %APPDATA%\Microsoft Flight Simulator. Copy the entire folder (excluding the Rolling Cache if you want to save space). Paste to your backup destination. Do not skip the InputProfiles subfolder.

Step 4: Backup the UserCfg.opt File (Optional but Smart)

This small file defines your community folder path, rolling cache settings, and other foundational preferences. Copy it from the same Roaming folder and keep it alongside your main backup.

Automating Backups with Scripts and Schedulers

Repeating the manual copy every week is tedious. A simple batch script or PowerShell command can run on a scheduled task. Below is a robust PowerShell script that copies both the Community folder and the Roaming settings, with a date-stamped folder name.

$backupRoot = "D:\MSFS_Backups"
$date = Get-Date -Format "yyyy-MM-dd"
$communitySrc = "$env:LOCALAPPDATA\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community"
$roamingSrc = "$env:APPDATA\Microsoft Flight Simulator"
$dest = Join-Path $backupRoot $date

New-Item -ItemType Directory -Path $dest -Force
Copy-Item -Path $communitySrc -Destination $dest -Recurse -Force
Copy-Item -Path $roamingSrc -Destination $dest -Recurse -Force -Exclude "RollingCache*"
Write-Host "Backup completed to $dest"

Schedule this script via Windows Task Scheduler to run weekly (e.g., every Monday at 3:00 AM). Always ensure MSFS is closed — add a command within the script to check for the FlightSimulator.exe process and exit if running.

Using the MSFS Addons Linker (or Similar Organizers)

Many serious simmers use utility tools like MSFS Addons Linker or FlightPanel to manage their community folder. These tools create symbolic links or junctions to a separate organized library. If you use one, backing up your add-ons changes slightly: you now need to back up the source library folder (where the actual add-on files reside), not the community folder itself. The community folder becomes just a collection of symlinks that can be recreated quickly. The advantage is huge: you can selectively enable/disable add-ons without moving files, and the backup process is more straightforward because all your content is in one tidy location.

When using Addons Linker, back up the library storage folder (often called MSFS_Addons or something similar) plus the linker’s configuration database (usually a .json or .xml file in the same storage folder). Restoring is simply a matter of copying back the library and re-running the linker to rebuild the links.

Cloud Sync Backup Strategy (OneDrive, Google Drive, Dropbox)

If you are comfortable with continuous sync, you can place your Community folder inside a cloud folder. Be careful: MSFS regularly reads and writes to the Community folder during flights (especially for scenery caching). Running a sync client simultaneously can cause file locks or incomplete uploads. It is safer to use a scheduled sync with a tool like rclone or FreeFileSync that runs only when MSFS is closed. Alternatively, configure your cloud provider to sync only one direction (local to cloud) during non-simulation hours.

Do not sync the Rolling Cache or huge Official folders to the cloud — that would waste bandwidth and storage. Stick to the Community folder and the Roaming settings.

Restoring Your MSFS Backup: Each Method Covered

A backup is worthless if you cannot restore it painlessly. Below are step-by-step restoration instructions for each backup method described above.

Restoring from a Manual Copy

  1. Close MSFS completely.
  2. Delete or rename the existing Community folder (keep a copy until you confirm the restore works).
  3. Copy your backup Community folder to the original path.
  4. Delete or rename the Microsoft Flight Simulator folder inside %APPDATA%.
  5. Copy your backup of that folder to the same location.
  6. Launch MSFS. It will rebuild any necessary cache files. Your key bindings and graphics settings should appear exactly as before.

Restoring from a Scripted Backup

If you used the date-stamped script, navigate to the latest backup folder. Copy the Community and Microsoft Flight Simulator subfolders to their respective locations (overwrite). The same closure and rename precautions apply.

Restoring After a Clean Windows Install

This is the ultimate stress test. After re-installing Windows and MSFS, do not run the simulator yet. Instead:

  1. Copy your backed-up Microsoft Flight Simulator roaming folder to %APPDATA%.
  2. Copy your backed-up Community folder to the appropriate path (you may need to launch MSFS once to create the folder structure, then close it, then paste).
  3. If you also backed up the Official folder, place that in the correct Packages folder to avoid re-downloading world updates.
  4. Launch MSFS. It should recognize your previous config paths and add-ons immediately.

Replace the symlink source folder (your library) with your backup copy. Then launch the Addons Linker tool — it will see the same library content and recreate all symlinks. If you also backed up the linker’s database file, restore that to the same location. The community folder will then point to the same add-ons as before.

How to Handle Large Add-Ons and Frequent Updates

Not all add-ons are created equal. Marketplaces add-ons are re-downloadable, so you may choose to exclude them from your backup to save space. Freeware airport packs can be many gigabytes each. A single backup of a 200 GB Community folder is doable, but incremental backups are much smarter. Use a tool like Duplicati or Restic that supports deduplication and incremental backups. They will only copy changed files after the initial full backup, drastically reducing time and storage.

For SSD health, avoid frequent writes of huge files to the same physical drive. Back up to a different internal drive, an external USB SSD, or a NAS.

Common Pitfalls and How to Avoid Them

Pitfall 1: Copying the Rolling Cache

The Rolling Cache is a good chunk of your drive and is recreated automatically. Never include it in your backup — it wastes space and time.

Pitfall 2: Restoring While MSFS Is Running

This corrupts the restored files instantly. Always confirm the process FlightSimulator.exe is not active.

Pitfall 3: Forgetting Controller Profiles

Your joystick, yoke, or rudder pedal calibrations live in the InputProfiles subfolder. If you only back up the main Community folder, those are lost. Always include the entire %APPDATA%\Microsoft Flight Simulator folder (excluding Rolling Cache).

Pitfall 4: Relying Solely on Steam Cloud

Steam Cloud for MSFS is minimal — it only saves a few config entries, not your Community folder or add-on installations. It is not a substitute for a proper backup.

Advanced Strategy: Versioned Backups with Windows File History

If you prefer not to use scripts or third-party tools, enable Windows File History. Configure it to back up your Community folder and your Roaming folder every hour (or daily). Then you can restore any previous version of a single file or folder right from the File Explorer context menu. This is simple, visual, and does not require any command line knowledge.

Similarly, macOS Time Machine works beautifully for those running MSFS via Boot Camp or Parallels — just set it to include the Windows partition’s relevant folders.

When a Backup Goes Wrong: Recovery Tips

Even with perfect backups, you may encounter issues. If after a restore your add-ons do not appear:

  • Check that the UserCfg.opt file points to the correct Community folder path. If you changed drives, update the path manually in a text editor.
  • Verify that your InputProfiles files are in the correct subfolder. A missing .xml means you will see “no controllers” upon launch.
  • If MSFS crashes on startup after restoring, delete the Rolling Cache folder (it will be rebuilt).
  • For market purchases that refuse to redownload, go to the in-game marketplace → “My Library” → “Repair/Reinstall”.

Conclusion: Build a Backup Habit That Sticks

Your MSFS setup is a living piece of digital aviation history. Protect it with the same rigor you would use for your real-world flight planning. The best method is the one you will actually do — whether that is a weekly scheduled script, a cloud sync, or a simple manual copy before every major update. Combine at least two methods (e.g., a scheduled local backup and an occasional cloud copy) to guard against hardware failure, user error, and update incompatibility.

For additional real-time advice and community supported backup solutions, bookmark these resources:

Rest easy knowing your perfect approach plate, third-life battery, and custom 737 livery will be there when you open the hangar tomorrow.