Why Your Download Shows 12 MB/s When Your Internet Plan Is 100 Mbps — Bandwidth vs Speed Explained (Windows 11)

You open Steam, start downloading a game, and the speed sits at 12 MB/s. You check your internet plan — it says 100 Mbps. You open Chrome, download a file — it shows 11.5 MB/s. Something feels off. You are paying for 100, but nothing on your screen ever shows that number.

So you restart your router. You restart your PC. You run a speed test and it says 95 Mbps. But Steam still shows 12 MB/s. Now you are confused — is the speed test lying, is Steam broken, or is your ISP quietly throttling your connection?

None of those things are happening. The number on your screen is not wrong, and your ISP is not cheating you. The entire confusion comes down to one thing — Mbps and MB/s are two different units, and they are not equal. Your internet plan is measured in one unit, your downloads are displayed in another, and the gap between them is exactly 8x. Once you understand why, the math checks out perfectly every time.

This article breaks down exactly why your download speed shows MB/s when your internet plan is in Mbps on Windows 11, what speed you should actually expect from your plan, why you never hit the full theoretical number, and how to tell whether your connection genuinely has a problem — or whether you are just reading two different units.


The Short Answer — Why Your Download Speed Is Always 8 Times Lower Than Your Plan

Your internet plan speed is advertised in Megabits per second (Mbps). Your downloads — whether in Steam, Chrome, Edge, or any other application on Windows 11 — display speed in Megabytes per second (MB/s).

These are not the same unit. One Byte equals 8 bits. That means:

100 Mbps ÷ 8 = 12.5 MB/s

That is the maximum your download can theoretically show on a 100 Mbps connection. When Steam shows 12 MB/s, it is delivering almost exactly what your plan allows. Nothing is broken. Nothing is throttled. The numbers match — they are just written in different units.

Every application that downloads files — Steam, Epic Games Launcher, browser download managers, torrent clients — uses MB/s by default. Every ISP on the planet advertises plans in Mbps. This mismatch is the single biggest reason people think their internet is underperforming when it is actually working at full capacity.

The rest of this article explains exactly how this conversion works, what realistic speeds look like for different plans, and when a low number actually does signal a real problem worth investigating.

Technician monitoring network activity during a download using performance monitoring tools.
Task Manager can reveal how much bandwidth a system is using.

What Mbps and MB/s Actually Mean — The Difference That Causes All the Confusion

The confusion between Mbps and MB/s is not a Windows 11 issue, not a software bug, and not something your ISP invented to trick you. It comes from two legitimate units of digital measurement that are used in two different contexts — and most people are never told the difference.

What a Bit Is and What a Byte Is — The Root of the Problem

A bit is the smallest unit of digital data. It is a single binary value — either a 0 or a 1. On its own, a bit cannot represent much. It takes a group of bits working together to form anything meaningful.

A byte is a group of exactly 8 bits. One byte can represent a single character — a letter, a number, a symbol. When you see a file size on your computer — say, a 500 MB game update — that size is measured in Megabytes. Each of those Megabytes contains 8 Megabits worth of data.

This 1-to-8 relationship is the entire reason your download speed number looks so much smaller than your internet plan number. Your plan measures data flow in bits per second. Your download manager measures data received in bytes per second. Same data, different scale.

Why ISPs Advertise in Mbps but Downloads Show MB/s

ISPs advertise in Megabits per second because that is the standard unit for measuring bandwidth and network throughput. Networking hardware — routers, switches, network cards, fiber terminals — all rate their capacity in bits per second. When your ISP says your plan is 100 Mbps, they are describing how many millions of bits their connection can push to your home every second.

Download applications, on the other hand, care about files. Files are stored and measured in bytes. When Steam downloads a 20 GB game, it tracks how many Megabytes it receives per second because that directly tells you how fast the file is being written to your disk. Showing bits per second in a download manager would be technically accurate but practically useless for estimating how long a download will take.

