Convert Mbps to Kibibytes per second. A Kibibyte (KiB) = 1,024 bytes (binary), vs Kilobyte (KB) = 1,000 bytes (decimal).
Start ConvertingConvert Mbps to Kibibytes per second. A Kibibyte (KiB) = 1,024 bytes (binary), vs Kilobyte (KB) = 1,000 bytes (decimal).
Watch the conversion happen in real-time as you adjust the speed slider.
Understanding Kibibytes, binary measurements, and why we use them.
A Kibibyte (KiB) is a multiple of the unit byte for digital information. It uses the binary prefix kibi-, meaning 2¹⁰, or 1,024 bytes. This was established by the IEC in 1998 to resolve confusion with the decimal kilobyte (KB) which means 1,000 bytes.
KiB/s (Kibibytes per second) measures data transfer rates. If you download a file at 1 KiB/s, you are receiving exactly 1,024 bytes of data every second. This is the standard measurement unit used internally by computer memory and operating systems like Linux and Windows.
Because 1,024 is larger than 1,000, a measurement in KiB will always be a smaller number than the same measurement in KB. Specifically, there is a 2.4% difference. A 100 KB file is ~97.6 KiB. This difference grows exponentially with larger units (MiB, GiB).
Computers process data in binary (base-2). Random Access Memory (RAM) and processor caches are naturally built in powers of 2. Early computer scientists used "Kilo" to mean 1,024 as it was close to 1,000, causing massive confusion when storage drive manufacturers used "Kilo" to mean 1,000 exactly.
The critical difference between binary and decimal data rates.
Convert Megabits per Second to Kibibytes per Second. Here's the formula and a step-by-step example.
Convert Mbps to Kibibytes per second. A Kibibyte (KiB) = 1,024 bytes (binary), vs Kilobyte (KB) = 1,000 bytes (decimal).
KiB/s = Mbps × 125,000 ÷ 1,024 — The conversion factor is × 122.07.
How the gap between binary (IEC) and decimal (SI) units grows as data gets larger.
Quick reference chart for common Mbps to KiB/s conversions.
How different OSs display download speeds and file sizes.
Windows internally calculates all file sizes and transfer speeds using binary (base-2) math. However, it displays the units as KB, MB, and GB. When Windows says a file is downloading at "12 MB/s", it actually means 12 MiB/s. This is the source of much confusion globally.
Since macOS 10.6 (Snow Leopard) in 2009, Apple completely switched to decimal (base-10) math for file sizes and network speeds. A 1 GB file on a Mac is exactly 1,000,000,000 bytes. Mac download speeds shown in MB/s match your ISP's Mbps exactly (just divide by 8).
Linux distributions and tools are generally the most technically precise. They use binary math (base-2) but correctly label the units as KiB, MiB, and GiB according to the IEC standard. Tools like wget, curl, and dd will display transfer speeds in KiB/s or MiB/s.
Network Attached Storage (Synology, QNAP, TrueNAS), because they are built on Unix/Linux kernels, default to binary calculation. TrueNAS explicitly uses KiB/MiB/GiB in its UI, preventing ambiguity between the storage you bought (decimal) and what is usable (binary).
How your favorite browsers and game launchers report download speeds.
Google Chrome and Microsoft Edge typically follow the OS convention. On Windows, they display KB/s or MB/s (but are actually calculating in binary KiB/s or MiB/s). A 100 Mbps connection will max out around 11.9 "MB/s" in Chrome on Windows.
Firefox is one of the few consumer applications that correctly uses IEC prefixes. When you download a file in Firefox, it will explicitly show your speed in KB/s or MB/s, and it calculates these using decimal math, making it align better with ISP speeds.
Steam displays download speeds in MB/s by default on Windows (which is secretly MiB/s). However, in Steam settings, you can toggle the display to Mbps (Megabits per second) so the numbers align perfectly with what you pay your ISP for.
Game launchers like Epic Games and Battle.net usually show MB/s (calculating in binary on Windows). If you have a Gigabit connection (1,000 Mbps), you will see a maximum download speed of roughly 119 MB/s in these launchers.
Translating Mbps into actual download times using KiB/s.
Note: Real-world overhead (TCP headers, encryption) will reduce this speed by another 5-10%, meaning a 100 Mbps connection usually tops out at ~11.2 "MB/s" in Windows.
Why you don't get "100" in your browser on a "100 Mbps" plan.
Avoid these frequent errors when dealing with KiB/s and KB/s.
Confusing bits (lowercase 'b') with bytes (uppercase 'B'). 100 kbps (kilobits) ≠ 100 KB/s (kilobytes). There are 8 bits in every byte. You must divide Mbps by 8 before accounting for binary vs decimal math.
Assuming that when Windows says "KB" it means 1,000 bytes. Windows is famously the only major OS that still calculates in binary (1,024) but uses decimal labels (KB/MB) instead of IEC labels (KiB/MiB).
Assuming a 100 Mbps connection will give you exactly 11.92 MiB/s of file payload. TCP/IP headers, encryption (TLS/SSL), and protocol overhead consume about 5-8% of your bandwidth, meaning real payload speed is lower.
Writing "Kib/s" or "kib/s" instead of "KiB/s". A capital 'B' means Bytes, while a lowercase 'b' means bits. "Kibit/s" is Kibibits per second (1,024 bits), which is very rarely used.
Applications and tools that strictly enforce IEC binary standards.
Command line utilities like rsync, scp, wget, and curl on Linux distributions natively output their progress and speed using KiB/s, MiB/s, and GiB/s to ensure cryptographic and memory precision.
When allocating memory flags or network limits to Docker containers (--memory="512m"), hypervisors like VMware, Proxmox, and Docker calculate exact memory page limits using binary KiB and MiB.
P2P applications like qBittorrent, Transmission, and Deluge typically use KiB/s or MiB/s. BitTorrent chunks data into powers-of-2 pieces (e.g., 256 KiB, 1 MiB pieces), making binary speed calculations natural.
Professional file transfer applications like FileZilla and WinSCP often default to or offer the option to display speeds in strictly binary KiB/s, ensuring server admins know precisely how many memory bytes are transferring.
Understanding the relationship between Megabits per second and Kibibytes per second.
Converting Mbps to KiB/s helps you understand your actual data throughput. ISPs advertise in Mbps but your experience depends on KiB/s.
Many applications and protocols specify bandwidth in KiB/s. Use this converter to match your network capacity to software requirements.
KiB/s = Mbps × 125,000 ÷ 1,024. Apply × 122.07 to any Mbps value. For example: 10 Mbps = 1,220.7 KiB/s.
Memorize the factor: × 122.07. This lets you do instant conversions in your head whenever you see Mbps values.
Common questions about converting Mbps to KiB/s.
A Kibibyte (KiB) = 1,024 bytes (2¹⁰). The IEC introduced KiB in 1998 to distinguish binary measurement from the decimal Kilobyte (KB = 1,000 bytes). This eliminates the ambiguity that existed when "KB" was used for both 1,000 and 1,024 bytes.
KB/s uses decimal (1,000 bytes per unit). KiB/s uses binary (1,024 bytes per unit). So 1 Mbps = 125 KB/s but only 122.07 KiB/s. The 2.4% difference grows at larger scales — 1 GiB is 7.37% larger than 1 GB.
Linux, memory specs, and technical documentation use KiB/s (binary). Windows and consumer apps typically display KB/s (decimal). If you see download speeds on Linux or in torrent clients, they are almost always KiB/s.
No. 1 KiB/s is actually slower than 1 KB/s when measured in raw bytes. 1 KiB/s = 1,024 bytes/sec while 1 KB/s = 1,000 bytes/sec. However, for the same Mbps speed, the KiB/s number will be lower than KB/s because each KiB is a larger unit. 100 Mbps = 12,500 KB/s but only 12,207 KiB/s.
Linux adopted IEC binary prefixes (KiB, MiB, GiB) to be technically precise. The Linux kernel, dd, wget, and most system tools report in binary units because RAM, caches, and block devices operate in powers of 2. This avoids the ambiguity of "KB" meaning different things on different platforms.
Windows historically displays "KB" but actually means 1,024 bytes (binary). Microsoft chose to keep the familiar "KB/MB/GB" labels for consumer friendliness, even though the underlying values are binary. This creates confusion when comparing speeds across operating systems.
Steam displays download speeds in MB/s or MiB/s (bytes-based), while your ISP advertises in Mbps (bits-based). Additionally, Steam may use binary units internally. A 100 Mbps connection shows ~11.9 MiB/s or ~12.5 MB/s in Steam — not 100, because of the bits-to-bytes division and binary vs decimal difference.
Multiply KiB/s by 1,024 to get bytes/sec, then multiply by 8 to get bits/sec, then divide by 1,000,000 to get Mbps. Formula: Mbps = KiB/s × 1,024 × 8 ÷ 1,000,000. Example: 12,207 KiB/s × 1,024 × 8 ÷ 1,000,000 ≈ 100 Mbps.
No. KiB is an IEC (International Electrotechnical Commission) unit, defined in the IEC 80000-13 standard. SI units use decimal prefixes (kilo = 1,000). IEC binary prefixes (kibi = 1,024, mebi = 1,048,576) were created specifically for computing to eliminate ambiguity.
ISPs use Megabits per second (Mbps) because: (1) bits are the standard unit for network transmission, (2) the higher number is better for marketing (100 Mbps sounds faster than 11.92 MiB/s), and (3) networking standards (IEEE, ITU) define link speeds in bits, not bytes.
No. Wi-Fi standards (802.11ac, 802.11ax/Wi-Fi 6) advertise speeds in Mbps or Gbps. However, your device's transfer speed when downloading over Wi-Fi may be displayed in KiB/s, KB/s, or MB/s depending on your operating system and application.