Salary to Hourly Calculator: Convert Annual Pay to Hourly Rate

I was staring at payroll and my math wouldn’t behave

I was sitting in the office with a coffee that’d gone cold, flipping between a payroll report and a spreadsheet, and the numbers just weren’t lining up. Someone on my team was moving from salary to hourly and I kept getting a different hourly rate every time I changed one tiny assumption. Lunch breaks, paid holidays, 40-hour weeks that aren’t really 40… you know the deal.

So yeah, if you’ve ever tried to convert annual pay to an hourly rate for a real business decision (pricing, hiring, overtime exposure, break-even, all that fun stuff), you’ve probably noticed it’s not one number. It’s a few numbers, depending on what you mean by “hourly.”

And that’s the whole point of this post.

You’re not just doing math. You’re choosing a definition.

If you want the quick tool, here’s the calculator I built for this exact headache:

The two “hourly rates” people mix up (and why it messes up budgets)

I’ve seen folks throw out a number like “that’s about 29 an hour” and then build a whole staffing plan on it, and later they’re wondering why labor percentage crept up and margins got weird. The thing is, there are at least two reasonable ways to convert salary to hourly:

1) Payroll hourly (simple conversion): Salary divided by the hours you assume are worked in a year. This is the one you use for quick comparisons, job offers, or sanity checks.

2) Effective hourly (worked hours): Salary divided by hours actually worked after you back out paid time off (vacation, holidays, paid sick time). This is the one that matters when you’re thinking about output, coverage, and what an hour of that person’s time really “costs” you in scheduling terms.

But then there’s the third thing people quietly mean, which is loaded cost (wages plus payroll taxes, benefits, maybe a laptop, maybe a truck). That’s not “hourly pay,” but it’s absolutely the number you should be using for break-even math.

So. Which one are you trying to get?

Pick your assumptions before you touch the calculator

If you don’t decide these up front, you’ll keep redoing the math and you’ll feel like you’re going crazy (I did). Here are the inputs I ask for when I’m doing this for a hire or a role change:

• Annual salary — the agreed annual amount, not “OTE” or bonus unless you’re intentionally including it.
• Hours per week — usually 40, but plenty of roles are 37.5, 35, or something odd like 45 in busy season.
• Weeks per year — most people use 52, unless you’re modeling seasonal work.
• Paid time off — vacation + paid holidays + paid sick time (if it’s paid, it counts).

And if you’re doing business planning, add one more:

Burden percentage — payroll taxes, benefits, workers’ comp, whatever you carry. I’m not going to pretend there’s one magic percent for every company. I’ve seen it be “barely anything” for a contractor-only setup and I’ve seen it be “wow, that’s a lot” for a benefits-heavy team. Use your real number if you’ve got it, or at least a ballpark you can defend.

That’s the difference between a clean spreadsheet and a fantasy.

The actual math (with a worked example that won’t lie to you)

Here’s the cleanest way to think about it: you’re converting a yearly amount into an hourly amount by dividing by yearly hours. The only debate is what “yearly hours” means.

Let’s use some real-ish numbers so it feels like a decision, not a textbook.

Scenario: You’re hiring an ops coordinator at 62,400 per year. They’re expected to work 40 hours per week. They get 10 paid holidays and 10 vacation days (so 20 paid days off total). That’s 4 work weeks of paid time off, because 20 days ÷ 5 days/week = 4 weeks.

Step 1: Simple payroll hourly

• Annual Hours (simple) = 40 × 52 = 2,080 hours
• Hourly (simple) = 62,400 ÷ 2,080 = 30 per hour

That’s the number most people stop at.

Step 2: Effective hourly based on worked hours

• PTO Weeks = 4
• Annual Hours (worked) = 40 × (52 − 4) = 40 × 48 = 1,920 hours
• Hourly (effective) = 62,400 ÷ 1,920 = 32.5 per hour

Same salary. Two hourly rates. And that 2.5 per hour difference is exactly where coverage and scheduling plans get quietly expensive.

And if you’re thinking like an owner (which you probably are), you’ll immediately ask: “Okay, but what does it cost me once I add burden?” That’s where you can use a loaded rate. If your burden is, say, about 18% (just an example), then your loaded hourly is roughly 32.5 × 1.18 = 38.35 per worked hour. That’s a pricing input, not just a payroll input.

That’s a lot of clarity for five minutes of math!

If you want to run your own numbers without fiddling in Excel, use the embedded tool here:

And if you’re doing the reverse (you’ve got an hourly figure and you’re trying to build a salary offer that won’t wreck your labor model), this one’s the companion: convert hourly to salary.

A quick table I use for sanity checks (because spreadsheets lie when you’re tired)

I keep a little cheat table around for common salaries at a 40-hour, 52-week assumption (2,080 hours). It’s not “the truth,” it’s just a fast sniff test so you can catch a typo before you email an offer letter.

But if your team works 37.5 hours/week, or you’ve got 15 holidays (some companies do), these anchors drift. That’s not a calculator problem, that’s a “define your inputs” problem.

So don’t skip the assumptions.

FAQ (the stuff people email me about after they run the numbers)

If you want to keep it simple, start here:

And yeah, you can do all of this in Excel. I do. But I also know how easy it is to fat-finger a cell and carry the wrong assumption through a whole model (and then you’re explaining it in a meeting like you meant to do that).

Use the calculator, sanity check the inputs, and make the decision with the version of “hourly” you actually mean.