Set up FlyByWire remote EFB and web MCDU in MSFS using SimBridge, with local-network connection steps and fixes for blank or disconnected pages.
To use the FlyByWire remote EFB or web MCDU in Microsoft Flight Simulator, install and start SimBridge, load a supported FlyByWire aircraft, then open SimBridge’s web address in a browser. On another device, replace localhost with the PC’s local IPv4 address; both devices must be on the same network.
What you need before connecting
The remote interfaces require the Windows PC version of Microsoft Flight Simulator, a compatible FlyByWire aircraft and the separate SimBridge companion application. The phone, tablet or second computer only runs the browser interface; SimBridge remains on the simulator PC.
Install the aircraft and SimBridge through the FlyByWire Installer, keeping both updated together. MSFS 2024 users should complete the compatible A32NX installation process before configuring remote displays.
This workflow cannot be hosted by an Xbox or PlayStation installation because those platforms cannot run the Windows SimBridge application. A mobile device is suitable as the remote screen, but it cannot replace the simulator PC.
How do I connect the remote EFB or MCDU?
Start SimBridge, load the FlyByWire aircraft into a flight, and test the browser interface on the simulator PC before attempting a phone or tablet connection.
- Install SimBridge. Use the FlyByWire Installer rather than copying files manually. If Windows requests network permission, allow SimBridge on private networks.
- Start Microsoft Flight Simulator and SimBridge. SimBridge may run before or after the simulator, but it must remain open while the remote display is being used.
- Load the aircraft completely. Enter a flight with the supported FlyByWire aircraft and provide electrical power to the cockpit equipment. A cold-and-dark MCDU may correctly appear blank.
- Test the local connection. On the simulator PC, enter
in a browser. This is the standard SimBridge address unless its port has been changed. - Connect the remote device. On a phone, tablet or second computer, enter the simulator PC’s local IPv4 address followed by
:8380, for example. - Open the required interface. Select the EFB or MCDU offered by the SimBridge page. Inputs made in the browser are sent to the corresponding aircraft system.
Use http, not https. Some mobile browsers try to upgrade local addresses to HTTPS automatically, which can produce a connection or certificate error.
What address should I use on a phone or tablet?
A remote device must use the simulator PC’s private IPv4 address because localhost always means the device on which the browser is running.
On the PC, run ipconfig and find the IPv4 address under the active Wi-Fi or Ethernet adapter. Ignore addresses belonging to VPNs, virtual network adapters and disconnected interfaces. The phone or tablet must normally be connected to the same router and local network.
If the PC address changes after a router restart, update the saved browser address. Guest Wi-Fi and settings described as client or access-point isolation can also prevent devices from reaching each other, even when both show the same Wi-Fi name.
No internet port forwarding is required. We recommend keeping SimBridge accessible only on the local network rather than exposing its web port to the internet.
What is the difference between the remote EFB and web MCDU?
The remote EFB presents the aircraft’s flyPad functions in a browser, while the web MCDU reproduces the flight-management control and display unit.
| Interface | Best used for | How it behaves |
|---|---|---|
| Remote EFB | Fuel, payload, performance, checklists and ground services | Acts as a browser client for the aircraft-specific flyPad and shares its aircraft state |
| Web MCDU | Route entry, flight-plan changes, radio pages and data entry | Mirrors the connected cockpit MCDU rather than creating an independent flight computer |
For the tablet’s operational pages, our flyPad fuel, payload and flight-planning walkthrough explains what each major function does. The FlyByWire flyPad is separate from the simulator-level tablet supplied with MSFS 2024; that system is covered in our guide to the built-in MSFS 2024 EFB.
The web MCDU uses the same aircraft data and electrical state as the cockpit unit. For MCDU-specific controls and connection details, see our dedicated remote MCDU setup and troubleshooting notes.
Why is the FlyByWire remote display not working?
The fastest diagnosis is to test localhost first: if that fails, the problem is on the simulator PC; if it works, the fault is usually the network address, firewall or router.
| Symptom | Likely cause and fix |
|---|---|
| The page does not open on the simulator PC | Confirm that SimBridge is running, restart it after an update and use the address or port shown by the application. Close any duplicate SimBridge instance. |
localhost works, but the phone cannot connect | Recheck the active adapter’s IPv4 address, allow SimBridge through the Windows firewall on private networks, disable a VPN temporarily and check for guest-network isolation. |
| The page opens but reports that the aircraft is disconnected | Wait until the flight has fully loaded, confirm that a supported FlyByWire aircraft is selected, and update both the aircraft and SimBridge through the same installer. |
| The MCDU or EFB is black | Supply the aircraft with electrical power, switch on the relevant unit and check its brightness. A web connection does not bypass the aircraft’s power state. |
| The interface is stale or controls are misaligned | Reload the page, clear its cached site data if necessary, return browser zoom to 100% and restart SimBridge after changing aircraft versions. |
| A saved address suddenly stops working | The router may have assigned the PC a new IPv4 address. Run ipconfig again and replace the old address in the browser bookmark. |