Can Your Employer Really Cut Your Pay if You Move to a Lower Cost City?

By The Penny Plan Editorial Team Published July 13, 2026 7 min read

A remote role finally makes a move to a cheaper city possible, but then someone mentions that the company adjusts pay based on where an employee lives, and suddenly the math behind the move feels a lot less certain.

The short answer

Yes, employers can generally reduce pay when an employee relocates to a lower cost-of-living area, as long as the new pay doesn’t fall below any applicable minimum wage and no contract, offer letter, or union agreement says otherwise. This is usually called geographic or location-based pay, and it isn’t standardized across companies. Whether an adjustment happens, how large it is, and how it’s calculated all depend entirely on the individual employer’s policy.

Why location-based pay exists

Some companies set compensation using regional pay bands, meaning a given role has a different salary range depending on the local labor market and cost of living tied to where the employee is based. The reasoning is usually framed around paying competitively for the local market rather than tracking cost of living directly, even though the two often move together. Other companies pay one national rate for a role regardless of location, which means a move wouldn’t trigger any change at all. Because there’s no universal standard, two people in similar remote jobs at different companies can have completely different experiences after the same kind of move.

How the adjustment usually gets calculated

Companies that do adjust pay by location typically use a compensation index or data from a cost-of-living or labor-market research service, comparing the new location to the original one or to a baseline city. This isn’t the same as a simple cost-of-living calculation, since it usually reflects local salary norms for that role rather than the price of groceries or rent specifically, though the two are related. Some employers apply the adjustment immediately upon a confirmed move, while others review compensation on a set schedule, like an annual cycle, which can create a lag between the move and any change to pay. Because a cost-of-living calculator doesn’t always map cleanly onto how a company sets pay, running personal numbers ahead of time is worth doing separately from whatever the employer’s own policy produces.

What to check before assuming a cut is coming

Weighing the move itself

A potential pay cut doesn’t automatically cancel out the benefit of a cheaper city, since lower housing costs, taxes, or other expenses can offset a reduced salary, sometimes by a wide margin. The relevant comparison is take-home pay after any adjustment against the actual cost of living in the new location, not the original salary against the sticker price of a new city. This is part of a broader set of tradeoffs that come up whenever someone is weighing a cheaper city against other priorities like job prospects, and it’s worth running the numbers before treating either the move or the pay policy as a settled outcome. Keeping some savings in reserve, similar to the reasoning behind maintaining an emergency fund, can also help absorb any gap between when a lease ends in one place and pay adjusts in the other.

The bottom line

Whether a move triggers a pay cut comes down entirely to a specific employer’s compensation policy, which can range from no adjustment at all to a formula-driven reduction tied to a regional pay band. Getting a clear, written answer from the employer before finalizing a move removes the guesswork and lets the actual numbers, rather than assumptions, guide the decision.