How much data does remote desktop use? A per-hour guide for metered connections

The honest answer is "it depends on what is on the screen", which is not useful when you are on a hotspot with a few gigabytes left. The useful answer is that screen content, not the tool, decides the bill — and that the numbers are easy to estimate once you know why.

Why the same session can cost 20 times more

Modern remote desktop tools do not send the screen as a sequence of pictures. They send a video stream, and a video encoder only spends bits on what changed since the previous frame. A spreadsheet you are reading changes almost nothing between frames; a scrolling web page changes most of it; a playing video changes all of it, every frame.

That is why two people using the same tool on the same connection report wildly different numbers. One was editing a document and saw a trickle. The other left a browser tab playing a video on the host and burned through a gigabyte without noticing. Nothing about the tool was different.

• Static content — a document, a terminal, a settings window. The stream drops to a small fraction of its peak between your actions.
• Interaction — typing, clicking through menus, dragging windows. Short bursts every time a region of the screen redraws.
• Scrolling and animation — long web pages, animated dashboards, anything with a moving background. Close to continuous.
• Video and games — the whole frame changes every frame. This is the ceiling, and the encoder runs at whatever rate the connection allows.

From megabits per second to megabytes per hour

Stream rates are quoted in megabits per second (Mbps); data plans are sold in megabytes and gigabytes. The conversion is simple enough to do in your head: one megabit per second sustained for an hour is 3,600 megabits, which is 450 megabytes.

What actually reduces it

1. Stop anything moving on the host. A video playing in a forgotten tab, an animated wallpaper, a screensaver, a clock with a seconds hand. These cost data every second whether or not you are looking at them. This single step matters more than every setting combined.
2. Lower the host's resolution. Fewer pixels changing means fewer bits for the same activity. A 4K host screen viewed on a phone is sending detail you cannot see.
3. Use a smaller window, or one monitor. If the tool lets you view one display or a region, the other screens stop costing anything. See remote sessions with multiple monitors.
4. Prefer keyboard to scrolling. Jumping a page with Page Down redraws once; dragging a scroll bar redraws continuously.
5. End the session when you are done. An open session on a static screen is cheap but not free, and it is easy to leave one running on a phone in your pocket.

The two costs people forget

Both ends pay. The host uploads what the viewer downloads. If the machine you are reaching sits on a metered connection — a 4G router at a holiday house, a mobile hotspot in a workshop — its plan is being drawn down at the same rate as yours.

Relayed sessions do not cost more data, but they can cost more time. When a direct connection is impossible the stream goes through a relay server. The amount of data is the same; the extra distance adds latency, and on a weak link the encoder may lower quality to cope. See why some connections will not establish for when that happens.

A rough budget for a mobile plan

For planning purposes, assume around 200–500 MB an hour for ordinary desktop work and one to two gigabytes an hour for anything involving video. If you have 1 GB left and need to fix a setting on your home PC, that is several hours of careful work or 30 minutes of watching something move. The table above lets you be specific; the rule of thumb is that what moves is what costs.

More guides