cityparity vs Numbeo: is your cost-of-living number actually right?

By Skyler Bissell · July 8, 2026 · 6 min read

Numbeo is the default. Type in two cities and it hands you a crisp verdict, something like "Amsterdam is 18% cheaper than San Francisco," backed by thousands of prices submitted by people who actually live there. For rent, groceries, a transit pass, and a beer, it's genuinely useful, and this isn't a hit piece.

But if you're pointing that percentage at a job offer, it's quietly answering a different question than the one you're asking. You want to know what you'd keep. Numbeo is telling you what a shopping cart costs.

What Numbeo is genuinely good at

Credit where it's due, because the crowd-sourced model has real strengths. Numbeo's coverage is enormous, its line items are granular (you can drill down to the price of a cappuccino or a one-bedroom in the city center versus the outskirts), and it updates constantly because thousands of contributors keep feeding it. If your question is "roughly how pricey does daily life feel in this city," it answers it well, and no other free tool spans as many places.

The one caveat on its home turf: the data is self-reported, so thin samples in smaller cities can skew a single line. But for a big metro with lots of contributors, the price feel is solid. That's the job it's built for.

The question a price index can't answer

Here's where the tool and the task part ways. A price index compares what a basket of goods costs. It never computes what you keep, because keeping is a function of four things Numbeo doesn't touch:

• Real taxes. Progressive brackets plus payroll on your actual salary rather than a national average. A price index runs none of it.
• Childcare net of subsidy. US daycare for two kids runs $30,000 to $50,000 a year; much of Europe subsidizes it down to a fraction. That single line dwarfs the grocery gap.
• Healthcare you actually pay. A US premium-plus-deductible line against a flat or near-zero one. It rarely shows up in a price basket.
• The cash value of time. Five weeks of statutory vacation and months of paid parental leave are pay you'd otherwise buy back.

We pulled all of these apart, plus expat tax regimes, in what every cost-of-living calculator gets wrong. The short version, aimed at Numbeo specifically: the things it measures well are the small lines, and the things it can't see are the big ones.

Where the verdict flips

Take a family of four weighing Seattle against Oslo. A price index reads Oslo as a touch pricier, a few percent up on the basket, so it nudges you to stay. Now add the two lines it can't see.

Childcare for two kids drops from about $30,000 a year in Seattle to roughly $6,700 in Oslo, where subsidy caps it. A US family's $29,964 in healthcare premiums and out-of-pocket mostly vanishes under Oslo's universal system. That's about $53,000 a year the index never counted. Solve for equal net cash and a $280,000 Seattle household matches on roughly NOK 2,428,740 in Oslo, and it still lands ahead on 11 more paid days off and 37 more weeks of parental leave. The price-index verdict didn't just miss by a little. It had the sign backwards. You can see that comparison line by line on the Seattle vs Oslo family page.

To be fair to Numbeo, it never claimed to answer this. It priced the basket, accurately enough. The mistake is ours if we ask a grocery tool to settle a paycheck question.

Numbeo vs cityparity, at a glance

So which should you use?

Both, for different jobs. Reach for Numbeo when you want a feel for daily prices in a city you're curious about, and it's a good first look. Reach for cityparity when you're holding an offer and need the number that holds up after taxes and the safety net, the equivalent salary that leaves you the same net cash. They aren't really rivals. They're different instruments, and most people reaching for the price index actually wanted the take-home one.

FAQ

Is Numbeo accurate?

For crowd-sourced prices, roughly, within the limits of self-reported data. Rent, groceries, transit, and a coffee are what it does well, though thin samples in smaller cities can skew a line item. It's a different matter for a relocation decision: Numbeo never computes income tax, childcare net of subsidy, healthcare out-of-pocket, or the value of paid leave, which are usually what decide the move.

Does Numbeo include taxes?

No. Numbeo compares prices of goods, services, and rent. It does not run either country's income tax or payroll contributions on your salary, so its percentage says nothing about your take-home. Two cities with a similar cost of living can leave you thousands apart after tax.

What is a better alternative to Numbeo for moving abroad?

For daily prices, Numbeo is fine. For deciding a move, use a tool that computes take-home: real progressive taxes, childcare net of subsidy, and healthcare you actually pay, then solves for the salary that matches your net cash. cityparity does exactly that and shows the line-by-line receipt for each city pair.

Numbeo vs Expatistan: which is better?

They're the same kind of tool: crowd-sourced price indexes that compare a basket of goods and rent. Numbeo has wider coverage and more data points; Expatistan is simpler. Both are useful for a price feel, and both share the same blind spot for a move, since neither computes taxes, childcare after subsidy, or healthcare.

Why does cityparity disagree with Numbeo?

Because they answer different questions. Numbeo compares what a basket of goods costs. cityparity compares what you keep, running each country's real taxes and the costs that change when you move (childcare, healthcare, housing), then matching net cash. When those lines are large, as they are for families, the two tools can point in opposite directions.

Is Numbeo good enough to decide whether to move abroad?

Not on its own. It's a solid gauge of whether daily life feels cheaper or pricier, but it can't see the tax, childcare, and healthcare lines that usually decide a relocation. Use it for the price feel, then run the take-home math before you commit.

Run the take-home number Numbeo can't →

Keep reading: what every cost-of-living calculator gets wrong for the full teardown, the equivalent salary you'd actually need for the method, or browse every city-pair comparison.

cityparity figures come from its per-city engine and were current at publication; currency rates and tax rules move, so treat any single number as a strong estimate and run your own inputs. Numbeo and Expatistan are independent tools, referenced here for comparison only. See the methodology.