Neither side is wrong. ISPs use the networking standard. Applications use the file-size standard. The problem is that nobody puts a clear label explaining the difference — so you see 100 in one place and 12 in another, and assume something is broken.

The Simple Formula — How to Convert Mbps to MB/s Yourself

The conversion is straightforward:

MB/s = Mbps ÷ 8

That is all there is to it. Take whatever your ISP plan says in Mbps, divide by 8, and you get the theoretical maximum download speed in MB/s.

A few quick examples:

  • 50 Mbps ÷ 8 = 6.25 MB/s
  • 100 Mbps ÷ 8 = 12.5 MB/s
  • 200 Mbps ÷ 8 = 25 MB/s
  • 500 Mbps ÷ 8 = 62.5 MB/s
  • 1 Gbps (1000 Mbps) ÷ 8 = 125 MB/s

If you want to go the other direction — say your download shows 37 MB/s and you want to know what that equals in Mbps — just multiply by 8. That gives you 296 Mbps.

Keep this formula in mind for the next section, where we look at what realistic download speeds actually look like for the most common internet plans — and why even after converting, you still will not hit the exact theoretical number.

What Download Speed You Should Actually Expect From Your Internet Plan

Now that the conversion formula is clear, the next question is obvious — what number should you actually see on your screen? Because even after dividing by 8, your real download speed will almost never land exactly on the theoretical maximum. There is always a small gap, and that gap is normal.

Here is what realistic download speeds look like for the three most common plan tiers.

100 Mbps Plan — What Normal MB/s Looks Like

Theoretical maximum: 12.5 MB/s

In practice, you should expect somewhere between 10.5 and 12.2 MB/s on a stable wired connection downloading from a fast server. If Steam shows 11.5 MB/s or Chrome shows 11.8 MB/s, your connection is performing exactly as it should. You are getting what you are paying for.

If you consistently see speeds below 9 MB/s on a wired connection with no other devices actively using the network, that is when it is worth investigating further.

200 Mbps Plan — What Normal MB/s Looks Like

Theoretical maximum: 25 MB/s

Realistic range on Ethernet: 21 to 24.5 MB/s. Downloads from well-connected servers like Steam’s CDN or Microsoft’s update servers will typically land in this window. Browser downloads from smaller servers may show lower numbers — that is a server-side limitation, not your connection.

Anything consistently above 20 MB/s means your 200 Mbps plan is delivering properly.

500 Mbps Plan — What Normal MB/s Looks Like

Theoretical maximum: 62.5 MB/s

Realistic range on Ethernet: 52 to 60 MB/s. At this tier, you are more likely to hit server-side limits. Not every download source can push data at 500 Mbps. Steam, Microsoft, and major CDN-backed downloads will usually come close. Smaller file hosts and regional servers may cap well below your plan speed regardless of how fast your connection is.

Seeing 55 MB/s on a 500 Mbps plan is completely normal and expected behavior.

Why You Never Hit the Full Number Even After Converting

Even if every condition were perfect — fast server, wired connection, no other devices, no congestion — you would still not see exactly 12.5 MB/s on a 100 Mbps plan. The reason is that raw data is never the only thing traveling through your connection.

Every internet connection uses protocols like TCP and IP to manage data transmission. These protocols attach headers, error-correction data, and acknowledgment packets to every piece of information that moves. This is called protocol overhead, and it consumes roughly 5 to 10 percent of your total bandwidth before any file data is transferred. That overhead is invisible to you but it is always present.

On top of that, if you are connected over WiFi instead of Ethernet, additional overhead from wireless encryption, signal negotiation, and interference reduces your usable throughput even further. This is one of the core reasons WiFi often feels slower than your speed test suggests — the raw connection speed and the usable file-transfer speed are never the same number.

The next section breaks down all five real-world factors that prevent your download from ever matching the full plan speed — and which ones you can actually do something about.

Person analyzing multiple applications consuming internet bandwidth on a laptop.
Several apps using the network simultaneously can reduce download speeds.

