Using RDP with multiple monitors turns a cramped single remote window into a genuine multi-screen workspace — your remote desktop stretches across two, three, or more of your local displays. The direct answer: in Remote Desktop Connection, go to Show Options → Display → "Use all my monitors for the remote session", connect, and the server desktop spans every screen. But there's a second mode (span), resolution quirks, and a few gotchas with ultrawides that are worth knowing before you rely on it daily. This guide covers both modes, setup on Windows and Mac, and the fixes for the common "it only uses one screen" problem.
The two modes: multi-monitor vs span
RDP offers two different ways to use more than one screen, and they behave very differently:
- True multi-monitor (
/multimon) — the remote session sees each of your monitors as a separate display, with matching resolutions. Windows on the server maximize to one screen, the taskbar can span or sit on one display, and display settings inside the session show real monitors. This is the mode you want. - Span mode (
/span) — the session sees one giant virtual monitor stretched across your screens. Maximizing a window fills all monitors, dialog boxes open straddling the bezel gap, and resolutions can look odd. It's a legacy fallback for old servers.
True multi-monitor requires Windows 7/Server 2008 R2 or newer on both ends — which in practice means everything still in use today. Unless you're connecting to something ancient, always choose multi-monitor over span.
Setup on Windows: step by step
- Open Remote Desktop Connection (
mstsc). - Click Show Options, then the Display tab.
- Check "Use all my monitors for the remote session."
- On the General tab, click Save As to store a
.rdpfile — multi-monitor then works every time you double-click it. - Connect. The remote desktop opens in full screen across all monitors.
From the command line, the same thing is mstsc /multimon /v:your-server-ip. Inside the .rdp file, the relevant lines are use multimon:i:1 and span monitors:i:0 — if a saved file misbehaves, open it in Notepad and check those two values.
Resolution rule: the total span is capped — historically around 4096×2048, higher on current builds. Two 1080p monitors (3840×1080) fit comfortably; three 4K monitors won't. If screens go black, reduce resolution before assuming the feature is broken.
Mac and other clients
In Microsoft Remote Desktop for Mac, edit the PC entry → Display tab → check "Use all monitors." The Mac app also offers "Fit session to window" for quick windowed use. On Linux, FreeRDP handles it with xfreerdp /multimon /v:server; Remmina exposes it as a checkbox in the connection profile. The browser-based web client is the exception — it runs in a single browser tab and doesn't do true multi-monitor, so use a native client for multi-screen work.
Fixing "it only uses one screen"
| Symptom | Likely cause | Fix |
|---|---|---|
| Checkbox is grayed out | Monitors have different DPI scaling or the session is windowed | Set identical scaling in Windows display settings; connect full-screen |
| Only one monitor lights up | Saved .rdp file has use multimon:i:0 | Re-check the box and re-save, or edit the file directly |
| Screens go black on connect | Total resolution exceeds the session cap | Lower resolution or disconnect one monitor and retry |
| Mouse lands in the wrong place | Mixed-DPI monitors confuse coordinate mapping | Match scaling across monitors (e.g., all 100%) |
| Taskbar duplicated oddly | Server-side taskbar spanning settings | Right-click taskbar → Taskbar settings on the remote side and adjust |
| Lag on multi-screen | Pixel count doubled — bandwidth/latency cost | Drop to 16-bit color; see our bandwidth and latency guides |
Daily-use tips
Once it's working, a few habits make multi-monitor RDP genuinely pleasant. Set "Apply Windows key combinations: On the remote computer" (Local Resources tab) so Win+Shift+Arrow throws windows between your remote screens — the shortcuts guide has the full list. If you need your local screens back in a hurry, Ctrl+Alt+Break drops the session out of full screen instantly.
For mixed workflows — say, a local browser on one screen and the RDP session on the other — skip full-screen spanning and just size the RDP window to fill a single monitor. And remember the cost: every extra monitor multiplies the pixels the server must paint and ship, so on a thin connection, two tuned monitors beat three laggy ones. All RDP Temple plans (Shared $6/month, Virtual $28/month, Dedicated $165/month) support multi-monitor sessions with full admin RDP and a dedicated IP — the heavier the multi-screen workload, the more the Virtual and Dedicated tiers earn their keep.
Mixed-DPI setups: the real-world headache
The setup that breaks multi-monitor RDP most often isn't exotic hardware — it's a 4K laptop at 150% scaling next to a 1080p monitor at 100%. Windows has to map one coordinate system onto two different pixel densities, and RDP sessions inherit the mess: mouse clicks land offset from the cursor, text renders at the wrong size on one screen, or the session simply refuses to span.
The fixes, in order of reliability:
- Match scaling across monitors. Set every display to 100% in Windows display settings before connecting. It's slightly small on the 4K screen and slightly large on the 1080p one, but the session maps cleanly and the weirdness vanishes.
- Use the laptop screen or the externals, not both. In display settings, choose "Show only on 2" (or press Win+P) so the session sees uniform displays. You lose a screen, but gain a session that actually works.
- Log off and back on after changing scaling. DPI changes apply per-session; an RDP session started before the change keeps the old mapping until you reconnect. This single step resolves a surprising number of "it worked yesterday" reports.
- Check the client version. Per-monitor DPI awareness in RDP improved significantly in the Windows 10 1703-era client and later. An ancient mstsc on a fully-patched laptop is a combination that produces exactly these symptoms.
If you're buying monitors specifically for RDP work, the boring advice is the right advice: identical monitors at identical scaling eliminate the entire category of problem. Two matching 1440p displays will give you a smoother remote-desktop life than a mismatched 4K-plus-1080p pair that costs more.
Ready for your own RDP server?
Full admin access, dedicated IP, 24/7 support and a 3-day money-back guarantee on every plan. Pay by credit/debit card, bank transfer, Bitcoin or altcoins.
3-day money-back guarantee · Instant setup · 30+ server locations · 99% uptime SLA
RDP Multiple Monitors: FAQ
In Remote Desktop Connection, click Show Options, open the Display tab, check Use all my monitors for the remote session, and connect. Save the connection so the setting sticks.
True multi-monitor treats each display separately, so windows maximize per screen. Span mode stretches one giant desktop across screens, so a maximized window fills every monitor.
Usually the saved connection has multi-monitor off, the session is windowed instead of full-screen, or the monitors use different DPI scaling. Re-check the box, connect full-screen, and match scaling across monitors.
Yes, within the session's total resolution cap. Two 1080p monitors fit comfortably; very high combined resolutions may exceed the cap and need to be lowered.
Yes. Edit the PC entry in Microsoft Remote Desktop for Mac, open the Display tab, and check Use all monitors.
Yes, roughly with pixel count. Two monitors double the pixels of one, so on thin connections drop the color depth or resolution to keep sessions smooth.
