Word to Gigabyte

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.

Hard drive manufacturers measure 1 TB as 1,000,000,000,000 bytes (decimal). Windows displays storage in gibibytes (binary) but historically labelled them as "GB" — so 1,000,000,000,000 bytes ÷ 1,073,741,824 ≈ 931 GiB, which Windows displayed as "931 GB". macOS (since 10.6) correctly reports the same drive as "1 TB" using decimal GB. The drive is not lying; the OS was using a binary unit with a decimal label.

8 GB RAM is the current minimum for gaming; 16 GB is the recommended standard for most modern games at 1080p and 1440p; 32 GB benefits heavily multitasking systems or games with large open worlds. Memory-intensive tasks like video editing, 3D rendering, and running large language models locally typically require 32–64 GB or more.

A 4K movie in H.264 or H.265 encoding is typically 50–100 GB on Blu-ray; streaming services compress aggressively to 15–25 GB for 4K HDR content. Netflix's 4K streams average about 7 GB per hour; the downloaded version via the Netflix app for offline viewing is roughly 3–6 GB per hour at high quality settings.

1 GB of mobile data supports roughly: 2–3 hours of music streaming, 1 hour of HD video streaming, 2–3 hours of web browsing, or 30–60 minutes of video calling. Social media apps with autoplay video are heavy consumers — TikTok and Instagram Reels can use 300–600 MB per hour of active use.

AI model sizes vary enormously. GPT-2 (2019) is about 1.5 GB; Llama 2 7B is roughly 13 GB in float16 precision; Llama 2 70B is about 130 GB. GPT-4-class models are estimated at 500+ GB. Quantised (compressed) versions are smaller: a 4-bit quantised 7B model fits in about 4 GB, runnable on a modern laptop. Training requires far more — the training dataset, gradients, and optimizer states for a 70B model can occupy 1–2 TB of GPU memory across a cluster. The trend toward larger models is driving consumer GPU memory from 8 GB to 16–24 GB as a baseline for local AI inference.