A remote desktop gives you one Windows workspace you can reach from your laptop, tablet or phone, with your apps still open where you left them. To feel smooth, it needs enough memory and processing power for the way you actually work. This guide helps you size RAM, CPU and storage for a remote-work desktop, and shows how extra apps and users change the numbers.
Before you start
Make a quick inventory of a normal working day:
- Which browsers you use and roughly how many tabs stay open.
- Office apps: Word, Excel, Outlook or alternatives.
- Communication tools: Teams, Slack, Zoom, WhatsApp Desktop.
- Work software: accounting tools, CRMs, design tools, trading platforms, VPN clients.
- How many people will sign in, and whether at the same time.
For most remote-work setups, a Windows Admin RDP is the natural fit. A Windows VPS also works, especially if you need Windows Server features.
RAM: the number that matters most
Windows needs a few gigabytes for itself before you open anything. On top of that:
- Browsers are usually the biggest user. Each tab is its own process, and web apps such as email, CRMs and dashboards can each take hundreds of megabytes.
- Chat and meeting apps built on web technology use a browser's worth of memory each.
- Office apps are moderate unless you work with very large spreadsheets.
Rough starting points to adjust after you measure:
- Light use (a browser with a handful of tabs, email, one office app): around 4 GB.
- Typical office day (two browsers, many tabs, chat, office suite): around 8 GB.
- Heavy use (dozens of tabs, several work apps, light image editing): 8–16 GB.
When memory runs short, Windows moves data to the page file on disk and every click feels slow.
CPU
Most office work is light on CPU, but it is bursty. Opening apps, loading heavy web pages, video calls and antivirus scans all cause spikes.
- 2 vCPUs suit one person doing light office work.
- 4 vCPUs feel noticeably smoother for heavy browser use, frequent video calls or several apps at once.
Tip: Video calls over Remote Desktop use CPU on the server and bandwidth both ways. For important calls, many people join from their local device instead.
Storage
Windows and its updates take a large share of the disk. Then add:
- Installed apps.
- Browser caches and profiles.
- Downloads and working files.
- Email caches, which grow with large mailboxes.
Keep at least 20–25% of the disk free so updates can install. Store important files in a cloud drive or another backup location too, rather than only on the server.
More than one user
Each signed-in user runs their own copy of every app, so memory needs scale roughly with the number of people working at the same time. Two people each with a busy browser need close to twice the RAM of one.
Note: Windows limits how many people can use Remote Desktop at the same time, and multi-user access on Windows Server can need extra licensing from Microsoft. Check Microsoft's current licensing terms before you plan a shared desktop.
Check it works
After a full working day on the remote desktop:
- Connect with
IP:3389, for example203.0.113.10:3389. - Open everything you normally use.
- Open Task Manager with Ctrl + Shift + Esc and select Performance.
- Check Memory → In use and the CPU graph during your busiest hour.
If memory stays above about 85–90% or the CPU sits near 100% for long periods, trim apps or move to a bigger plan.
Troubleshooting
- Everything feels slow after lunch: browser tabs pile up. Close unused tabs or use a tab-sleeping feature.
- Typing lags but Task Manager looks fine: the delay may be network latency. Choose a server location closer to you. See what is latency.
- Apps close when you leave: close the Remote Desktop window to disconnect. Do not choose Sign out.
- Disk keeps filling: clear the Downloads folder and browser caches, and run Disk Cleanup.
Next steps
- Set up your daily desktop: use Admin RDP as a remote work desktop.
- Use more screens: multiple monitors and display scaling.