Skip to content

Reference

Why a VIN won't decode

A VIN that returns nothing is usually not a broken tool. It is usually a vehicle outside the database, or a character read wrong.

By Pixoware. Published 12 September 2026, updated 28 October 2026.

“Won't decode” covers three different outcomes. The decoder can refuse the number before looking anything up, because it is the wrong length or contains characters a VIN cannot have. The check digit can fail. Or the lookup runs and NHTSA's database returns little or nothing. Each has a short list of causes, and working through them in order usually settles which one you have.

Step 1: count the characters

Every VIN under 49 CFR Part 565 is exactly seventeen characters, every position filled, using the digits 0–9 and the capital letters other than I, O and Q. NHTSA began requiring the seventeen-character VIN with the 1981 model year.

Step 2: check the check digit

Position 9 is computed from the other sixteen characters, so most single-character typos make it fail. Run the number through the check digit validator. If it fails, assume a typo before anything more exotic. The common mix-ups are 8 and B, 5 and S, and 2 and Z.

When the check digit fails, our decoder tells you what position 9 should be and offers two buttons: one to change character 9 to that value, and one to decode the number as typed. Use the first only if you are sure position 9 is the character you misread. If the mistake is somewhere else, “fixing” position 9 produces a VIN that passes the check and describes a different vehicle. Going back to the plate is always the better fix.

NHTSA's database will often decode a VIN with a bad check digit anyway, and say so: its response includes “Check Digit (9th position) does not calculate properly.” Treat anything it returns in that case with suspicion until you have rechecked the number.

One honest exception: Part 565 is a US rule. A vehicle built only for another market was not made to it, so a failed check digit on a genuine foreign-market vehicle is possible.

Step 3: work out why the lookup came back empty

NHTSA's vPIC database, which our decoder queries, is built from the VIN-deciphering information manufacturers file under 49 CFR 565.16. If there is no filing that covers your number, there is nothing to decode, however correct the number is. That is the common thread in every case below.

It was built before 1981

Before the 1981 model year, manufacturers used their own identification formats of varying lengths. A 1974 vehicle has a perfectly valid identification number that is not a VIN in the modern sense, and our decoder, which is built for the seventeen-character format, will not read it. NHTSA's own API offers some support for older ranges when a model year is supplied, but for a classic car the title, the manufacturer's records and owners' clubs are usually better sources.

It was not built for the US market

A car built for the European, Japanese or Australian market was never filed with NHTSA, so there is nothing to look up, even though its VIN may be real and correctly formed. Federal rules recognize this in two places. Vehicles that are at least 25 years old are exempt from the ban on importing vehicles that do not meet US safety standards. And a car, SUV or light truck certified by a registered importer whose original VIN does not meet Part 565 must carry a plate inside the passenger compartment, readable through the windshield, reading “SUBSTITUTE FOR U.S. VIN” with the original number. That plate tells you the vehicle was not built for the US market, and the original manufacturer's number is unlikely to be in NHTSA's database.

It is too new

Manufacturers must file their coding with NHTSA at least 60 days before offering the first vehicle that uses it for sale, and must file amendments when the coding changes. A brand-new model, or a mid-year change, can still produce a thin result for a while. The typical sign is a decode that returns the make, model year and vehicle type but no model, with vPIC's message “No detailed data available currently.” Try again later.

It is from a small manufacturer, or it is a trailer

A manufacturer building fewer than 1,000 vehicles of a type a year uses a six-character identifier: a 9 in position 3, with positions 12–14 completing the maker's code. If you see a 9 in position 3, those three middle characters are part of the manufacturer's identity, not the serial number. Small makers file like anyone else, but how complete the result is depends on what they filed.

Trailers decode differently even when everything works. Part 565 only requires a trailer VIN to encode the make, type of trailer, body type, length and axle configuration. There is no engine, restraint system or trim level to report, so a complete trailer decode looks sparse beside a car's.

It is a kit, homemade or reconstructed vehicle with a state-assigned VIN

When there is no manufacturer — a homemade trailer, a specially constructed or replica car, a rebuilt vehicle whose original number is missing — the state assigns one. Virginia's form VSA 22, for example, covers homemade trailers, specially constructed, reconstructed and replica vehicles, and vehicles whose VIN is missing, changed or altered; New York has a form to request a VIN for a small homemade trailer. A state-assigned number does not come from a manufacturer filing, so a decoder built on NHTSA data has nothing to say about it. The title and the state's records are the authority for those vehicles.

It decoded, but only partly

Sometimes the vehicle is found but many fields are empty. That is not an error. It means the manufacturer did not file those attributes for that VIN, or filed them in a form the database cannot break out. What is returned is still what the manufacturer filed.

It is not a VIN at all

Engine numbers, transmission numbers and other part or serial numbers can look similar and are not interchangeable with a VIN. Motorcycles carry both a VIN and a separate engine number. A vehicle built for a market that does not use the seventeen-character format may carry a shorter chassis or frame number instead. If the number came from anywhere other than the windshield plate or the door-jamb certification label, check that it is the right one; see where to find the VIN.

A quick way to tell which case you have

  1. Not seventeen characters, and the vehicle is 1981 or newer: re-read it from the vehicle.
  2. Not seventeen characters, and the vehicle is older: it predates the standard.
  3. Seventeen characters, check digit fails: assume a typo, and find it on the plate.
  4. Check digit passes, nothing comes back: look at position 1 and the vehicle's history. A foreign-market vehicle, a state-assigned number or an off-road machine is likely.
  5. Check digit passes, make and year come back but no model: a very new model, a small maker, or a thin filing.
  6. Check digit passes and the decode is complete but describes a different vehicle: stop. That is either a transcription error that happens to pass, or a VIN that does not belong to the car; see VIN cloning and fraud.

None of these steps tells you anything about a vehicle's history, title or open recalls. For recalls on one specific vehicle, NHTSA's own VIN lookup is the authority.

Quick answers

Why won't my VIN decode?

Check for a copying mistake first. A VIN must be exactly seventeen characters with no I, O or Q, and most single-character typos make the check digit fail. If both pass and the lookup still comes back empty, the common thread is that no manufacturer filing with NHTSA covers the number.

Why won't a VIN from before 1981 decode?

Because it is not a VIN in the modern sense. Before the 1981 model year, manufacturers used their own identification formats of varying lengths, and a decoder built for the seventeen-character format will not read them. For a classic car, the title, the manufacturer's records and owners' clubs are usually better sources.

Why does my VIN decode with no model listed?

The likely causes are a very new model, a small maker or a thin manufacturer filing. A brand-new model or a mid-year change can return the make, model year and vehicle type but no model for a while, so try again later.

Why won't an imported car's VIN decode?

Because a car built for the European, Japanese or Australian market was never filed with NHTSA, so there is nothing to look up even though its VIN may be real. A failed check digit is also possible on a genuine foreign-market vehicle, since Part 565 is a US rule.

Sources

Try the decoder →