Cost of Living by Location Calculator

What would your salary feel like there?

A salary is a number in one city and a lifestyle in another, and the exchange rate between the two is the cost-of-living ratio. Enter your current city, your target city and what you earn; this tool converts purchasing power using rent-inclusive indices anchored to New York = 100, and shows the equivalent salary, the index ratio, the percentage gap and which of the two cities is cheaper — the whole negotiation in four numbers.

The page keeps its promise precise: indices compress housing, groceries, services and rent into one rent-inclusive figure, so the output is directionally excellent and lease-signing insufficient — a screening instrument, printed as such. Currency is deliberately neutral; the ratio is the point, not the unit. That makes it perfect for the real questions: is the abroad offer actually an increase? what number should the transfer conversation start from? which of two remote bases stretches a fixed income further? Pair it with the city comparison for the wider picture and the timezone planner for the call schedule, and the relocation decision has its quantitative spine — free, instant, accountless.

Worked examples

• 500 km around London — captures 10 major cities in the curated dataset — Paris, Brussels, Amsterdam among them — summing to ≈ 17.8 million people, a transparent lower-bound market size.
• Density contrast — Mumbai (~32,000/km²) vs Los Angeles (~3,200/km²) is a clean 10× — ratios like this are the stable part of snapshot data.
• Cost index ratio — Zurich ≈ 118 vs Bengaluru ≈ 23 (NYC = 100) means the same basket costs roughly 5× as much — the ratio, not either absolute, is the trustworthy figure.

People on maps: estimates, vintages and honest numbers

Population tools live on a spectrum from census-exact to clearly-labelled estimate, and the honest move is to say where each number sits. Authoritative counts come from census bureaus and their boundary files — the right source for legal and funding work. Quick comparative work, by contrast, often only needs a transparent estimate: a curated set of major cities with approximate municipal populations and a stated vintage, summed inside your radius with the contributing list published so the total is inspectable rather than asserted.

Density and cost indices carry the same duty. Metro population over built-up area gives people-per-km² figures whose ratios between cities are trustworthy even when absolutes are rough; cost-of-living indices compress housing, groceries and services into one rent-inclusive number anchored to a familiar baseline. Every snapshot ages — vintages should be printed next to the figures, not buried in a footnote.

Used well, these estimates sharpen questions rather than answer them finally: 'which of these three sites reaches more people?', 'what would this salary feel like there?', 'how differently do these two cities live?'. The map makes the comparison spatial, the table makes it concrete, and the CSV export hands it to the next step of your analysis.

Tips & common mistakes

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.

Compare with ratios, not differences: density and cost indices are snapshots, and the relationship between two cities is far more stable than either absolute value. That stability is what makes quick comparisons legitimate.

Using estimates without fooling yourself

Population numbers carry unusual rhetorical weight, which raises the duty of care. The honest spectrum runs from census-exact (legal, funding) to transparent estimate (screening, comparison), and the malpractice lies in the middle: polished numbers with hidden assumptions. A good estimate prints its vintage, its definitions (municipal vs metro vs urban area), and its ingredients — the actual city list behind a radius sum — so a reader can recompute or reject it. That transparency is not a consolation prize; for quick comparative work it is often more trustworthy than a black box with more digits.

Comparisons gain stability when expressed as ratios. Absolute densities and cost indices age and wobble; the relationship between two cities — ten times denser, half as pricey — survives snapshot error. Lead with the ratio, footnote the absolutes, and keep the map in view: spatial context turns '4.7 million' from a statistic into a place, which is where good decisions actually live.

How professionals use this

• Print vintage + definition with every population figure you reuse; unstated definitions are how errors spread.
• Lead comparisons with ratios; they are the stable part of snapshot data.
• Treat curated radius sums as lower bounds outside dense metro cores, and say so when presenting.
• Escalate to census geometry when the decision involves money or law; estimates screen, censuses decide.

Step-by-step masterclass

1. 1. Print the vintage and definition — ≈2020 municipal, metro vs urban area — the label travels with the number or the number shouldn't travel.
2. 2. Inspect the ingredients — A radius sum with its city list shown is an argument; without it, a spell. Read the list before reusing the total.
3. 3. Lead with ratios — Ten times denser, half as pricey — relationships survive snapshot error; absolutes wobble.
4. 4. Keep the map in view — 4.7 million is a statistic; the same number pinned beside its ring is a place, and decisions live in places.
5. 5. Escalate at the money line — Estimates screen, censuses decide; when grants or legal lines depend on it, move to census geometry and say so.

Definitions vary by culture as much as by data: US 'city' populations are legally small (city limits), European figures often mean urban continuum, and Asian megacities blur province-scale — which is why every comparison here states its metro-ish convention and treats cross-cultural absolutes as orientation, not gospel.

Related questions people ask

Quick glossary

Vintage

The year a dataset snapshot describes; always cite it.

Municipal vs metro

City limits vs the wider economic region; populations differ by multiples.

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.

Lower bound

What a major-city sum guarantees: the true population is at least this.

Snapshot

A dataset frozen at a vintage; correct for its date, approximate for yours.

Reading people-numbers like an analyst

Analysts develop a reflex for population figures: before the number, the definition; before the definition, the question. 'City' can mean legal limits, continuous built-up area or metropolitan economy, and the same name carries all three in different documents — which is why serious comparisons state the frame in the first sentence and prefer ratios thereafter. The second reflex is ingredient inspection: any sum should show its addends, because a radius total that hides its city list is rhetoric, not analysis. These habits make even rough snapshots professionally usable: as screens, shortlists and sanity checks, always printed with their vintage, and always paired with the escalation path — census geographies and statistical-office indices — for the moment a decision attaches real money or legal weight to the figure. The same reflexes scale downward to everyday questions. Choosing between two job offers, a warehouse site or a conference hub all reduce to comparable frames and visible ingredients, and the map keeps the exercise spatial rather than abstract. Even the errors are instructive: when a radius sum looks too low for a region, the published city list shows exactly why — the dataset's gaps become legible instead of hidden, and the user learns something real about how population actually distributes. That legibility is the core promise: numbers you can argue with, point by point, are numbers you can trust enough to act on — and knowing precisely when to stop acting on them is the analyst's final skill.

• First sentence rule: frame (metro/municipal/urban) before figure, every time.
• Sums show addends; export the breakdown CSV with any total you publish.
• Two snapshots compared must share a vintage, or the difference is partly calendar.

Honest limits & when to escalate

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.
• Published citations → primary sources with vintages, not snapshots.

Data & methodology note

City populations, densities and cost indices are MapForge's curated ≈2020–2023 snapshot, printed with its vintage and intended for transparent estimation; authoritative US counts live at the Census Bureau.

Category context: Places & Population — Find cities inside a radius and estimate population from curated data. This page is one of the places & population tools on MapForge; the related-tools links below and the header's Tools menu connect every sibling instrument.