Federal, State and Local Minimum Wage: Which One Applies

Three floors, and only one of them binds

The rule is simpler than the map suggests. Federal law sets a floor, states may set a higher one, cities and counties may set higher again, and where more than one applies your employer must pay the highest. There is no conflict to resolve and no hierarchy to work out — the layers are minimums, so the tallest one wins.

What makes this feel complicated is that the layers cover different populations and change on different schedules. A state rate might apply to almost everybody while a city rate applies only inside city limits, and a sectoral rate might apply only to employers of a certain size. The stacking rule is easy; the coverage questions underneath it are where the actual work is.

So the useful habit is to establish each layer separately rather than trying to hold a single number in your head. Federal, then state, then city or county, then any sectoral rate that might reach your industry. Take the highest one that genuinely covers your job and stop.

The federal floor, and how long it has sat there

The federal minimum wage is $7.25 an hour and has been since July 2009, which is now seventeen years without a change. Nothing is currently scheduled to alter it. That single fact explains most of the activity at the state and local level: as the federal floor stayed still through a long stretch of price increases, states and cities filled the gap themselves, and the result is the patchwork you are trying to read.

It also means the federal figure is genuinely the operative rate for very few people nationally. It matters most in the handful of states with no minimum wage law of their own, where federal coverage is doing all of the work by itself. Everywhere else it functions as a backstop that almost never gets reached. That is worth knowing before you use $7.25 as a reference point for anything, because for most workers it describes a floor nobody is standing on.

The two odd cases worth knowing

Five states have no state minimum wage law at all: Alabama, Louisiana, Mississippi, South Carolina and Tennessee. Covered employees there fall back on the federal $7.25. That is not the same as having no protection, and the distinction matters — it means the protection comes entirely from federal law, so anybody federal law does not reach has nothing beneath them. In a state with its own statute, a gap in federal coverage is often filled; in these five it is not.

Then there are two states, Georgia and Wyoming, whose own statutes still set $5.15. Those figures are below the federal rate and are overridden by it for any employee federal law reaches, so the practical answer in both places is $7.25 for most people. It is a good illustration of the stacking rule: a lower state figure does not reduce anything, it simply never becomes the operative number.

Location, not headquarters

The rate follows where the work is physically performed rather than where the company keeps its head office. A company headquartered in a low-wage state pays the higher local rate for employees working in a city that sets one. The reverse holds just as firmly: being employed by a company in an expensive city does not entitle somebody working elsewhere to that city’s rate. Employers get this wrong in both directions, and the second direction produces the more disappointing conversation.

For remote work this becomes a question about where you are sitting when you do the job, which is exactly the principle that governs pay transparency coverage and state tax withholding as well. If you work from home in a county with its own ordinance, that ordinance is in your stack even if your employer has never heard of the county. Small employers hiring their first remote worker frequently have no idea this is true, which is a reason to raise it rather than a reason to assume bad faith.

Employees who move between locations during a single shift can be covered by different rates in different parts of the same day. Delivery drivers, home care workers and field service staff all run into this routinely. Where it happens the usual approach is to apply the rate for the hours worked in each jurisdiction, tracked separately. It is a genuine compliance headache rather than an exotic edge case, and it is one of the places where a timekeeping system that has no field for location quietly produces underpayment.

The federal contractor rate is no longer what it was

For several years, employees working on federal contracts were entitled to a substantially higher minimum wage, set by executive order rather than by statute. That distinction turned out to matter a great deal. The order was revoked in March 2025, the Department of Labor stopped enforcing it, and the implementing regulations were set for rescission. An entitlement resting on an executive order can disappear in a way a statutory one cannot.

The consequence is narrow and real. If you work on a federal contract and were relying on that rate, the ordinary stack described above is now the whole picture for you. Guidance published before 2025 still describes the contractor rate as though it applies, and that guidance remains online, confidently written and well ranked in search results. This is a recurring hazard across this whole subject: nothing marks a page as superseded.

Sectoral rates sit on top of all of this

A growing number of jurisdictions set rates for particular industries rather than for everybody. California’s fast food rate of $20.00 an hour, applying to chains of sixty or more locations, is the best known example. These behave like any other layer — if one covers your job, it enters the stack and the highest applicable figure still wins.

The complication with sectoral rates is never the number and almost always the coverage. Whether a franchise counts by brand or by individual owner, whether a particular role inside a covered business is included, and how a chain-size threshold is actually measured are all questions with real answers that are easy to get wrong. A single franchisee with three locations may be covered because the brand has hundreds. That is the sort of detail worth confirming rather than assuming in either direction.

How to establish your own number

Work up the stack in order. Start with the federal $7.25 as a floor that always exists. Check your state’s rate on the state labor department’s own page rather than a summary. Then search your city and county by name for a minimum wage ordinance, because this is the layer most often missed and the one most likely to be highest. Finally consider whether any sectoral rate reaches your industry.

The whole exercise takes about ten minutes and produces a figure you can check a payslip against. If the hourly number on your stub falls below what the stack produces, you have a specific and checkable problem rather than a suspicion. What to do about it is covered separately in this section, and the first step is simply writing down what you found and when.

This is general information about how the layers fit together rather than legal advice about your pay. Roughly eighty-eight jurisdictions changed a rate during 2026 alone, so any figure quoted in an article has a short shelf life — your state labor agency has the current one and will answer a question without any obligation to file anything.