Why You Never Get 100 Percent of Your Plan Speed — 5 Real Reasons

The unit conversion explains the biggest chunk of the gap between your plan number and your download number. But even after converting Mbps to MB/s, there is still a difference. That remaining gap comes from real, measurable factors that affect every internet connection. None of them are bugs, and most of them are unavoidable to some degree.

Reason 1 — Protocol Overhead Reduces Every Connection by 5 to 10 Percent

Every piece of data sent over the internet is wrapped in protocol layers — TCP headers, IP headers, Ethernet framing. These layers handle addressing, error checking, and delivery confirmation. They are essential for reliable data transfer, but they consume bandwidth that does not count toward your actual file download.

On a typical connection, protocol overhead eats roughly 5 to 10 percent of total throughput. On a 100 Mbps plan, that alone drops your usable bandwidth to around 90–95 Mbps before your download application ever sees the first byte of file data. When packet loss is present on the connection, the overhead increases further because TCP has to retransmit lost segments, consuming even more bandwidth without moving your download forward.

Reason 2 — The Server You Are Downloading From Has Its Own Speed Limit

Your ISP controls how fast data reaches your home. But the server hosting the file controls how fast it sends data out. If you are downloading from a small file-hosting site running on limited infrastructure, that server may only push 5 or 10 MB/s to each user regardless of how fast your connection is.

Major platforms like Steam, Microsoft Update, and Epic Games use large CDN networks that can usually saturate most residential connections. Smaller servers, regional mirrors, and single-host download links often cannot. If one download is slow but others hit your expected speed, the bottleneck is the source — not your connection.

Reason 3 — WiFi Reduces Your Real Throughput vs Ethernet

WiFi introduces overhead that does not exist on a wired connection. Wireless encryption, channel contention, signal attenuation through walls, and interference from neighboring networks all reduce the amount of usable throughput your device actually receives.

A 100 Mbps plan over WiFi may deliver 60 to 85 Mbps of real throughput depending on signal quality, distance from the router, and band selection. This is why WiFi ping tends to run higher than Ethernet on the same router — wireless connections carry more variability and more overhead in every direction. If you want to verify whether your connection is delivering full plan speed, always test on Ethernet first.

Reason 4 — Other Devices on Your Network Share the Same Bandwidth

Your internet plan provides a total bandwidth pool for your entire household — not per device. If someone is streaming 4K video, another device is syncing cloud backups, and a phone is updating apps in the background, your download is splitting that 100 Mbps with all of them.

This is especially noticeable on plans below 200 Mbps. A single 4K stream can consume 25 Mbps, immediately cutting your available download bandwidth by a quarter. If your internet lags during large downloads, the issue is often bufferbloat caused by one device saturating the connection while others compete for the remaining capacity.

Reason 5 — Peak Hours Reduce ISP Throughput

ISPs provision bandwidth at the neighborhood level. During evening hours — typically 7 PM to 11 PM — when many households in your area are streaming, gaming, and downloading simultaneously, the shared infrastructure gets congested. Your plan still says 100 Mbps, but the actual throughput your ISP can deliver to your specific connection may drop to 70 or 80 Mbps during these windows.

This is one of the most common reasons your internet slows down noticeably at night but works perfectly during the day. The speed difference is not dramatic on fiber connections, but on cable and DSL, peak-hour degradation is measurable and consistent.

User connecting an Ethernet cable to a laptop during a speed test.
Testing speeds over a wired connection removes WiFi interference.

How to Check What Speed You Are Actually Getting on Windows 11

Understanding the Mbps-to-MB/s conversion is one thing. Knowing how to verify your actual connection performance is another. Windows 11 gives you built-in tools to monitor real-time throughput, and free browser-based speed tests let you measure your connection against what your ISP promises. Here is how to use both — and how to read the results correctly.

How to Check Real-Time Download Speed in Task Manager

