How to Write Numbers Correctly in English
Numbers shape every sentence we write, yet most writers guess their way through them. Mastering the handful of rules that govern numerals instantly lifts clarity, credibility, and reader trust.
Below, you will find the exact practices used by seasoned editors, financial analysts, and technical communicators. Each section isolates a fresh decision point so you can apply the right form without hesitation.
Choose Words or Digits by Magnitude, Not Mood
Single-digit numbers zero through nine appear as words in running text. Ten and above switch to digits unless they open a sentence.
That threshold prevents visual clutter while keeping tiny quantities readable. A grocery list that reads “3 bananas, 12 oranges” jars the eye; “three bananas, 12 oranges” feels balanced.
Journalists often stretch the cutoff to ninety-nine for aesthetic reasons, but academic and business audiences stick with nine for consistency across databases and formulas.
Exceptions Where Digits Always Win
Percentages, money, addresses, page counts, and scores remain numeric even when below ten. Write “5 %,” “$8,” “3 Main St.,” “page 7,” and “a 4–2 win” without spelling.
These elements travel into spreadsheets, search filters, and legal forms; digits future-proof them against re-typing errors.
Position Large Numbers for Instant Scanning
Readers absorb “2.3 million” faster than “2,300,000.” Compress integers above one million to two significant digits followed by the appropriate suffix.
Financial reports pair the abbreviated form with the exact figure in parentheses once: “$4.6 million ($4,615,222).” After that, the short form stands alone.
This dual display satisfies both skimmers and auditors without repeating bulky strings.
Space, Comma, or Thin Space?
Anglophone conventions mark thousands with commas: 45,300. Continental texts often use points; international documents sometimes adopt a thin space: 45 300.
Pick one system per publication and codify it in the style sheet. Never let commas and thin spaces mingle in the same file.
Keep Ordinals Consistent with Cardinals
If you write “12th edition” in a caption, refer to it elsewhere as “12th,” never “twelfth.” Switching forms suggests two different items.
Legal contracts suffer most from this slip; “fourteenth amendment” in the synopsis and “14th Amendment” in the exhibit can void cross-references.
Superscript or Baseline?
Modern web fonts render “1st” baseline as clearly as superscript. Reserve superscript for scientific notation (10⁴) to avoid microscopic strokes that break at low resolution.
Express Ranges with En Dashes and No Surrounding Spaces
Correct form: “pp. 22–27,” “2015–2022,” “9:00–10:30 a.m.” The en dash (–) signals “up to and including,” unlike a hyphen (-) which can mean “versus.”
Always keep the last two digits: “312–15,” not “312–315.” The shortened second number saves space and speeds recognition.
Date Range Shortening
Within the same century, drop the century repeat: “1998–2005” becomes “1998–2005,” but “1998–05” is unacceptable in formal prose.
Separate Phone Numbers for Thumb-Friendly Dialing
Use (555) 123-4567 in North America; +44 20 7946 0958 for international. Chunked groups match the way people memorize strings.
Avoid dot separators; screen readers parse them as decimal points and recite “five hundred fifty-five point one two three.”
Extension Notation
Present extensions with a comma: (555) 123-4567, ext. 890. The comma cues a brief pause, matching verbal dictation.
Anchor Currency Symbols to the Left, Unspaced
Write “$45,” “€120,” “¥8,500.” The symbol acts as a prefix identifier, not a unit, so no gap intervenes.
When the amount is round, drop the decimal zeros: “$75,” not “$75.00.” The shorter form reduces noise in tables.
Currency Conversion Transparency
Quote the exchange rate in parentheses once: “€90 ($98 at 1 EUR = 1.09 USD).” After that, use the local currency only to avoid daily fluctuation clutter.
Quantify Units with a Non-Breaking Space
Correct: “45 km,” “6 lb,” “89 %.” Insert a non-breaking space (Unicode U+00A0) so the digit and unit stay on the same line.
Technical style guides accept the percent symbol with or without a space; pick one and stay with it throughout the document.
Degree Notation
Temperature and angles hug the degree symbol without space: “23°C,” “45°.” Use the same rule for latitude and longitude: “51°30′N.”
Handle Decimal Exactness Like an Engineer
Mirror the precision of your measuring tool. A digital caliper reading of 12.34 mm implies ±0.01 mm accuracy; writing “12.340 mm” falsely advertes three-decimal certainty.
Financial prose keeps two decimals for currency, scientific texts may keep one, four, or six, depending on the discipline.
Trailing Zero Taboo
Never add zeros to imply extra accuracy; auditors treat them as falsified precision and may reject reports.
Render Ratios as Integers When Possible
Write “a 4:3 aspect ratio,” not “1.33:1,” unless the industry standard demands decimals. Integer ratios speed mental modeling.
Cooking yields cleaner recipes with “3:2 flour to fat” instead of “1.5:1.”
Odds versus Probability
Odds keep the colon: “5:1.” Probability uses the percent: “83.3 %.” Mixing the two formats confuses bettors and statisticians alike.
Signal Uncertainty with Parentheses and Plus-Minus
Report: “mean 18.4 (±2.3) kg.” The parentheses isolate the spread from the grammar, letting the sentence read aloud smoothly.
Avoid asymmetric intervals in text; “18.4 (+2.3/–1.8)” belongs in tables where alignment matters.
Confidence Intervals
Write “95 % CI: 0.82–0.96.” The colon introduces the range, and the unit-free interval stays in digits to facilitate meta-analysis scraping.
Start Sentences with Words, Not Digits
Recast “2023 saw record exports” into “The year 2023 saw record exports.” Leading digits slow comprehension until the reader identifies the part of speech.
Where rephrasing feels forced, promote the number to a headline: “2023: Record Year for Exports.” Headlines bypass the sentence rule entirely.
Bullet-Point Exception
Vertical lists may begin with digits because the bullet already signals a new item: “3. Deploy the patch.”
Mix Number Systems in Legal Drafting
Write “forty-five (45) days.” The dual form removes ambiguity if one version is later challenged.
Repeat the paired style for every quantity in contracts; partial pairing invites disputes over omitted numbers.
Auto-Correction Risk
Disable smart fractions in Word; “1/2” auto-converts to “½,” which may not OCR correctly when the contract is scanned in court.
Apply Serial Commas to Serial Numbers
List part numbers as “items 001, 002, and 003.” The serial comma prevents fusion of “002 and 003” into a single range misread.
Keep leading zeros in technical codes; they are significant digits, not ornaments.
Ellipsis versus En Dash in Gaps
Use an en dash for consecutive ranges: “004–007.” Use an ellipsis to show intentional omission: “004 … 009,” implying 005–008 are skipped.
Localize Decimals and Delimiters for Global Readers
English (US/UK) uses a dot for decimals and a comma for thousands: 3,141.59. German reverses them: 3.141,59.
Programmers sidestep conflict with underscores: 3_141.59, a format every compiler accepts.
PDF Layer Strategy
Publish dual-layer PDFs: one layer with US formatting, one with EU, toggled by JavaScript based on browser locale.
Protect Sensitive Figures with Redaction Boxes
Black rectangles over “$––––,–––” leak length clues. Replace the entire number with “[REDACTED]” or a rounded bracketed placeholder: “[$XXX,XXX].”
Uniform placeholders prevent inference attacks that reconstruct hidden values from character counts.
Metadata Scrubbing
Excel retains unseen decimals; round before copy-paste. A redacted “4.7 %” may still contain “4.726 %” in the cell, discoverable under “Show Formulas.”
Make Numbers Accessible to Screen Readers
Tag “$75” with the aria-label “seventy-five dollars.” The machine voice then matches the visual experience.
Avoid pictographic fonts that turn “2019” into a single glyph; assistive tech skips unknown Unicode blocks.
Fraction Alternatives
Offer decimal equivalents: “⅜ in. (9.5 mm).” Dual units widen your audience and satisfy WCAG 2.2 success criterion 1.3.3.
Stress-Test Your Style Sheet with Edge Cases
Run a find-all search for “zero, nil, 0, O” to catch sports scores, phone masks, and license plates in one sweep.
Create a regex that flags numbers adjacent to inconsistent units: “3km” versus “3 km.” A single missing space can break database imports.
Living Document Rule
Date every revision of the style sheet; number formats evolve with software updates and regional standards.