Data Sizes & Storage Units

How to say data sizes in English:

Standard formal pronunciation:

• KB = "kilobyte" / "kilobytes" — say: "five hundred and twelve kilobytes"
• MB = "megabyte" / "megabytes" — say: "two point three megabytes"
• GB = "gigabyte" / "gigabytes" — say: "sixty-four gigabytes"
• TB = "terabyte" / "terabytes" — say: "one point four terabytes"
• PB = "petabyte" / "petabytes"
• EB = "exabyte" / "exabytes"

Common informal versions (acceptable in conversation):

• MB → "meg" / "megs" ("a 50-meg download")
• GB → "gig" / "gigs" ("I only have 2 gigs left")
• TB → "tee-bee" or just "terabytes" (no common slang)

Note on plurals: The abbreviations (KB, MB, GB) are not typically pluralised in writing — "512 KB" not "512 KBs". But when reading aloud: "five hundred and twelve kilobytes" (with plural).

Decimal separator: In English, the decimal point is a dot: "1.4 TB" = "one point four terabytes" (not "one comma four" as in many European languages).

Web performance and file size vocabulary:

2.3 MB of JavaScript is a significant performance problem. Context:

Why bundle size matters: JavaScript is not just downloaded — it must be parsed and executed by the browser. A 2.3 MB bundle on a 3G connection (~1.5 Mbps) would take ~12 seconds to download alone, before execution.

Industry benchmarks:

• Well-optimised SPA: 100–250 KB gzipped JavaScript
• Acceptable: under 500 KB gzipped
• Concerning: 500 KB–1 MB gzipped
• 2.3 MB uncompressed → ~600–700 KB gzipped → still heavy

Vocabulary for discussing large files:

• "The bundle is bloated." — informal, common in developer conversation
• "The bundle size is excessive." — more formal
• "We need to reduce / optimise / trim the bundle size."
• "We should code-split the application." — divide into smaller chunks loaded on demand
• "We need to tree-shake the dependencies." — remove unused code
• "The bundle went from 2.3 MB to 340 KB after optimisation — an 85% reduction."

SI units (decimal) vs. binary prefixes — a common source of confusion:

The decimal system (used by hard drive manufacturers and network speeds):

• 1 KB = 1,000 bytes
• 1 MB = 1,000,000 bytes
• 1 GB = 1,000,000,000 bytes
• 1 TB = 1,000,000,000,000 bytes

The binary system (used by operating systems for RAM and file sizes):

• 1 KiB = 1,024 bytes
• 1 MiB = 1,048,576 bytes
• 1 GiB = 1,073,741,824 bytes
• 1 TiB = 1,099,511,627,776 bytes

Why this matters in practice: A "500 GB" hard drive (manufacturer's decimal) shows as ~465 GiB in Windows — this is not a scam or error, it is the binary/decimal difference. A "16 GB" RAM module = exactly 16 GiB because RAM manufacturers use binary.

How to say them:

• GB = "gigabyte"
• GiB = "gibibyte" (from "gibi" = "giga binary")
• MiB = "mebibyte" (not "mibibyte")
• KiB = "kibibyte"

In casual conversation, most engineers use "GB" to mean both — context usually makes it clear.

Reading data quantities aloud — formal vs. informal:

Option B is formally correct: "three terabytes", "two hundred gigabytes", "one point four terabytes"

Key pronunciation notes:

• "terabyte" — stress: TER-a-byte (not "terra-BITE" or "teh-RAH-byte")
• "gigabyte" — stress: GIG-a-byte
• "megabyte" — stress: MEG-a-byte
• "1.4 TB" → "one point four terabytes" (not "one comma four")

Option D is acceptable in casual engineer conversation but uses "gigs" (informal) and "terrabytes" (misspelling). Note: "terabyte" has one "r", not two.

Describing data growth:

• "The database grew from 200 GB to 1.4 TB."
• "The data set expanded from 200 GB to 1.4 TB — a 7× increase."
• "We process 3 TB per day / 3 TB daily." — both formulations are common
• "At 3 TB/day, we process about 90 TB a month." — using the abbreviation in writing