Windows 11 Task Manager shows live network usage for every application on your system. To check it:

  1. Press Ctrl + Shift + Esc to open Task Manager.
  2. Click the Performance tab on the left sidebar.
  3. Select Ethernet or WiFi depending on your connection type.

You will see a live graph showing current send and receive throughput. The numbers here are displayed in Kbps or Mbps — not MB/s. So if you see 95 Mbps while a download is running, divide by 8 to get the MB/s equivalent. That 95 Mbps equals roughly 11.8 MB/s, which matches what your download manager is showing.

Alternatively, click the Processes tab and look at the Network column. This shows per-application bandwidth usage in Mbps. If Steam is using 92 Mbps and your browser is using 6 Mbps, you can see exactly where your bandwidth is going and whether multiple applications are competing for throughput.

How to Run a Speed Test and Read the Result in Both Mbps and MB/s

Speed test tools measure your connection’s maximum download and upload throughput directly against a test server. The two most reliable browser-based options are Cloudflare Speed Test{:target=”_blank” rel=”nofollow”} and Fast.com by Netflix{:target=”_blank” rel=”nofollow”}. Both work directly in your browser with no installation required.

For the most accurate result, follow these steps before testing:

  • Connect via Ethernet, not WiFi.
  • Close all other applications that might use bandwidth.
  • Pause any active downloads, cloud syncs, or streaming.
  • Make sure no other devices on your network are doing heavy transfers.

Speed test results are displayed in Mbps. If your test shows 94 Mbps on a 100 Mbps plan, divide by 8 — that gives you 11.75 MB/s, which is exactly the kind of number you should see in your download manager. The speed test confirms your ISP is delivering properly. The download manager confirms the application is receiving at the correct rate. They are just reporting in different units.

If you want a deeper comparison of available testing tools and what each one measures beyond raw speed — including latency and jitter — there is a detailed breakdown in our speed test tools guide.

What a Normal vs Problem Speed Looks Like for Your Plan

Here is a quick reference to identify whether your speed is healthy or worth investigating:

Internet PlanExpected MB/s (Ethernet)Investigate Below
50 Mbps5.2 – 6.0 MB/sBelow 4 MB/s
100 Mbps10.5 – 12.2 MB/sBelow 8 MB/s
200 Mbps21 – 24.5 MB/sBelow 16 MB/s
500 Mbps52 – 60 MB/sBelow 40 MB/s

If your speeds consistently fall within the expected range on a wired connection, your internet is working as it should — the MB/s vs Mbps difference was the only issue. If your numbers fall into the “investigate” column regularly, something else is reducing your throughput beyond normal overhead and conversion differences.

When Low Download Speed Is a Real Problem — Not Just the MB/s vs Mbps Confusion

Once you understand the unit difference and account for normal overhead, you can clearly separate a non-issue from a genuine connection problem. Most people who search for why their download shows MB/s when their internet plan is in Mbps on Windows 11 discover that nothing was ever wrong. But sometimes, the speed really is too low — and knowing how to identify that matters.

How to Tell If You Are Getting Less Than You Should After Conversion

The process is simple. Take your plan speed in Mbps, divide by 8, and subtract roughly 10 percent for overhead. That gives you the realistic floor for your connection on Ethernet.

For a 100 Mbps plan: 100 ÷ 8 = 12.5 MB/s. Subtract 10 percent and you get approximately 11.25 MB/s. If your wired download speeds consistently sit at 11 MB/s or above, your connection is healthy. If you are regularly seeing 6 or 7 MB/s on Ethernet with nothing else using the network, that is a real problem — not a unit confusion issue.

The key word is consistently. A single slow download from a remote or overloaded server does not indicate a connection issue. But if multiple downloads from major platforms like Steam, Microsoft, and other CDN-backed sources all underperform after proper conversion, your connection is not delivering what your plan promises.

What to Check First If Real Speed Is Way Below What Your Plan Allows

