U.S. driver's license number formats by state: what you can actually confirm

Why there is no national format

In the United States a driver's license is issued by each state (and the District of Columbia), not by the federal government. AAMVA, the association of North American motor vehicle administrators, publishes the driver license and ID card design standard, in a 2025 edition, which addresses card aspects such as one- and two-dimensional barcodes. The page does not define a format for the document number, and that is where the diversity comes from: each state inherited its own numbering system, often decades old, from when the number was just an internal database key.

The practical result is a patchwork. Some states use digits only, others start with a letter, some mix letters in the middle, and several accept more than one format at once because older cards remain valid. Pattern lists used by data-loss-prevention tools, such as the Skyhigh Security reference for U.S. license numbers, show this: Arizona appears as 9 digits or 1 letter followed by 8 digits, and North Dakota as a 3-letter, 2-digit, 4-digit layout. Treat that kind of list as a third-party hint, not a specification; the next section uses only what the agencies themselves say.

License number (DLN)

The driver's identifier inside the state's system. It is what forms, insurers and employment checks ask for.

Document number

Identifies one specific physical card and changes at every renewal or replacement. New York separates the two explicitly.

Issuing state

The party that defines the format. The same digits can be valid in one state and impossible in another.

The formats official sources confirm

The table below gathers only what we could check on state agency pages, law-enforcement manuals or federal documents. States missing from it are not "unknown": they just do not publish the format in a way we can cite. California is a good example, since the DMV asks for the number on dozens of forms without describing its structure on any of the pages we consulted.

When the number carries your name and birth date

The most instructive case is Illinois. The state police LEADS manual, dated May 11, 2022, explains that the number is "computed by a special formula" and that each number encodes the driver's name (last name, first name or initial, and middle initial), sex and birth date. That is why an officer can query the database by name, sex and birth date: the system recalculates the number and uses it as the search key.

1. Letter and three digits from the last nameThe first letter of the last name, followed by 3 digits derived from the rest of it. In the manual's example, "Y620".
2. Three digits for first and middle nameA 3-digit code representing the first name (or initial) and the middle initial. In the example, "930".
3. Two digits of the birth yearThe last two digits of the year. In the example, "57" means 1957.
4. Three digits for sex and birth dayThe last three digits signal sex and the encoded birth day. In the example, "270".

The manual also fixes rules that work as sanity checks. The digits 7, 8 and 9 never appear in the first three numeric positions. The last three digits run from 001 to 372 for men and from 601 to 972 for women; the 373 to 600 range is not produced by the formula. When two people compute to the same number, the last three digits are replaced by an assigned value between 400 and 599. Applying that: a number ending in 270 falls in the male range, one ending in 725 would fall in the female range, and one ending in 450 could only be a tie-breaker number. The photo ID card, per the same manual, has the letter at the end rather than the front.

1. Up to 2018Washington: numbers tied to the person

   The old numbers were built from personal details, according to coverage of the 2018 change.

2. September 4, 2018Washington starts issuing "WDL" + 9 random characters

   All newly issued or renewed cards get the new 12-character number, unrelated to name or birth date.

3. May 11, 2022Illinois still documents the formula

   The LEADS manual of that date describes the computation from name, sex and birth date as the current method.

4. July 31, 2024Florida randomizes part of the number

   New numbers now contain at least 4 random digits, under an amendment to statute 322.14(1)(a); the number only changes again if the last name changes.

The direction of the story is clear: numbers derived from personal data let anyone who knows a name and a birth date reconstruct much of the identifier, which makes identity fraud easier. That is why Washington and Florida changed. The details of the two changes are in KOMO's report on Washington and the Ocala Gazette coverage of Florida. For software developers the lesson resembles the one from other identifiers with check digits: do not infer business rules from a format the agency can change without notice.

Testing validation with synthetic data

For QA the goal is to have numbers with each state's right shape, in volume, without using a real person's document. The tool below generates a full synthetic profile for all 50 states and the District of Columbia (name, birth date, address, issue and expiry dates), draws a card with a "SPECIMEN" watermark, and offers a deterministic mode: with the same name, birth date, state and sex you always get the same profile, which is useful for reproducible fixtures. A validation tab checks whether a number has the expected shape for the state.

Validating without blocking real users

Whoever writes the validation for a "license number" field faces two opposite risks: accepting garbage and rejecting legitimate numbers. Given what we saw, the second is the more expensive, because a real user who gets blocked abandons the signup. The New York example shows how easy it is to get wrong: the card has two numbers, one of 9 digits and another of 8 or 10 characters, and the DMV page itself warns that characters such as I and 1 or O and 0 can look alike.

• Accept spaces and hyphens on input and strip them before validating (Illinois prints hyphens on the card).
• Normalize to uppercase, but do not silently swap O for 0 or I for 1.
• Validate per state once the state is chosen, and use a wide length range when it is not.
• Do not assume the format is stable: Florida and Washington changed in 2024 and 2018.
• Treat a format match as "plausible", never as "verified".
• Do not write the number to application logs or echo it in error messages; it is personal data.