Anatomy of an .rdp file
An .rdp file is just text — open one in Notepad and you'll see lines like full address:s:203.0.113.10. Each line is name:type:value, where the type letter matters: s = string, i = integer, b = binary. Double-clicking the file launches Remote Desktop with exactly those settings, no dialogs needed. That's the whole power of RDP file configuration: repeatable, shareable, version-controllable connections.
Tip: keep a folder of .rdp files — one per server — instead of retyping addresses. Name them clearly (trading-vps.rdp, office-dc.rdp) and you'll never fat-finger an IP again.
Creating and editing
Two ways to make one: save from the GUI (open Remote Desktop Connection, set your options, General tab → Save As) or write it by hand in a text editor. The GUI route is best for discovering settings; hand-editing is best for precision. After hand-editing, save with the .rdp extension and Windows will offer to open it with Remote Desktop. One caution: the GUI rewrites the file when you open and re-save from it, which can reorder or drop hand-added lines — keep a master copy if you maintain custom files.
Connection settings
The core of the file — where to connect and as whom:
full address:s:203.0.113.10— server IP or hostname. Add a custom port as203.0.113.10:3390.username:s:admin— pre-fills the login name (the password is never stored here in plain text).domain:s:— leave blank for workgroup servers; set for domain-joined ones.prompt for credentials:i:0— 0 uses saved credentials silently; 1 always prompts. Useful for shared jump boxes.alternate shell:s:— launch a specific program instead of the full desktop (e.g. a single app).
For servers behind a gateway, add gatewayhostname:s:gateway.example.com and gatewayusagemethod:i:2 — see our RDP gateway setup guide for the server side.
Display settings
Display quirks are the #1 reason to hand-edit .rdp files:
screen mode id:i:2— 1 = windowed, 2 = full screen. Full screen withuse multimon:i:1spans all local monitors.desktopwidth:i:1920/desktopheight:i:1080— exact remote resolution. Set both (not just one) or the client may ignore them.session bpp:i:32— color depth; drop to 16 on slow links for a noticeable speed-up.smart sizing:i:1— scales the remote desktop to fit the client window instead of adding scrollbars. Great on small laptops.dynamic resolution:i:1— the remote desktop resizes live when you resize the window (Windows 8.1+ targets).
Device redirection
Redirection bridges your local devices into the remote session — and it's also where most "why doesn't X work" mysteries live:
redirectprinters:i:1— your local printers appear in the remote session. Set to 0 if printing causes session slowdowns.redirectclipboard:i:1— copy/paste between local and remote. If clipboard stops syncing, toggling this and reconnecting usually fixes it.redirectdrives:i:1— maps local drives into the session for file transfer (seedrivestoredirect:s:to limit to specific drives).audiomode:i:0— 0 plays remote audio locally; 2 disables it. Set 2 on metered connections.redirectcomports:i:0/redirectsmartcards:i:0— leave off unless you specifically need them; each adds overhead.
Security note: every redirected device widens the session's attack surface slightly. On untrusted networks, disable drive and device redirection you don't need.
| Goal | Settings to set |
|---|---|
| Full-screen dual monitor | screen mode id:i:2, use multimon:i:1 |
| Fast on slow internet | session bpp:i:16, disable wallpaper:i:1, disable themes:i:1 |
| Local files on remote | redirectdrives:i:1, drivestoredirect:s:C: |
| Print from the server | redirectprinters:i:1 |
| Quiet, no audio | audiomode:i:2 |
| Single app, not desktop | alternate shell:s:C:\app.exe |
| Through a gateway | gatewayhostname:s:gw.example.com, gatewayusagemethod:i:2 |
Security settings
A few lines control how much you trust the connection:
authentication level:i:2— 2 warns on failed server authentication; 0 connects regardless (never use 0 outside a lab).enablecredsspsupport:i:1— enables Credential Security Support Provider, required for Network Level Authentication. Keep at 1.promptcredentialonce:i:1— single sign-on prompt for gateway + session scenarios.
Performance tuning
The "Experience" tab settings, as file lines — the classic slow-connection recipe:
connection type:i:2— 1 = modem, 2 = low-speed broadband, 6 = LAN. This presets the toggles below.disable wallpaper:i:1,disable full window drag:i:1,disable menu anims:i:1,disable themes:i:1— each strips eye candy for speed.bitmapcachepersistenable:i:1— caches bitmaps locally; helps on repeat visits to the same desktop.
On a decent broadband link the defaults are fine; reach for these when sessions feel laggy or you're on mobile data.
Signing and the publisher warning
Hand-edited .rdp files trigger Windows' "unknown publisher" warning because the file's hash no longer matches any signature. For personal use, click through — it's your own file. For team distribution, sign the files with rdpsign.exe and your code-signing certificate; signed files from a trusted publisher connect without the warning. Document which certificate you used so future edits get re-signed, not silently broken.
When an .rdp file won't connect
Most .rdp failures fall into a short list. Work top-down — file, client, network, server:
- Wrong address or port. Retype the
full addressline by hand; a single transposed digit is the most common cause of "it worked yesterday" mysteries. If you changed the server's port, confirm the:portsuffix is there, and try the raw IP instead of the hostname to rule out DNS. - Credential loops. The file pre-fills a username but the login prompt keeps coming back: set
prompt for credentials:i:1to force a clean prompt, type the credentials fresh, and confirm the username line matches the actual account name. - Publisher warning on every open. Expected for hand-edited files — Windows can't verify who changed them. Sign with
rdpsign.exefor team distribution, or accept the prompt for personal files. - Display looks wrong. Set both
desktopwidthanddesktopheight; the client silently ignores one without the other. - Custom lines keep vanishing. Opening the file in the Remote Desktop GUI and saving rewrites it — keep a master copy outside the GUI's reach.
- Gateway lines ignored.
gatewayhostnameandgatewayusagemethodneed a reasonably current client; update Remote Desktop if the file connects directly instead of through the gateway.
If the file is correct and the client is current, the problem is server-side: the RDP listener isn't running, the firewall is blocking the port, or there's an NLA mismatch. Those fixes live on the server — our registry guide covers the listener values and our port guide covers the network side.
Ready for your own RDP server?
Full admin access, dedicated IP, 24/7 support and a 3-day money-back guarantee on every plan.
3-day money-back guarantee · Full admin RDP · Dedicated IP · 24/7 support
rdp file configuration: FAQ
It's a plain-text configuration file for Microsoft Remote Desktop. Each line is a name:type:value setting — server address, display size, redirected devices, security, and performance options. Double-clicking it launches a remote session with exactly those settings.
Either configure a connection in Remote Desktop Connection and use Save As on the General tab, or write the settings by hand in a text editor and save with the .rdp extension. The GUI is best for discovering settings; hand-editing is best for precision.
Hand-edited .rdp files aren't digitally signed, so Windows shows an 'unknown publisher' warning. It's safe to proceed with your own files. For team distribution, sign files with rdpsign.exe and a code-signing certificate to remove the warning.
Lower color depth (session bpp:i:16), disable wallpaper, themes, menu animations and full window drag, and set connection type:i:2. Together these strip the eye candy that eats bandwidth on slow links.
Set screen mode id:i:2 for full screen and use multimon:i:1 to span all local monitors. The remote desktop will then stretch across your displays as one wide desktop.
Yes — that's one of their strengths. Keep a master template in version control, derive per-server copies with the right address and username, and distribute signed files so nobody gets publisher warnings or mistypes an IP.
