What's Your Real Hourly Rate on a Salary?

A salary sounds like a fixed number, but it’s actually hiding a rate per hour, one that depends entirely on how many hours you put in to earn it. Most people size up a salary against the standard 40-hour week, but if your actual hours run higher than that, and for a lot of salaried roles they do, your real hourly rate is lower than the sticker number suggests.

The core concept

An annual salary is really a payment for a year’s worth of work, not for a fixed number of hours. When you divide that salary by hours per week and weeks worked per year, you get an hourly rate, but that rate only holds up if you actually work the hours you divided by. Bump the hours up (a 45-hour week instead of 40, say) without any change in pay, and the same salary now covers more work. The dollar amount per hour has to fall, even though your paycheck looks identical.

This matters most when comparing offers. A salaried role and an hourly role can advertise similar-sounding pay, but if the salaried job routinely runs 50-hour weeks and the hourly job caps at 40, the hourly job’s advertised rate is closer to what you’ll actually earn per hour worked. It also matters when you’re deciding whether to leave a salaried job for freelance or contract work: a client rate that looks lower on paper can still beat your current effective rate once you account for the extra, unpaid hours the salaried job quietly assumes.

The formula

Weekly Pay  = Annual Salary ÷ Weeks Worked Per Year
Hourly Rate = Weekly Pay ÷ Hours Per Week

Weeks worked per year defaults to 52, but you can lower it if you take unpaid time off (for example, 50 weeks for two unpaid weeks). Hours per week is the field that matters most for this article’s point: it should reflect the hours you actually work, not just the hours your offer letter mentions.

Worked examples

Take a $60,000 annual salary at a standard 40-hour week, 52 weeks worked:

• Weekly pay: $60,000 ÷ 52 = $1,153.85
• Hourly rate: $1,153.85 ÷ 40 = $28.85/hour

Now a smaller salary with a shorter standard week, $45,000 a year at 37.5 hours a week, 52 weeks worked:

• Weekly pay: $45,000 ÷ 52 = $865.38
• Hourly rate: $865.38 ÷ 37.5 = $23.08/hour

Notice the second example pays less overall but has a higher rate per hour than you might guess, since it assumes fewer hours per week. The hours you divide by change the answer just as much as the salary itself does.

The hours trap

Here’s where the gap between advertised and real hourly rate shows up. Go back to the first example: $60,000 a year, weekly pay of $1,153.85. That number assumes a 40-hour week. But if your actual average is 50 hours a week, the same weekly paycheck now has to stretch across more hours:

• Hourly rate at 50 hours: $1,153.85 ÷ 50 = $23.08/hour

That’s nearly $5.77 less per hour than the 40-hour version, and your paycheck hasn’t changed at all. Salaried jobs rarely adjust pay upward when hours creep past the standard week the way hourly overtime does, so the extra hours simply dilute the rate you’re actually being paid. If you regularly work evenings, weekends, or “just finish this one thing” hours that never make it onto a timesheet, your true effective rate is quietly lower than whatever number you calculated using a tidy 40-hour assumption.

A second caveat worth flagging: this calculation covers base salary only. It doesn’t count health insurance, retirement matching, paid time off, or other benefits, and it doesn’t subtract taxes. Those benefits add real value, and taxes reduce what actually lands in your account, but neither belongs in an hourly-rate comparison meant to measure cash pay per hour worked. If you’re weighing a salaried offer against an hourly one, or against freelance and contract work, it’s worth running the numbers with your realistic hours, not the hours listed in the job posting, and treating benefits as a separate line item rather than folding them into the rate.

It’s also worth redoing the math every year or two, not just when you first take the job. Responsibilities tend to expand quietly, meetings multiply, and the “extra hour or two here and there” you accepted at the start can drift into a much longer week without any single moment where it felt like a change worth pushing back on. Revisiting the calculation periodically, using your current actual hours rather than the hours you agreed to on day one, keeps the number honest.

FAQ

Why is my effective hourly rate lower than I expected? Most likely because you’re working more hours than the number you used to calculate it. Salaried roles often run past 40 hours a week in practice, and unlike hourly overtime, that extra time usually isn’t paid at a premium, or paid separately at all. Plug in your real average hours per week instead of a round number, and the gap usually explains itself.

Should I include bonuses or benefits when figuring my hourly rate? Not if you’re trying to compare cash wages per hour worked. Bonuses are often variable or discretionary, and benefits like health insurance or a 401(k) match have real value but aren’t wages you can spend the same way. Keeping the calculation to base salary and actual hours gives you a cleaner, more comparable number; you can weigh benefits separately afterward.

How do I estimate my actual hours per week if they vary? Track a few representative weeks, including any work that happens outside your official schedule, like answering emails at night or coming in early, and average them. Even a rough estimate based on a typical month beats using the “standard” number from your offer letter, since that number is exactly what tends to understate how much time the job actually takes.

Use the Salary to Hourly Calculator to run your own numbers.