See the must-have plugins for X-Plane 12, with clear picks for charts, pushback, cameras and checklists, plus compatibility fixes.
No third-party plugin is required to enjoy X-Plane 12, but our practical core set is AviTab, BetterPushback, X-Camera and XChecklist. Add FlyWithLua NG only when a trusted script requires it. Traffic, online-network and aircraft-specific plugins are optional, not universal essentials, and should be installed according to how you fly.
The essential X-Plane 12 plugin shortlist
These five plugins cover the functions most pilots miss without adding several overlapping systems.
| Plugin | Best for | Why install it | Main caveat |
|---|---|---|---|
| AviTab | Charts, documents and maps | Provides an in-simulator tablet window and integrates with supported aircraft cockpits. | It does not automatically provide a complete set of current navigation charts; pilots may need to supply their own files or services. |
| BetterPushback | Airliner pushback | Lets you plan the tug route and control a more convincing pushback operation. | Install a build explicitly compatible with X-Plane 12. An old X-Plane 11 package may not work correctly. |
| X-Camera | Saved cockpit and external views | Makes organised camera profiles, transitions and aircraft-specific viewpoints easier to manage. | X-Plane's native views may already be sufficient, especially for simple general-aviation flying. |
| XChecklist | Interactive checklists | Displays checklists and can recognise completed actions when the aircraft includes a compatible clist.txt file. | Its usefulness depends on the quality of the checklist supplied for each aircraft. |
| FlyWithLua NG | Lua scripts and small utilities | Runs compatible scripts that adjust controls, interfaces or simulator behaviour. | It is a scripting framework, not an enhancement by itself. Install it only when you have a specific script to run. |
Our broader selection of useful free X-Plane 12 utilities covers alternatives such as camera effects and additional cockpit tools.
Which X-Plane 12 plugins suit your flying?
The right selection depends on the aircraft and type of operation rather than the length of a recommended-plugin list.
- Airliner flying: Start with AviTab and BetterPushback, then add X-Camera or XChecklist if the aircraft does not already provide equivalent features.
- General aviation and IFR practice: AviTab and XChecklist are usually the most useful. The built-in G1000 and standard avionics do not require a plugin.
- VR: Keep the set small and verify that every window or camera utility works comfortably in VR before adding another.
- Traffic: Install one traffic system, not several competing injectors. LiveTraffic emphasises live movements, Traffic Global favours straightforward generated traffic, while WorldTraffic 3 offers more configuration. Our traffic-plugin comparison explains which approach fits each pilot.
- Online network flying: Use the client required by the chosen network. It is essential for that service but unnecessary for offline flying.
- Scripting and cockpit hardware: Add FlyWithLua NG only for a known script. Scripts that manipulate private art controls or outdated datarefs can stop working after simulator updates; our guide to X-Plane datarefs and plugin interaction explains the distinction.
Scenery libraries, orthophoto tools and aircraft installers are often described as plugins even though they belong elsewhere. Do not put everything into Resources/plugins; use the folder specified by the add-on's documentation.
How do I install X-Plane 12 plugins safely?
Install each plugin in its own folder under X-Plane 12/Resources/plugins, then start the simulator and verify it before adding another.
- Confirm compatibility: Check that the package supports X-Plane 12, your operating system and your processor architecture. On Apple Silicon, a plugin needs a compatible native binary unless X-Plane is deliberately run through the relevant compatibility layer.
- Extract the archive: Do not run a plugin from inside its ZIP file.
- Check the folder depth: The plugin's files must not sit inside an unnecessary second copy of the same folder. Excess nesting is one of the failures we see most often.
- Copy it to the plugin directory: Place the complete plugin folder in
Resources/plugins. FlyWithLua scripts normally go in that plugin's ownScriptsfolder instead. - Restart X-Plane: A full restart is more reliable than trying to reload a newly installed plugin during a flight.
- Inspect the result: Look for its entry or menu inside X-Plane and check
Log.txtin the simulator's main folder if it is absent.
For screenshots of the expected directory structure and more detailed diagnostics, follow our X-Plane 12 mod and plugin installation procedure.
Why is an X-Plane 12 plugin not loading?
A plugin usually fails because it is in the wrong folder, was compiled for another platform or architecture, depends on missing software, or is an outdated X-Plane 11 release.
- Nothing appears in the Plugins menu: Open
Log.txtand search for the plugin's name, loading errors or missing libraries. - The plugin worked before an update: Remove it temporarily, test X-Plane cleanly, then obtain an explicitly compatible plugin release.
- FlyWithLua quarantines or stops a script: Treat the script as the likely fault rather than repeatedly reinstalling FlyWithLua. Test scripts individually.
- X-Plane crashes during start-up: Move recently added plugin folders outside
Resources/pluginsand return them one at a time until the culprit is identified. - Two plugins control the same feature: Disable one. Multiple camera-motion tools, weather controllers or traffic injectors can issue competing instructions even when each works alone.
- macOS blocks the binary: Review the operating system's security message and use a trusted, compatible package rather than indiscriminately bypassing protection.
Do X-Plane 12 plugins reduce frame rate?
Plugins can reduce performance, but their workload matters more than the number of folders installed.
Traffic injection, moving maps, weather processing and scripts that run calculations every frame can consume CPU time. Measure performance in the same aircraft, airport, weather and view, then disable suspected plugins one at a time. Leaving unused plugins installed but inactive is less useful than maintaining a small, known-good set.
For most pilots, AviTab, BetterPushback and one checklist or camera tool form a sensible baseline. Add traffic, scripting and aircraft-specific utilities only when they solve a clear problem.