Population Within Radius
Set a centre and radius to estimate nearby population. In the United States, MapBench uses 2020 Census ZCTA population and housing totals plus recent ACS demographic context such as income, age, home value, poverty and education. Inclusion is centroid-based and explicitly presented as an approximation, not an exact custom-area Census count. Outside the U.S., the tool falls back to documented major-city data.
By Aryan Khan, Founder & Editor · Updated October 2026
For example, the tool never pretends a circle is uniform: it sums the census areas your circle actually covers, apportioning each tract or block group by the share of its area inside the line.
How to use Population Within Radius
Circles do not respect census boundaries, so the counting method is the tool:
Population Within Radius estimates how many people live inside a circle you draw, by adding up the census areas it covers, each apportioned by its overlap with the circle. Set centre and radius and read the estimate with its method attached — the method decides whether the number deserves trust.
- 1Set the centre point and radius.
- 2Run the population analysis.
- 3Check the active U.S. Census or worldwide fallback mode and read its methodology note.
- 4Treat the output as an estimate and use official small-area analysis for formal decisions.
What people use Population Within Radius for
1. Site and store planning
“How many people live within 3 miles?” is the first question of every site decision. The Cities Within Radius lists the towns; this tool counts the people.
2. Service and clinic catchments
A new facility's realistic service population, estimated from the census areas it actually covers — the number grant applications ask for by name.
3. Campaign and outreach sizing
Canvassing, mail drops and event promotion all size themselves by the circle's population before they size their budgets.
4. Exposure and risk sketches
How many residents sit within a radius of a site is the first-pass exposure question — estimated honestly here, modelled properly by specialists later.
Worked examples
A 2 km circle at a claimed uniform 5,000 people/km² would hold π × 2² × 5,000 ≈ 62,800 people — but real density is never uniform (a park, a river and a tower block share most circles). The tool's tract-by-tract apportionment exists to replace that fantasy number with a defensible one.
A circle centred on a waterfront spends half its area on the harbour — zero residents, half the circle. Apportionment by land-intersecting census areas handles it; naive area maths counts the fish. Manhattan-edge circles are the classic test.
How the estimate is built
Each step, and the honesty it buys.
| Step | Method | Buys you |
|---|---|---|
| Find intersecting areas | Tracts/block groups the circle touches | Real settlement patterns, not uniform paint |
| Apportion each | Population × share of the area's land inside the circle | Partial areas counted partially |
| Sum and report | Total with the census vintage named | A number whose recipe you can repeat |
| Round honestly | Estimates reported as estimates | No false precision to the last person |
Apportionment assumes people spread evenly within each small census area — a good approximation at block-group grain, weaker at tract grain. The figure is an estimate built on the named census, not a headcount.
Population within a radius is now Census-backed in the U.S., but it remains an explicitly labelled geographic estimate
For U.S. locations, MapBench estimates population from Census ZIP Code Tabulation Areas whose Census reference points fall inside the selected circle. That is a substantial improvement over simply adding the populations of a few nearby major cities because suburban and many rural residents are represented through ZCTA population totals. The result also reports housing units and, where recent ACS coverage is available, contextual measures such as household income, median age, home value, poverty and educational attainment.
The tool deliberately does not call this an exact custom-area Census count. A ZCTA can cross the radius boundary, so including or excluding the entire area according to its reference point creates approximation error near the circle edge. The demographic summary is also based on recent ACS estimates for a bounded set of the largest included ZCTAs and displays a coverage percentage. That makes the calculation useful for exploratory market sizing and comparing candidate locations while keeping its limitations visible.
For formal funding, regulatory, epidemiological or policy work, a GIS analyst would normally intersect smaller Census geographies or gridded population data with the exact circle and apply an areal or population-weighted allocation method. MapBench is designed to provide a fast, reproducible first-pass estimate and enough methodological detail for users to know when a more rigorous workflow is required.
How to interpret the result
The most common errors come from using a correct result to answer the wrong geographic question. Keep these points in mind for Population Within Radius:
- State the vintage and definition with every population number you reuse: metro vs municipal vs urban-area figures for the same city differ by multiples, and unstated definitions are how bad comparisons spread.
- Use radius sums as lower bounds in rural regions: curated major-city datasets capture the big dots, not the in-between settlement. For funding or legal work, move to census geometry; for screening and comparison, the transparent estimate wins on speed.
Limits & appropriate use
Population tools live closest to the honesty line, because numbers about people carry rhetorical weight. The curated snapshot used here is labelled with its vintage and definitions, publishes its ingredients for every sum, and positions itself as a lower-bound screen outside dense cores — but it remains an estimate, and metro-vs-municipal-vs-urban definitions can multiply the 'same' city's figure. Cost and density indices add compression error: one rent-inclusive number cannot hold housing policy, healthcare and taxes without losing texture. Ratios survive that compression far better than absolutes, which is why the comparisons lead with them.
The escalation ladder is the product's pride rather than its shame: census bureaus own authoritative counts and blocks; statistical offices own price indices; research firms own rent-normalised granularity. A transparent estimate that screens in seconds and prints its recipe is the right first move for curiosity, comparison and shortlisting — and it says, plainly, where the money-grade answers live when the decision gets serious.
- Funding/legal counts → census bureau tables and geographies.
- Relocation packages → licensed cost-of-living research.
- Site selection → census blocks plus mobility data.
Data & methodology
U.S. mode uses Census ZCTA reference points to determine inclusion, sums 2020 Census population/housing values for included ZCTAs, and adds recent ACS demographic context. This is a centroid-based approximation rather than polygon clipping. Non-U.S. mode uses the documented curated major-city fallback dataset.
For source details, licences and model limitations, see Data Sources and Methodology.
Key terms worth knowing
- Cost index
- Rent-inclusive price level relative to a baseline city (here, NYC = 100).
- Density
- People per unit area; the ratio-stable texture of a city.
Editorial guidance: MapBench explains the method and limitations so the tool can be used as a transparent reference, not as a black-box answer. For legal boundaries, safety-critical routing, surveying, engineering, regulated decisions or official statistics, verify the result with the responsible authority or a qualified professional.
Category: Places & Population. Results are intended for everyday analysis and planning unless a page explicitly states otherwise.
Method, assumptions & limits
- This tool’s method
- U.S. mode uses Census ZCTA reference points to determine inclusion, sums 2020 Census population/housing values for included ZCTAs, and adds recent ACS demographic context. This is a centroid-based approximation rather than polygon clipping. Non-U.S. mode uses the documented curated major-city fallback dataset.
- Before relying on the answer
- Check whether the result counts dataset points, administrative areas or an estimated population footprint. Record the source vintage when provided.
- What the result cannot establish
- Settlement points and area totals do not represent a complete count of residents inside an arbitrary shape. Survey estimates also carry uncertainty.
Coverage: Worldwide. Search, basemap and external data requests may use third-party services; browser-based does not mean every operation is offline. Read the source and licence notes, calculation methodology and privacy policy. If a result looks inconsistent, report a correction with the inputs and mode used.
Frequently asked questions
Clear answers about the calculation, accuracy and appropriate use.
Is the U.S. result an exact Census count inside the circle?
No. ZCTAs are included by their Census reference point/centroid, so returned areas can partly extend outside the circle. The page labels this as an approximation.
Which U.S. population source is used?
The population and housing totals use 2020 Census ZCTA data; recent ACS estimates provide additional demographic context.
What demographic context is available?
Where coverage allows, MapBench summarizes income, age, home value, poverty and bachelor's-or-higher education context for included U.S. ZCTAs.
What happens outside the United States?
The tool falls back to the documented curated major-city dataset, which is useful for broad comparison but does not count every resident or settlement.
What should I use for a formal custom-area population estimate?
Use small-area Census or national statistical geography with GIS intersection/areal interpolation appropriate to the decision.
Which census areas are summed?
The smallest areas with published populations that the data supports — block groups where available, tracts otherwise — each apportioned by its land-area overlap with your circle.
How accurate is the estimate?
Good for planning at neighbourhood scale and better as the radius grows (errors average out). At very small radii the within-area uniformity assumption dominates — read a 500-metre circle's number as a sketch, not a count.
Does it count daytime population?
No — census residence is the basis: people where they live. Workplace and daytime populations are different datasets with different tools and honest labels.
Water and parks inside the circle?
Handled by apportioning on land-intersecting areas where the data separates land — the harbour example on this page is the design case, not an afterthought.
Can I compare two circles?
Run both and compare — the method is identical, so the comparison is fair even where each estimate carries its own error. Overlap between circles, if any, is yours to note.
Business use — site selection finals?
As the demographic first pass, yes. Final site decisions deserve current commercial data and a site visit; the circle estimate narrows twenty candidates to three honestly.
Outside the United States?
The method travels wherever small-area census counts exist; coverage depth varies by country and the tool's data statement names what it holds.
Why not just use density × area?
Because density is not uniform — the uniform-trap example prices the error. Apportionment costs more arithmetic and buys a number you can defend in a meeting.
Related tools and resources
Towns in the circle: Cities Within Radius; ZIPs inside: ZIP Codes Within Radius; density sense: the Population Density Compare.
More free tools
Sources, methodology & editorial trust
- ✓ Browser-first processing where supported
- ✓ External sources are documented
- ✓ No account required for public tools
- ✓ Review data sources
Calculations are documented with their assumptions, limitations and source context rather than presented as unexplained answers.
Reviewed and maintained by Aryan Khan, Founder & Editor of MapBench.
Part of our radius & service area hub
Population Within Radius sits in the radius & service area cluster, alongside 18 other tools that answer neighbouring questions with different methods or datasets.
You may also need
When this answer is only part of the job, these clusters cover the next step.
Read the guide behind this tool
How to Draw a Radius on Google Maps — Google Maps has no radius button. Here are the exact workarounds to draw a radius circle — plus free tools that do it in one click.