Salary by State: How to Compare Hourly vs. Annual Pay

Start With Hours, Not the Pay Label

A salary is a yearly number. An hourly rate is only a starting point until you know how many hours you will actually be paid for. That is the first decision to make, because a 40-hour schedule and a 28-hour schedule do not belong on the same math sheet.

The fastest baseline is still 2,080 hours a year, which assumes 40 paid hours a week for 52 weeks. Use that number only when the schedule is steady. If the role is seasonal, part-time, or built around rotating shifts, replace 2,080 with the hours you can realistically expect.

A simple conversion looks like this:

• Hourly to annual: hourly rate x paid hours per week x paid weeks per year
• Salary to hourly: annual salary ÷ actual paid hours per year

If overtime is part of the role, keep it separate. Base pay and overtime pay should not be blended into one number before you compare offers.

Use One Comparison Frame

The comparison gets clearer when both offers sit in the same frame. For a steady full-time role, compare annual totals. For a shifting schedule, compare the guaranteed hours first, then add overtime only if it is a normal part of the job.

A $48,000 salary sounds simple, but at 2,080 hours it is roughly $23.08 an hour before taxes and deductions. A $22 hourly role at 40 hours a week is about $45,760 a year before taxes. Those two numbers are close enough that state taxes, overtime, and paid leave can change which offer is actually better.

State Factors That Change the Real Number

Two jobs with the same gross pay can land very differently once the state and local rules are in the picture. The biggest movers are not mysterious. They are the practical costs that come out of the paycheck or the calendar.

• State income tax and local tax affect take-home pay directly.
• Payroll withholding affects how much cash shows up in each check.
• Overtime rules affect whether extra hours are paid separately.
• Remote work location can change which state handles payroll.
• Paid leave affects how much of the year is paid time and how much is not.
• Commute, parking, and travel time matter when one role needs more of them than the other.

The useful habit is to compare the same kind of money on both sides. Gross pay tells you what the employer is promising. Take-home pay tells you what you can spend. If one offer is in a higher-tax state, it may need a stronger base number to keep up with a lower-tax alternative.

When Hourly Pay Usually Comes Out Ahead

Hourly pay tends to work better when the schedule is predictable only in blocks, not in exact totals. It also works better when overtime is real and paid, because every extra hour is part of the deal instead of hidden inside the same salary.

Hourly makes more sense when:

• the schedule changes from week to week
• overtime happens often and is paid properly
• you want extra hours to show up in the paycheck
• the role is part-time, seasonal, or shift-based
• you need a clear floor for the number of hours you will actually work

Hourly is weaker when the schedule is thin or unstable. A role that looks fine at 40 hours can shrink fast if the real week is 30 or 32 hours. That is why a conservative hour count is more useful than a busy-season number.

When Salary Usually Comes Out Ahead

Salary tends to make more sense when the week is steady and the role is built around consistent responsibilities rather than clocked hours. It also helps when benefits and paid leave are strong enough to close part of the gap.

Salary makes more sense when:

• the schedule is stable
• overtime is rare or already built into the role
• paid time off is meaningful
• benefits reduce your out-of-pocket costs
• you want one fixed number instead of a changing paycheck

Salary is weaker when the role quietly runs long. If the job regularly stretches to 45, 50, or more hours without extra pay, the effective hourly rate drops fast. In that case, the headline salary can hide a much smaller real wage.

A Simple Way to Compare Two Offers

Use this 5-step approach whenever you are comparing one hourly offer to one salary offer, or comparing jobs across states.

1. Write down the guaranteed weekly hours for each role.
2. Convert the hourly role to an annual number using realistic paid hours.
3. Convert the salary role to an hourly number by dividing by actual paid hours.
4. Add overtime only where it is truly part of the job.
5. Estimate the take-home difference after state and local taxes, then factor in commute, parking, and unpaid time.

If one role only wins in the busiest month, do not use that month as the baseline. Use the normal month instead. The job that looks weaker at a conservative hour count is the one most likely to disappoint later.

Common Mistakes That Skew the Comparison

A lot of bad pay comparisons come from the same few mistakes.

• Using 2,080 hours for a schedule that is not actually full time
• Counting bonus pay as if it were guaranteed
• Ignoring overtime because the base rate looks simpler
• Comparing gross pay while forgetting state and local taxes
• Leaving out unpaid time off, commute time, or parking costs
• Treating a remote offer as if the employer address were the only location that mattered

The cleanest rule is simple: compare the guaranteed pay first, then add the variable pieces one by one. That keeps the comparison grounded in the money you can actually count on.

A Few Real-World Examples

If you have a $20 hourly job with a true 40-hour week, the annual gross is about $41,600 before taxes. If that same job regularly drops to 30 hours, the gross falls to about $31,200. The hourly rate did not change, but the yearly result did.

If you have a $50,000 salary and a schedule that really runs 50 hours most weeks, your effective hourly rate is lower than the simple 2,080-hour estimate suggests. That is why salary should not be judged only by the annual number when the hours are heavy.

If two offers are close on paper, the smaller details decide more than people expect. A stronger PTO policy, a lower-tax state, or fewer unpaid hours can matter as much as a modest raise.

Quick Answers

How do I turn hourly pay into annual pay?

Multiply the hourly rate by the number of paid hours in a year. If the role is steady full time, 2,080 is the usual starting point. If the schedule is shorter, use the actual paid hours instead.

Should I compare gross pay or take-home pay?

Take-home pay gives the better comparison across states. Gross pay is still useful, but it does not show what taxes and deductions do to the number that lands in your account.

What if the salary job expects long weeks?

Divide the salary by the real weekly hours, not by 2,080 alone. That gives you a more honest hourly figure and makes it easier to compare with an hourly offer.

What if the hourly role has overtime?

Count overtime separately at the rate it is actually paid. If overtime happens often, it can change the outcome a lot. If it is rare, do not let it carry the comparison.

Does remote work change the math?

Yes. Remote pay still runs through a state payroll setup, and the work location can affect withholding and tax treatment. Use the location where the work is performed as part of the comparison.

What if one job is part-time?

Do not use a full-time annual baseline. Compare the actual scheduled hours, then decide whether the smaller schedule still gives you enough income and stability.

Practical Verdict

Use hourly pay as the anchor when the schedule moves around or when overtime is part of the deal. Use salary as the anchor when the hours are stable and the benefits package really adds value. Across states, compare take-home pay, not just headline pay, and use the actual work schedule instead of the best-case version.

The offer that holds up at realistic hours is the better offer. The one that only looks good when every week is perfect is the one most likely to cause regret later.