Learn how to extract ZIP files for flight simulator add-ons, identify the correct package folder, and fix nested-folder or corrupt-archive errors.
To extract a ZIP add-on for Microsoft Flight Simulator, X-Plane, FSX or Prepar3D, save it to a temporary folder, right-click the ZIP and choose Extract All on Windows, or double-click it on macOS. Read the included instructions, identify the actual package root, then install its contents in the simulator's correct add-on location.
How do I extract a flight simulator ZIP file?
- Create a temporary staging folder. Keep it outside the simulator's installation and add-on folders. This lets you inspect the archive before anything is copied into the live simulator.
- Extract the complete archive. In Windows, right-click the ZIP, select Extract All, choose your staging folder and start extraction. In macOS Finder, double-click the ZIP; the extracted folder normally appears beside it.
- Wait for extraction to finish. Do not run an installer or drag selected files from the compressed-folder view. Extracting everything preserves the directory structure and avoids omitted gauges, textures, effects or documentation.
- Open the extracted folder. Look for a readme, installation document or manual before moving files. Its instructions take precedence because some packages use an installer while others require folders to be copied manually.
- Find the package root. ZIP files commonly contain an extra outer folder named after the download or version. The usable add-on may be one level farther down.
- Install the package in the correct location. Copy the package folder or its specified contents, not the original ZIP, unless an add-on manager explicitly tells you to import the unopened archive.
Which extracted folder should I copy?
The correct folder is normally the lowest folder containing the add-on's defining files, not necessarily the first folder created during extraction.
| Simulator or package type | What identifies the package root |
|---|---|
| Microsoft Flight Simulator 2020 or 2024 | A manual Community package normally has manifest.json and layout.json directly inside its root. Copy the folder enclosing those files, rather than an extra wrapper above it. |
| X-Plane aircraft | The aircraft's main folder contains at least one .acf file, usually alongside its objects, liveries and other supporting folders. Keep that structure intact. |
| FSX, Prepar3D or FS2004 aircraft | The aircraft folder normally contains aircraft.cfg and folders such as model, panel, sound and texture. An archive containing top-level Effects, Gauges or SimObjects folders is a multi-location package, so follow its instructions rather than copying the wrapper as one aircraft. |
| Installer-based add-on | The extracted files include an installer and documentation. Run it from the extracted staging folder only if the download is trusted; do not place the installer folder inside the simulator. |
For example, if the path is AircraftName-v2/AircraftName/manifest.json, the inner AircraftName folder is the Microsoft Flight Simulator package. Copying the outer folder creates an extra directory level, so the simulator may not detect it.
Folder destinations differ by simulator. Our X-Plane 11 and 12 extraction and installation steps explain the aircraft, scenery and plugin locations, while our manual FSX aircraft installation workflow covers aircraft folders and separate support files.
Why does the ZIP fail to extract?
An extraction error usually means the download is incomplete, the archive uses another format, or the destination cannot accept the files.
- Invalid archive, CRC error or unexpected end: delete the failed copy and download it again. These messages commonly indicate a truncated or damaged file.
- Password requested: use only the password supplied with the download. A password prompt does not necessarily mean the archive is corrupt.
- No Extract All option: check the extension. A
.raror.7zfile is not a ZIP and must be opened with an archive utility that supports that format. Renaming its extension does not convert it. - Access denied or path too long: extract to a short, writable location under your user folders rather than directly into a protected simulator directory.
- Not enough space: the extracted add-on can be considerably larger than the compressed download, so both the staging drive and simulator drive need free capacity.
- Security software blocks a file: do not disable protection automatically. Confirm that the archive came from a trusted source and check which file was flagged before proceeding.
Why is the add-on missing after extraction?
Extraction alone does not install an add-on, and the most common installation fault is an extra nested folder between the simulator and the package root.
- Confirm that you copied the extracted package rather than the ZIP.
- Remove unnecessary wrapper folders above
manifest.json,layout.json,.acforaircraft.cfg. - Do not flatten the package by moving all files into one directory; relative paths must remain intact.
- Check that the package was installed for the correct simulator and version.
- If the first extraction produces another obvious archive, read the documentation before extracting it. Do not recursively unpack every ZIP stored inside an add-on because some are intentional resources.
If an aircraft still fails to appear, work through our package-root and aircraft visibility checks.
Can I install an add-on without extracting the ZIP?
Most desktop flight simulators do not load add-ons directly from ZIP files. Extract the archive first unless the add-on's installer or manager specifically provides an Import ZIP function; in that case, leave the archive intact and import it through that tool.
Can I delete the ZIP after installation?
Yes, once the add-on loads correctly and you have confirmed that no installer needs the archive again. Keeping the original ZIP is useful for reinstalling or identifying files placed in several simulator folders, but the archive itself is not required during normal simulator use.