Megabit to Word

Divide Mbps by 8 to get megabytes per second (MB/s). A 100 Mbps connection = 12.5 MB/s. A 1 Gbps connection = 125 MB/s. This conversion is essential when comparing advertised internet speeds (always in Mbps) to actual file download speeds (shown in MB/s by browsers and download managers).

Netflix recommends 25 Mbps for 4K Ultra HD. Disney+ and Apple TV+ recommend 25 Mbps; YouTube recommends 20 Mbps for 4K. These are per-stream figures — a household streaming two 4K sources simultaneously needs roughly 50 Mbps of reliable throughput, plus headroom for other devices.

ISP speed ratings are theoretical maximums under ideal conditions. Real-world factors include network congestion, router quality, Wi-Fi interference, the server's upload speed, and protocol overhead. Additionally, browsers and download managers report speeds in MB/s (bytes), which is 8× smaller than the Mbps figure — a 100 Mbps plan showing 11 MB/s in a browser is performing normally.

One gigabit equals 1,000 megabits (SI decimal system). Gigabit broadband (1 Gbps) = 1,000 Mbps = 125 MB/s theoretical download speed. In the binary IEC system, one gibibit = 1,024 mebibits — but for internet speeds the SI decimal values are always used.

Fiber-to-the-home (FTTH) delivers symmetric speeds of 100–10,000 Mbps with consistent performance regardless of distance from the exchange. Cable (DOCSIS 3.1) offers 100–1,200 Mbps download but typically 10–50 Mbps upload, and throughput degrades during neighborhood peak hours due to shared bandwidth. DSL (VDSL2) maxes out at 50–100 Mbps download and drops sharply beyond 500 meters from the DSLAM cabinet. In practice, most cable users see 60–80% of advertised speeds; DSL users at distance may see under 50%. Fiber is the only technology that reliably delivers its rated megabit throughput.

A word's size depends on the CPU architecture. In x86/x64 (Intel/AMD) documentation: word = 16 bits, DWORD = 32 bits, QWORD = 64 bits. In ARM 32-bit: word = 32 bits. In most modern 64-bit systems (excluding x86 documentation): word = 64 bits. When reading technical documentation, always check the architecture's definition, as "word" is not a universal fixed size.

In Windows API documentation and x86 architecture, a DWORD (Double Word) = 32 bits = 4 bytes, capable of holding values 0–4,294,967,295 (unsigned) or -2,147,483,648 to 2,147,483,647 (signed). DWORD is the most common fixed-width integer type in the Windows API, used for flags, handles, and return codes. The equivalent in modern C/C++ is uint32_t (unsigned) or int32_t (signed).

A CPU's word size determines: (1) the maximum addressable memory — a 32-bit CPU addresses up to 4 GiB (2³² bytes); a 64-bit CPU addresses up to 16 EiB (2⁶⁴ bytes); (2) the precision of integer arithmetic — a 64-bit word handles numbers up to ~18.4 × 10¹⁸ in a single instruction; (3) performance — operations on data smaller than the word size may require extra sign-extension instructions on some architectures.

Modern x86-64 CPUs (Intel Core, AMD Ryzen) have 64-bit general-purpose registers, so their native word size is 64 bits for most operations. However, x86 documentation maintains the legacy definition: "word" = 16 bits, DWORD = 32 bits, QWORD = 64 bits. This creates a confusing terminology mismatch between the architectural naming convention and the physical register size.

Memory alignment means storing data at addresses that are multiples of the data's size. A 32-bit word should be stored at an address divisible by 4 (bytes); a 64-bit word at an address divisible by 8. Misaligned access is either forbidden (causes a CPU fault) or penalised (requires two memory reads instead of one). Compilers automatically align variables; manual struct packing can create misalignment that causes subtle performance issues or crashes on strict architectures.