If your converted speed is genuinely lower than it should be, work through these checks in order:

  1. Test on Ethernet, not WiFi. WiFi introduces too many variables to diagnose an ISP-level issue. Always rule out wireless problems first.
  2. Run a speed test during off-peak hours. If your speed test shows significantly less than your plan during low-traffic hours (mid-morning, early afternoon), the issue is likely between your ISP and your home — not network congestion.
  3. Check for background bandwidth usage. Cloud sync services, Windows Update, game launchers auto-updating — all of these consume bandwidth silently. Task Manager’s Processes tab reveals exactly which applications are using your network.
  4. Restart your modem and router. A full power cycle — 30 seconds off, then back on — clears cached routing states and sometimes resolves throughput drops caused by stale connections.
  5. Contact your ISP with test results. If wired speed tests consistently show 50–60 Mbps on a 100 Mbps plan during off-peak hours with no local interference, the problem is on your ISP’s end. Provide them with timestamps and test results.

If your speed test shows full speed but actual browsing and downloads feel slow, the issue may be related to DNS resolution, QoS misconfiguration, or router-level bottlenecks rather than raw bandwidth. Similarly, if you notice ping spikes when someone else on your network starts a download or stream, the problem is traffic prioritization — not total speed.

Multiple household devices connected to a router while a person checks network performance.
Every connected device shares the available internet bandwidth.

Frequently Asked Questions

Why does Steam show 12 MB/s when I have 100 Mbps internet?

Because Steam displays download speed in Megabytes per second (MB/s), while your internet plan is measured in Megabits per second (Mbps). Since 1 Byte equals 8 bits, 100 Mbps divided by 8 equals 12.5 MB/s. Steam showing 12 MB/s means your connection is performing at near-maximum capacity.

What is the difference between Mbps and MB/s?

Mbps stands for Megabits per second — the unit used by ISPs to describe connection bandwidth. MB/s stands for Megabytes per second — the unit used by download managers and applications to show file transfer speed. One MB/s equals 8 Mbps.

Why is my download speed 8 times lower than my internet plan?

It is not actually lower. Your plan and your download are reporting in different units. Mbps measures bits, MB/s measures bytes, and there are 8 bits in every byte. The 8x difference is purely a unit conversion, not a performance gap.

How do I convert Mbps to MB/s?

Divide your Mbps value by 8. For example, 200 Mbps ÷ 8 = 25 MB/s. To convert MB/s back to Mbps, multiply by 8.

What download speed should I get on a 100 Mbps plan?

The theoretical maximum is 12.5 MB/s. In practice, expect 10.5 to 12.2 MB/s on a wired Ethernet connection. Slightly lower speeds on WiFi are normal due to wireless overhead.

Why does my speed test show 100 Mbps but my download is only 12 MB/s?

The speed test reports in Mbps. Your download application reports in MB/s. Both numbers represent the same throughput — 100 Mbps equals 12.5 MB/s. The results actually match perfectly.

Is 12 MB/s a good download speed for a 100 Mbps plan?

Yes. 12 MB/s on a 100 Mbps plan means you are receiving 96 Mbps of actual file data, which is excellent. After accounting for protocol overhead, that is nearly the maximum your plan can deliver.

Why does my download speed vary so much on the same internet plan?

Multiple factors affect download speed moment to moment — server capacity, number of devices sharing your connection, WiFi signal quality, network congestion during peak hours, and protocol overhead. Some variation is completely normal. Large, consistent drops below your expected range are worth investigating.


Wrapping Up

The gap between your internet plan number and your download speed number is not a defect, not a scam, and not a Windows 11 issue. It is a unit conversion — Megabits vs Megabytes, a factor of 8. Once you divide your plan speed by 8, the math lines up almost every time.

If your 100 Mbps plan delivers 10.5 to 12.2 MB/s in downloads over Ethernet, everything is working correctly. If your speeds fall significantly below that range consistently — across multiple servers, on a wired connection, during off-peak hours — contact your ISP with documented speed test results and timestamps. That is the only scenario where the problem is real and not just a misread number.

Leave a Comment