Learn how MSFS 2024 World Hub works, how to claim, edit and submit an airport, and why an accepted change may not appear immediately.
Microsoft Flight Simulator 2024 (MSFS 2024) World Hub is Microsoft's community airport-improvement system. It lets signed-in contributors claim an eligible default airport, edit it with the built-in Scenery Editor and submit corrections for moderation. Accepted work is folded into a later simulator update, not installed immediately as personal scenery.
What does MSFS 2024 World Hub change?
World Hub corrects default airport data so that approved improvements can benefit everyone using that airport in MSFS 2024. Typical contributions address:
- Runway position, dimensions, surface, markings and lighting.
- Taxiway geometry, names, signs, centre lines and hold-short points.
- Parking stands, gates, ramp starts and connected taxi paths.
- Aprons, windsocks, fences and permitted stock-library buildings or objects.
Its scope is the airport itself. Regional terrain, photogrammetry, elevation data and points of interest belong to World Updates, which have a separate installation and content-management process. Navigation procedures, radio aids and data supplied by the simulator's navigation database may also sit outside what an airport scenery edit can change.
World Hub is primarily a PC contributor workflow because it relies on Developer Mode and the scenery-development toolchain. Xbox Series X|S and PlayStation 5 users receive published corrections through simulator updates but do not create World Hub projects on their consoles.
How do you use World Hub in MSFS 2024?
- Update and sign in: Use an online, updated PC installation and sign in with the Microsoft account used by the simulator. World Hub access can be staged or temporarily unavailable during service maintenance.
- Enable Developer Mode: Turn on Developer Mode in the simulator's developer or advanced settings. Allow any matching developer-tool component that MSFS requests.
- Open World Hub: Select the World Hub command from the developer tools, then search for the airport by identifier or name. Its status will show whether it can be edited, is protected, has already been reserved or is under review.
- Reserve the airport: Claim or reserve the eligible airport using the wording presented by the Hub. Start with the World Hub copy rather than creating an unrelated scenery package; the Hub needs its project structure and airport identity intact.
- Inspect before editing: Load the airport and compare the existing layout with reliable reference material that you are permitted to use. Record what actually needs correction instead of rebuilding working sections unnecessarily.
- Edit with the supplied tools: Use the Scenery Editor for airport objects and the supporting project tools for validation and building. Our explanation of how the airport scenery tools fit together covers the roles of the Scenery Editor, Project Editor and Package Builder.
- Validate and test: Clear every relevant validation error, then test taxi routes, runway starts, parking positions, AI movement, ATC routing and lighting. Disable any separate add-on that replaces the same airport while testing. For terrain, snapping, altitude and exclusion problems, use our practical MSFS 2024 editor settings guidance.
- Submit for moderation: Add a concise change description and any requested supporting information, then submit through World Hub. A moderator may approve it, reject it with a reason or return it for revision.
Submission does not update the public simulator immediately. The correction must pass moderation and then be included in a later content or simulator update; there is no guaranteed publication date.
Should you use World Hub or make a normal scenery add-on?
Use World Hub for factual corrections to an eligible default airport when the work can be built entirely with assets and features permitted by the Hub. Choose a normal add-on when you need custom models, textures, scripts, dependencies or control over your own release schedule.
| Choose World Hub when... | Choose normal scenery when... |
|---|---|
| The default runway, taxiway or parking layout is wrong. | You need bespoke terminals, hangars or ground textures. |
| The correction should become part of the shared base airport. | You want a private package or independently distributed release. |
| The work uses objects authorised by World Hub. | The airport depends on imported assets or another package. |
A normal package also makes more sense for extensive artistic redevelopment rather than a correction. The broader custom scenery creation workflow explains how to build and test that type of project outside World Hub.
Why is an airport unavailable or a submission rejected?
An unavailable airport is usually protected, already reserved, undergoing moderation or outside the Hub's eligible dataset. Handcrafted and third-party airports may be locked because a community edit could conflict with the package that supplies them.
Common submission failures include:
- Disconnected taxi paths, invalid runway starts or parking links that prevent AI and ATC routing.
- Overlapping or duplicate airport elements left behind after moving a runway or apron.
- Missing project metadata or unresolved errors in the validator.
- Custom models, textures or dependencies that World Hub cannot distribute safely to every user.
- Changes based on inaccurate, outdated or unlicensed reference material.
- A project that alters areas unrelated to the claimed airport.
Fix validator errors before cosmetic warnings, then retest from a clean simulator session without replacement scenery active. Do not delete a functional taxi network merely to silence an error; repair its connections and airport references instead.
How do accepted World Hub airports appear in the simulator?
Accepted World Hub changes arrive through a later MSFS 2024 update and normally require no individual airport download. The published airport then becomes part of the simulator's shared default scenery.
If the airport still looks unchanged after its correction has been released, check that the simulator has received the relevant update and restart it. A Community-folder package or installed third-party airport covering the same location can override the updated default airport, so disable that replacement before judging whether the World Hub version is present.