Set up X-Plane 12 for streaming with the right capture source, hardware encoder, resolution and audio, plus fixes for black screens and stutter.
To set up X-Plane 12 for streaming, create a dedicated scene in your broadcasting software, capture the simulator window or display, select a hardware video encoder, match output resolution and frame rate to available performance, add simulator and microphone audio, then make a local test recording before going live.
How do I connect X-Plane 12 to streaming software?
The safest method is to establish a basic capture at low load, verify it, and then increase quality one setting at a time.
- Prepare a representative flight. Load the aircraft, airport, weather and add-ons you expect to stream. A quiet default-aircraft test can hide performance problems that appear at a detailed hub in rain.
- Choose a stable display mode. A maximised X-Plane window makes switching between applications easier. Full-screen is also usable if the capture source remains visible after switching away. Keep the X-Plane resolution unchanged once the scene has been framed.
- Create a dedicated scene. Add X-Plane as the bottom source, followed by any camera, chat or information overlays. Lock the sources after positioning them so an accidental drag does not ruin the layout.
- Connect the streaming destination. Sign in through the broadcasting app or enter the service address and private stream key it supplies. Never display that key on screen or save it in a scene containing visible account details.
- Select a hardware encoder. Hardware H.264 is the broadly compatible choice unless the streaming service explicitly supports another codec. Encoder names may refer to NVIDIA, AMD, Intel Quick Sync or Apple VideoToolbox, depending on the computer.
- Set the output format. Start with 1920×1080 at 30 frames per second, constant bitrate and the keyframe interval required by the streaming service. Use its published bitrate range rather than copying settings intended for another platform.
- Add audio separately. Capture X-Plane or system sound once, then add the microphone as its own source. Confirm that both meters move before testing.
- Record a complete test. Include cockpit movement, external views, loud engine phases, radio audio and application switching. Watch the recording at full screen; the small preview can conceal blurred instruments and frame-pacing problems.
Which capture source should I use?
Game or application capture usually gives the cleanest result on Windows, while display capture is the most dependable fallback when X-Plane produces a black frame or uses separate panel windows.
| Capture source | Choose it when | Main limitation |
|---|---|---|
| Game or application capture | You want X-Plane only, without exposing the desktop | Can show a black frame if the capture API, graphics adapter or application privileges do not match |
| Window capture | X-Plane runs in a stable maximised window | Detached instruments, menus or plug-in windows may not be included |
| Display capture | You need the most reliable capture or must include pop-out panels | Notifications, other applications and private information can appear on stream |
On macOS, grant the broadcasting app screen-recording and microphone permissions, then restart it if the source remains blank. On a Linux Wayland session, display or window capture may depend on the system screen-sharing portal. Whatever the platform, confirm that moving the X-Plane window has not changed the captured area.
What resolution and frame rate should I stream?
For most X-Plane 12 flights, 1080p at 30 fps gives the best balance between readable instruments, bandwidth and simulator performance.
| Output | Best use | Trade-off |
|---|---|---|
| 1920×1080 at 30 fps | Airliner flying, instrument procedures and general streaming | Fast external pans are less fluid than 60 fps |
| 1920×1080 at 60 fps | Low-level flight and frequent camera movement on a system with substantial headroom | Requires more encoding capacity and bitrate; cockpit text may suffer if bitrate is constrained |
| 1280×720 at 30 fps | Limited upload bandwidth or a computer already close to its performance limit | Small avionics labels are harder to read |
| 1280×720 at 60 fps | Motion matters more than fine cockpit detail | Uses more bitrate than 720p30 without improving text resolution |
Do not select 60 fps simply because the monitor runs at 60 Hz. If X-Plane fluctuates between roughly 35 and 50 fps, a 60 fps broadcast will repeat frames unevenly and appear jerky; a stable 30 fps output usually looks better.
Set the canvas to the captured desktop or simulator resolution, then perform only one downscale at the output stage. Scaling the source inside the scene and scaling it again during encoding softens glass-cockpit text. Use constant bitrate for livestreaming, leave enough upload headroom for fluctuations, and use a wired network connection where practical.
How much performance headroom does streaming require?
X-Plane 12 and the broadcasting app need enough GPU and CPU headroom to render, composite and encode every frame on time.
Hardware encoding reduces CPU demand, but it does not make streaming free: the broadcasting app still uses GPU resources to compose and scale the scene. Avoid running X-Plane with the GPU pinned at full utilisation before opening the stream. Our guide to identifying X-Plane 12 CPU and GPU bottlenecks explains which settings to change for each type of limit.
- When GPU-limited: reduce rendering resolution, anti-aliasing, cloud quality or shadows. Lowering the stream from 60 to 30 fps also reduces composition and encoding work.
- When CPU-limited: reduce world-object density, rendering distance, traffic and demanding plug-ins. Dropping texture resolution will rarely solve a main-thread bottleneck.
- When VRAM-limited: lower texture quality, remove oversized scenery or aircraft textures, and close GPU-accelerated applications. Our explanation of reducing VRAM pressure and texture-related pauses covers this problem in detail.
Test the most demanding phase rather than tuning at cruise altitude. A dense airport, complex aircraft, heavy cloud and several overlays can expose a bottleneck that remains invisible over open countryside. If image quality still needs adjustment, use our advice on balancing X-Plane graphics clarity against frame rate rather than raising every graphics slider together.
How should I set up X-Plane audio for a stream?
The microphone should remain clearly above engines and environmental sound without either source reaching clipping level.
- Use headphones so speaker audio does not return through the microphone.
- Capture X-Plane audio through one source only. Adding both application audio and full system audio can create doubling or an echo.
- Keep normal voice peaks around -12 to -6 dBFS and place simulator audio several decibels below the voice. Treat those as practical starting points, not mandatory targets.
- Use noise gates conservatively. An aggressive gate can remove the beginning of radio calls or quieter speech.
- Check voice-client and ATC audio separately. Some devices route communications to a headset output that the stream mix does not capture.
- Match the broadcasting app and audio devices to the same sample rate, commonly 48 kHz, to reduce resampling and gradual synchronisation problems.
How do I make cockpit views easier to watch?
Readable, repeatable camera positions are more useful than constant viewpoint changes.
Frame the primary instruments without covering them with chat or camera overlays, and save cockpit and external views through X-Plane’s quick-look system. For more controlled sequences, the documentation for repeatable cockpit and cinematic camera positions explains a dedicated camera tool. Remember that window capture may omit detached avionics displays; use display capture if those panels must be visible.
Why is my X-Plane stream black, blurry or stuttering?
Black video is usually a capture problem, while blur and stutter normally come from scaling, insufficient bitrate, network loss or exhausted rendering resources.
| Symptom | Likely cause | Fix |
|---|---|---|
| Black X-Plane window | Incompatible capture method, mismatched application privileges or different laptop graphics adapters | Switch between application, window and display capture; run both apps at the same privilege level; ensure they use the same graphics adapter |
| Simulator is smooth but stream preview stutters | Broadcast rendering or encoding overload | Use a hardware encoder, lower output frame rate or resolution, simplify overlays and reduce X-Plane GPU load |
| Network dropped frames | Bitrate exceeds sustained upload capacity or the connection is unstable | Lower bitrate, stop background uploads and use a wired connection |
| Blurry cockpit instruments | Too many scaling stages or insufficient bitrate for the selected frame rate | Scale once, favour 1080p30 over 1080p60, or reduce scene motion |
| Audio echo | The same output is captured through two audio sources | Mute one source and monitor the final mix through headphones |
| Washed-out colours | OS-level HDR and SDR capture settings do not match | Use an SDR capture and output workflow unless every stage is deliberately configured for HDR |
What should I check before going live?
A final local recording and a short restricted test stream catch most X-Plane streaming faults before an audience sees them.
- Load the busiest aircraft, airport and weather combination you plan to use.
- Check broadcasting statistics for rendering lag, encoding lag and network drops; each requires a different fix.
- Listen for microphone clipping, doubled simulator sound and missing radio audio.
- Open every pop-out instrument and camera view to confirm it remains inside the captured area.
- Disable desktop notifications and remove account details, pilot names or stream keys from view.
- Verify that cockpit labels remain readable on the encoded recording, not merely in X-Plane itself.
- Save the working scene and output settings as a dedicated X-Plane profile before making further experiments.