How do I convert MSFS 2020 liveries to MSFS 2024?

Many MSFS 2020 liveries can be tested unchanged in Microsoft Flight Simulator 2024. When package references or metadata need migration, the Liveries.to MSFS 2024 Livery Converter can update compatible packages, but it cannot make old textures fit an aircraft whose 3D model, UV map or material layout has changed.

Do MSFS 2020 liveries work in MSFS 2024?

Yes, many MSFS 2020 liveries work in MSFS 2024 when the simulator is loading the same underlying aircraft model with compatible geometry, UV mapping, materials and package references. If the original package appears in the aircraft selector and looks correct in flight, conversion offers no practical benefit.

A livery is aircraft-model-specific, not aircraft-name-specific. A repaint made for one developer's A320, 737 or Cessna 172 will not automatically fit another developer's implementation of the same aircraft. The mistake we see repeatedly is matching the visible aircraft name while overlooking the developer, package, model and variant.

• Unchanged or backward-compatible aircraft: test the original livery first. A package correction or converter pass may be enough if it does not appear.
• Replaced or substantially revised aircraft: expect to use a native MSFS 2024 paint kit and rework the textures.
• Separately developed aircraft with the same real-world name: treat it as a different aircraft. The old livery normally needs to be recreated.

Our detailed breakdown of cross-version livery compatibility explains how aircraft and texture differences affect the result.

How to use the Liveries.to MSFS 2024 Livery Converter

The Liveries.to converter is the sensible next step when the underlying aircraft remains compatible but the MSFS 2020 package needs updated references, structure or metadata. Use a separate output location so the source is never overwritten.

1. Back up the original livery. Keep an untouched copy outside every Community folder. If you have not already done so, test that original in MSFS 2024; stop if it loads and looks correct.
2. Verify the exact base aircraft. Install the MSFS 2024-compatible version of the aircraft, including the correct developer and variant. A similarly named default or third-party aircraft is not an adequate substitute.
3. Select the source and a new output location. Choose the MSFS 2020 livery package as the converter source. Send the result to a new, empty folder outside the active Community directory rather than writing over the original.
4. Run the conversion. Allow the tool to migrate the package information and supported aircraft references. Do not add, rename or delete textures while it is generating the output.
5. Inspect the generated package. Its package root should contain files such as manifest.json and layout.json, rather than hiding them inside multiple unnecessary folders.
6. Install only the generated package. Place the converter output in the active MSFS 2024 Community folder. Temporarily keep the source package out of that folder because two copies can create identifier and load-order conflicts. Follow our MSFS livery installation and Community-folder checks if you are unsure which folder is active.
7. Test before discarding anything. Restart the simulator, select the exact base aircraft and inspect the livery in the aircraft selector and in flight. Do not delete or overwrite the original backup until the generated package has passed these checks.

Converting a package for personal testing does not grant permission to redistribute somebody else's artwork. Retain the original author's licence and obtain permission before publishing a modified version.

What can an MSFS 2024 livery converter change?

A livery converter can update supported package structure, metadata, generated file lists and compatible aircraft references. It is a package-migration tool, not an automatic repainting system.

If the aircraft uses a new model or paint template, use a manual repaint. If the required files are protected or no supported paint kit exists, contact the aircraft developer rather than trying to bypass the package protection.

Which conversion method should I use?

Choose the least invasive method that solves the actual fault; rebuilding a working livery creates extra opportunities for conflicts.

How do I manually convert a livery with the MSFS 2024 SDK?

An SDK rebuild is warranted when the converter cannot support the source package, references must be corrected manually, or the artwork needs a native MSFS 2024 texture layout. It is unnecessary when the original package already works or the converter produces a clean, visually correct result.

1. Confirm the target aircraft. Record its developer, package, model and variation. Do not build against a similarly named aircraft.
2. Obtain the proper paint kit and permission. Layered source artwork is preferable to editing compressed texture files. Check the original author's redistribution terms.
3. Set up the matching SDK. Use the SDK and livery template intended for your installed MSFS 2024 build. Our SDK installation and project set-up guide covers the required starting workflow.
4. Create a clean livery project. Give it unique package and variation identifiers so it cannot overwrite the 2020 package or another repaint. Never edit the simulator's Official or streamed package areas.
5. Transfer or remap the artwork. If the UV map is unchanged, much of the paint may align. Otherwise, reposition every marking against the MSFS 2024 template, including seams, doors, wings, nacelles and control surfaces.
6. Match the material setup. Export the texture names, formats, paths, alpha data and material channels required by the target aircraft. Blindly renaming old textures can cause black, white, transparent or incorrectly reflective surfaces.
7. Replace legacy references. Point the project at the exact MSFS 2024 base aircraft and remove fallbacks or dependencies tied only to the 2020 implementation.
8. Build and test a fresh package. Let the SDK regenerate the package metadata and file list. Test the livery by itself and inspect exterior surfaces, cockpit-visible areas, landing gear, engines, control surfaces, different model variants and distant levels of detail.

Why does the converted livery not appear in MSFS 2024?

A missing livery normally indicates a converter-output, installation or dependency failure rather than bad painted artwork. Check these causes before changing any textures:

• Wrong Community-folder root: the generated package was copied to an inactive Community folder, or the folder containing manifest.json and layout.json is buried beneath extra directory levels.
• Duplicate package or variation IDs: the original and converted versions are both active, or the output shares an identifier with another livery. Remove the duplicate and rebuild with unique identifiers where necessary.
• Stale or incomplete generated metadata: files were added, renamed or deleted after conversion. Run the converter again into an empty output folder rather than merging new output with an older conversion.
• Missing dependency: the livery targets a separate aircraft, edition or add-on variant that is not installed. Install the exact compatible base package.
• Unsupported or protected source: the converter could not read or migrate all required package information. Use the developer's supported template or perform an authorised SDK rebuild.

If the livery appears in the selector but selecting it loads another paint, inspect its aircraft and variation references. If it never appears at all, concentrate on the package root, metadata, identifiers and dependency before considering a repaint.

Why is the converted paint distorted or partly missing?

Artwork that is stretched, mirrored, displaced or wrapped around the wrong part of the aircraft indicates incompatible geometry or UV mapping. A converter cannot calculate where every marking belongs on a different model.

• Logos cross the wrong seams: remap them on the MSFS 2024 fuselage template.
• Wings, doors or engines remain unpainted: those parts may use different texture sheets or material assignments.
• Surfaces have incorrect gloss, transparency or metallic appearance: rebuild the required material-channel textures rather than editing only the colour layer.
• The problem changes with viewing distance: inspect the aircraft's lower-detail models and any separate texture assignments they use.

These faults require a compatible MSFS 2024 paint kit and texture rework. Our aircraft repainting guide explains how to preserve UV layouts, material channels and export requirements.

Can I convert a livery by changing the aircraft name?

No, not unless both aircraft use the same model, UV map, material layout and compatible internal references. Changing a displayed title, folder name or aircraft reference cannot turn a repaint for one developer's model into a repaint for another.

Where the underlying aircraft is genuinely compatible, the Liveries.to converter may update supported references safely. Where the model differs, start from the correct paint kit and treat the work as a new livery.

Can converted liveries be installed on Xbox or PlayStation?

Locally converted Community packages are a PC workflow. Xbox Series X|S, PlayStation 5 and PS5 Pro do not expose a PC-style Community folder for arbitrary livery packages, so console distribution must use an approved in-simulator channel and meet its packaging and licensing rules.