Install FlyByWire A32NX and A380X liveries in MSFS correctly, choose the right Community folder, and fix missing or incompatible repaints.
To install FlyByWire A32NX or A380X liveries in Microsoft Flight Simulator, install the matching base aircraft first, extract the downloaded archive, and place the livery’s package folder in the active Community folder. Restart MSFS, select the correct FlyByWire aircraft, and choose the repaint from its available liveries.
What do A32NX and A380X liveries require?
Each repaint requires the exact FlyByWire base aircraft it was built for. A livery download normally contains only replacement paint textures and configuration files; it is not a flyable aircraft by itself.
| Livery package | Required aircraft | Not interchangeable with |
|---|---|---|
| A32NX livery | FlyByWire A32NX | The default A320neo, A320neo V2 or another developer’s Airbus |
| A380X livery | FlyByWire A380X | Any other A380 model or an A32NX package |
Install and load the base aircraft successfully before adding repaints. Our FlyByWire A32NX base-aircraft download page covers the required aircraft and package structure. For the larger Airbus, our explanation of the FlyByWire A380X and its required base model helps distinguish the aircraft from livery-only downloads.
How do I install an A32NX or A380X livery package?
For a normal archive-based livery, installation means copying one self-contained package into the Community folder rather than altering FlyByWire’s aircraft files.
- Check the aircraft and simulator compatibility. Confirm that the download names the FlyByWire A32NX or A380X and supports the edition of Microsoft Flight Simulator you use. A repaint for another A320 or A380 will not become compatible by renaming its folder.
- Extract the downloaded archive. Unpack the ZIP, RAR or 7z file first. MSFS cannot load a livery that remains inside its compressed archive.
- Find the actual package folder. Its root normally contains
manifest.jsonandlayout.json, usually alongside aSimObjectsfolder. If those files sit inside a second folder, copy that inner folder rather than the outer download wrapper. - Copy the package into Community. Keep it separate from the FlyByWire aircraft package. Do not paste textures into the base aircraft’s folders, because an aircraft update may overwrite them and a malformed edit can stop the aircraft loading.
- Restart Microsoft Flight Simulator. Select the FlyByWire A32NX or A380X in the aircraft selection screen, then choose the repaint from that aircraft’s available liveries. The repaint should not appear as a completely separate aircraft type.
For more detail on archive extraction and identifying a valid package root, see our Community-folder livery installation instructions.
Which Community folder should I use in MSFS 2020 or 2024?
MSFS 2020 and MSFS 2024 can use different Community folders, so the repaint must go into the folder read by the version you actually launch. This is a common problem when both simulators are installed or when the Packages location has been moved to another drive.
Do not assume a path copied from another PC is correct. Store edition, installation choices and a custom Packages location can all change it. Also keep MSFS 2020 and MSFS 2024 copies separate unless the livery documentation explicitly confirms compatibility with both.
Manual Community-folder installation applies to PC. Xbox Series X|S and PlayStation 5 do not allow users to sideload these PC livery archives into the simulator’s file system.
Why is my FlyByWire livery not showing?
A missing FlyByWire repaint is usually caused by the wrong aircraft variant, an extra nested folder or installation into an inactive Community folder.
- Verify the base model: select the FlyByWire aircraft, not a similarly named default or third-party Airbus.
- Inspect the folder depth: opening the installed livery folder should reveal
manifest.jsonandlayout.json, not another identically named package folder. - Check the simulator edition: a package placed in the MSFS 2020 Community folder will not automatically appear in MSFS 2024, or vice versa.
- Remove duplicate repaint versions: two old copies of the same livery can conflict. Retain one complete, up-to-date package without removing the FlyByWire base aircraft.
- Confirm build compatibility: older liveries can break after aircraft model or configuration changes. Use a package explicitly made for the relevant A32NX or A380X version rather than editing its manifest to force recognition.
If those checks do not solve it, work through our full checklist for MSFS liveries that do not appear.