Where to Find a Free ZIP-to-County Crosswalk File

Last year a friend building a sales territory map asked me for "just a simple file that maps ZIP codes to counties." It took me three sources and one unpleasant discovery to realize there is no single perfect version, because ZIP codes and counties were never designed to nest neatly. Some ZIP codes straddle two or three counties. Some are PO-box-only codes that belong to no residential geography at all. Here is what I found, ranked from most authoritative to most convenient.

Why you need a crosswalk at all

ZIP codes are mail delivery routes, not geographic areas. Counties are legal jurisdictions. Businesses constantly need to translate between the two: sales tax territories, demographic analysis, insurance rating territories, service-area mapping, HUD income limit lookups. A crosswalk file is simply a table with one row per ZIP-to-county relationship. If your list has 40,000 ZIPs, the file has at least 40,000 rows, sometimes more where codes span multiple counties.

1. HUD's official USPS crosswalk (most authoritative)

The Department of Housing and Urban Development publishes the canonical crosswalk at huduser.gov, updated every quarter. Download the ZIP-COUNTY file for the most recent quarter and you get an XLSX mapping ZIP codes to counties with residential ratio weights.

2. The open GitHub crosswalk (most convenient)

A researcher at NYU published an open crosswalk combining HUD's ZIP-to-FIPS and ZIP-to-CBSA files with Census county names and OMB metro names. The resulting CSV has clean columns: zipcode, FIPS, CountyName, cbsacode, cbsatitle, and metromicro, and the file is about 2.3 MB. Search GitHub for Crosswalk-ZipCode-County-CBSA and you will find it. I use this one for quick exploratory work because ZIP, county, and metro area arrive in a single table.

3. Missouri Census Data Center Geocorr (most flexible)

For research-grade work, the Geocorr application from the Missouri State Data Center lets you generate custom crosswalks on demand: ZIP/ZCTA to county, county subdivision, census tract, and more, weighted by housing units or population. It is the tool demographers cite when they need something the canned files do not provide. The interface is dated but the output is exact.

4. CMS county-to-ZIP files (healthcare-specific)

The Centers for Medicare and Medicaid Services publish county-zipcode crosswalk data in their qpp-eu-data repository, refreshed for each performance year. If you work in healthcare analytics, this is worth bookmarking, because it reflects the county assignments CMS itself uses.

5. The free starter database on this site (quickest start)

If you need city, state, county, and coordinates for a manageable set of ZIP codes right now, the free CSV here covers 2,000 ZIP codes across all 50 states plus DC and Puerto Rico, with county included. It is a starter file, not a replacement for the full HUD tables, but it is enough to prototype a territory map, a county lookup form, or a classroom project today.

The hard part: ZIP codes that span counties

Here is the unpleasant discovery I mentioned. A crosswalk is not always one row per ZIP. Codes like 90210 sit in one county, but plenty of rural and suburban ZIPs cross county lines. When that happens you have three options, and you should pick consciously:

• Primary county: assign the ZIP to the county holding the majority of its addresses or population. Simple, but you lose precision.
• Weighted rows: keep one row per ZIP-county pair with a weight column. Correct, but downstream analysis gets more complex.
• Centroid assignment: map the ZIP to whichever county contains its geographic center. Easy to compute, arbitrary at the edges.

The HUD file uses residential ratios for exactly this reason. If your use case involves taxes or regulated boundaries, do not shortcut this decision. A delivery address near a county line can legitimately sit in either jurisdiction, and your crosswalk choice determines the answer.

FAQs