Use land area for conventional population density, match the population and boundary vintages, and divide combined population by combined land instead of averaging county densities.
Population density looks like a simple division: people divided by area. The difficult part is deciding which people and which area belong together. A correct division can still produce a misleading statistic if the population describes one geography while the denominator describes another.
The examples below combine the Census Bureau’s Vintage 2025 population estimates with the 2026 Gazetteer land areas used throughout this site, joined by GEOID. They are the same figures shown on each county profile, so you can check every calculation there or in the download.
Why the conventional denominator is land
The Census Bureau describes U.S. population density as people per square mile of land area. Water is not included in that conventional denominator. A total-area density is mathematically possible, but it needs an explicit label and should not be compared directly with a land-area density. See the Census explanation.
The distinction can be modest in a county with little water and substantial in one with a large water allocation. It changes the resulting number even when the population is held perfectly constant. Before interpreting a difference between two sources as population growth or crowding, check whether one denominator includes water. A measurement definition can create an apparent demographic difference.
Same population, two denominators
Cook County, Illinois, had an estimated 5,194,625 residents on July 1, 2025. Its 2026 measurements are 944.93 square miles of land and 1,634.64 square miles in total, because the county includes part of Lake Michigan.
| Calculation | Result |
|---|---|
| 5,194,625 ÷ 944.93 land mi² | 5,497 people / land mi² |
| 5,194,625 ÷ 1,634.64 total mi² | 3,178 people / total mi² |
The total-area result is 42.2% lower than the land-area result. That reduction equals the water share: replacing land with land plus water enlarges the denominator without adding a single resident. Two sources reporting these two numbers would both be arithmetically right, and a reader comparing them could mistake a definition change for a demographic one.
A matching name is not enough for a valid join
Use a county GEOID, preserve it as text, and check the geographic vintage of the population source. A table published recently may describe older boundaries. Likewise, an unchanged name does not by itself prove that the represented area stayed the same. The Gazetteer notes that releases can differ in entities, names, and boundaries.
Connecticut illustrates the issue: a historical county record cannot be relabeled as a current planning region and treated as the same area. Inspect the source’s geography rather than matching the nearest-looking label. If the boundaries differ, use compatible data or a documented geographic correspondence method. A perfect five-digit match is a useful check, but you still need the source’s boundary date before combining years.
Do not take the simple average of county densities
Cook County and its neighbor Will County show why. Cook has 5,497 people per square mile of land; Will has 852. The simple average of those two densities is 3,175. But together the two counties have 5,906,878 residents on 1,780.8 square miles of land: 3,317 people per square mile.
The simple average gives each county equal weight regardless of its area, so it overstates the density of a region where the smaller county is the denser one. For the density of the combined region, sum the populations and divide by the sum of land areas. Equivalently, weight each county density by its land area. The same rule applies to a metropolitan comparison, a group of neighboring counties, or a state, and to other ratios, not just population density. State pages on this site calculate state density this way.
A county average does not describe every neighborhood
Even a carefully calculated density compresses a spatial pattern into one number. A county can contain a concentrated settlement and extensive sparsely populated land. Another can distribute the same population more evenly across the same total land area. Their county densities would be identical, despite a very different experience on the ground.
Use smaller-area population data if your question concerns neighborhoods or the distribution of settlement. Do not infer travel times, congestion, building height, or available housing from county density alone. It can be a useful summary for a stated boundary and date; it becomes misleading when used as a stand-in for every local condition within that boundary.
What to include next to a density result
Document the population source, reference date or period, geographic identifier, area source and vintage, units, and rounding. Say whether the population is a count or an estimate. If the population source provides uncertainty measures, preserve those rather than implying that a precise-looking quotient is exact. County population estimates are revised every year, so cite the vintage, not just the year being described.
Keep unrounded values for the calculation and round the final display once. For square kilometers, divide people by land square miles multiplied by 2.58998811. Label the result in people per square kilometer, not square miles. The data dictionary identifies the area fields, and the spreadsheet workflow explains the identifier and import checks that make a later join reliable.
Sources and calculation notes
County examples and calculations use our pinned 2026 Census Gazetteer dataset. Ratios use published square-mile values; land rankings use original square meters. Population figures are Census Bureau Vintage 2025 estimates, joined by GEOID; examples labeled hypothetical are teaching examples.
- Original 2026 Census county measurements (ZIP)
- U.S. Census Bureau: understanding population density
- U.S. Census Bureau: Vintage 2025 county population estimates (CSV)
- U.S. Census Bureau: Gazetteer files, coverage, and vintage notes
- U.S. Census Bureau: understanding geographic identifiers
How we calculate and verify the data · Download and reproduce the examples · Suggest a correction