IT explained · 7 min read

What is bandwidth? Capacity, latency and why remote sessions lag

Written for: Anyone diagnosing a slow connection, sizing a link for remote work, or trying to understand why a fast broadband package did not fix a laggy session.

Capacity versus delay

A wide pipe carrying parallel data lanes next to a narrow pipe, with a latency clock measuring round-trip delay.A wide pipe carrying parallel data lanes next to a narrow pipe, with a latency clock measuring round-trip delay.
Bandwidth is how much fits through the pipe at once. Latency is how long each piece takes to arrive. Remote sessions feel slow for the second reason far more often than the first.

In short

Bandwidth is the maximum amount of data a connection can carry per second, usually quoted in megabits per second. It is capacity, not speed: a wider pipe does not make each piece of data arrive sooner. That distinction matters because when a remote session feels sluggish, the cause is usually latency, packet loss or jitter rather than a shortage of bandwidth.

Key takeaways

  • Bandwidth is capacity per second. Latency is delay per round trip. They are different measurements and they fail differently.
  • Megabits (Mb) are not megabytes (MB). Divide the advertised figure by eight to get a realistic download rate.
  • A typical remote support session needs far less bandwidth than people assume, often under 2 Mbps, but it is sensitive to latency and loss.
  • Upload capacity matters more than download for the machine being controlled, because it is the one sending the screen.
  • Contention, not capacity, causes most complaints: the line is fine until forty people join video calls at once.

Bandwidth, in one paragraph

Bandwidth is the maximum volume of data a link can move in a given second. The standard unit is megabits per second, written Mbps. A 100 Mbps connection can carry one hundred million bits every second, no more, however you divide that between users and applications.

The plumbing metaphor is useful if you keep it accurate. Bandwidth is the width of the pipe. Latency is how long water takes to travel from one end to the other. Widening a pipe does not shorten it, which is exactly why upgrading a broadband package often makes no difference to a session that feels laggy.

The three measurements that actually describe a connection

When someone says a connection is slow, they mean one of three specific things, and the fix for each is different.

  • Bandwidth: capacity per second. Too little means transfers take longer and heavy applications compete with each other.
  • Latency: round-trip delay, measured in milliseconds. High latency makes interaction feel disconnected, because your keystroke takes noticeably long to appear.
  • Packet loss and jitter: data that never arrives, or arrives out of rhythm. This produces the frozen-then-catching-up behaviour people describe as stuttering.

Megabits versus megabytes

Consumer connections are advertised in megabits per second while file sizes are quoted in megabytes. There are eight bits in a byte, so a 100 Mbps line downloads at roughly 12.5 megabytes per second at best. This single unit confusion is behind a large share of complaints that a connection is not delivering what was sold.

Real throughput sits below the theoretical figure anyway, because protocol overhead, contention and the far end of the connection all take their share.

How much bandwidth a remote session needs

Less than most people expect. A remote control session sends compressed screen updates, not raw video, and modern tools only transmit the regions that changed. Text editing and administration on a single monitor typically fit comfortably inside 1 to 2 Mbps. Full-screen video, CAD work or three high-resolution monitors are a different matter and can consume ten times that.

The direction matters. The machine being controlled is uploading its screen, so its upload capacity is the constraint. Home connections are usually asymmetric, with far less upload than download, which is why supporting a home worker sometimes feels worse than supporting an office machine on a slower headline speed.

  • Administration and text work, single monitor: roughly 0.5 to 2 Mbps
  • General desktop use with graphics: roughly 2 to 5 Mbps
  • Multiple monitors or video playback: 10 Mbps and upwards
  • File transfer alongside a session: whatever is left, so cap it if responsiveness matters

Why the line looks fine and the session does not

Speed tests measure a best case: one stream, to a nearby server, at the moment you clicked. They tell you almost nothing about contention at 9am, a saturated upload during a cloud backup, Wi-Fi interference between the laptop and the router, or an overloaded VPN concentrator adding thirty milliseconds to every packet.

When diagnosing, measure latency and loss over time rather than bandwidth once. A continuous ping to a fixed target during the period when users complain is more diagnostic than any single speed test.

What each symptom points to

What each symptom points to
Cursor lags behind the mouseLatency, not bandwidth
Screen freezes then jumpsPacket loss or jitter
Large files crawl but the session is fineGenuine bandwidth shortage
Fine at 8am, unusable at 10amContention on a shared link
Only one user affectedLocal Wi-Fi or that device's upload

Select any column heading to sort.

Common mistakes

  • Buying more bandwidth to fix a latency problem, then being surprised nothing changed.
  • Testing from the office when the complaint comes from home workers.
  • Ignoring upload capacity on the controlled machine, which is the side sending the screen.
  • Running a single speed test at a quiet time and treating it as proof the link is healthy.

Frequently asked questions

What is bandwidth in simple terms?
The maximum amount of data a connection can carry each second, usually quoted in megabits per second. It is the capacity of the link, not how quickly each piece of data arrives.
Is bandwidth the same as internet speed?
No. Bandwidth is capacity and latency is delay. A high-bandwidth connection with high latency still feels slow for interactive work such as remote control or video calls.
How much bandwidth do I need for remote desktop?
Around 1 to 2 Mbps is enough for administration and text work on a single monitor. Multiple high-resolution monitors or video playback can need 10 Mbps or more.
Why is my remote session slow when my broadband is fast?
Almost always latency, packet loss or the upload capacity of the machine being controlled. Headline broadband figures describe download capacity, which is the least relevant number for a remote session.
How do I measure bandwidth properly?
Test repeatedly across a working day rather than once, test from the location that has the problem, and record latency and packet loss alongside throughput.

How this works in 247connect

247connect is built for constrained links, adapting session quality to the connection rather than assuming office bandwidth, which is what makes supporting home and field devices practical rather than painful.

Start a 14-day free trialSee the feature list

More IT explainers