US Address Format Explained: USPS Addressing Rules

Every US mailing address follows the same compact grammar, and once you can read it, form design, address validation and test-data generation all get easier. The authoritative rulebook is USPS Publication 28, which defines how addresses should be standardized for mail processing ^[pub28]. This guide walks the format part by part, with the standard abbreviations and worked examples — and shows what a structurally correct but fictional test address looks like.

The scale involved explains why the format is so strict: USPS serves more than 165 million delivery points across the country ^[usps-facts], organized under roughly 41,000 active ZIP codes ^[zip-wiki]. At that volume, addresses are machine-read and machine-sorted — a predictable structure is not bureaucratic pedantry, it is what makes next-day sorting physically possible.

The two lines that matter

Strip away recipient names and company lines and a domestic address reduces to two functional lines. The delivery address line locates the point: primary number, street name, suffix and any secondary unit. The last line routes it: city, two-letter state abbreviation, and ZIP code ^[pub28].

Standard abbreviations: why AVENUE becomes AVE

Publication 28 defines a canonical abbreviation for every street suffix and unit designator — over 200 suffix variants map onto a much smaller standard set: AVENUE, AVENU and AV all standardize to AVE; BOULEVARD to BLVD; APARTMENT to APT ^[pub28]. Address-validation APIs (and the CASS-certified software behind shipping labels) rewrite input into this canonical form, which is why the address you typed in a checkout often comes back subtly different.

• Common suffixes — ST (Street), AVE (Avenue), BLVD (Boulevard), DR (Drive), LN (Lane), RD (Road), CT (Court), PL (Place), PKWY (Parkway), CIR (Circle).
• Directionals — N, S, E, W, NE, NW, SE, SW, before or after the street name: 100 N MAIN ST, 200 OAK AVE SW.
• Unit designators — APT, STE (Suite), UNIT, FL (Floor), RM (Room), BLDG (Building); '#' is discouraged in standardized form.
• States — always the two-letter code: TX, CA, NY. Old-style abbreviations like Calif. or Tex. are not valid in the last line.

How the ZIP code ties it together

The last line's ZIP code is what actually routes the piece: the first digit places the address in one of ten national zones, the first three digits identify a sectional center facility, and the full five digits a delivery area ^[pub28]. The optional +4 narrows further to a block face or building. Crucially, ZIP prefixes are geographically consistent — 787 is central Texas, 100 is Manhattan — so an address whose city, state and ZIP disagree fails validation instantly. We cover the system in depth in what is a ZIP code.

Worked examples

Note what standardization did: spelled-out words became canonical abbreviations, punctuation disappeared, '#' became a designator, and every last line gained a correct ZIP. If your form or fixture data round-trips through a validation API unchanged, it was already well-formed.

Generating structurally correct test addresses

For developers, the payoff of understanding the format is better fixtures: addresses that pass real validators without pointing at real homes. The random address generator applies the rules above — real city/state pairs, state-consistent ZIP prefixes, randomized street and number — and the state pages and city pages pin results to a specific place when your test needs, say, a Texas address. For a full profile around the address (name, 555-range phone, email), use the complete identity generator.

The bottom line

A US address is a small, strict format: delivery line plus last line, canonical abbreviations, and a ZIP that must agree with its city and state. Learn the grammar once and you can design better address forms, debug validation failures faster, and recognize immediately why good generated test addresses look the way they do.