How Much Hours Are In A Month

How many hours are actually in a month? It's a question that sounds almost too simple to ask. And then you start thinking about it — work hours, billable hours, sleep hours, the hours you lose to scrolling — and the "simple" math gets weird fast.

Here's the thing: the answer depends on what you're counting. On top of that, a calendar month isn't a fixed number of hours. So if you've ever looked at a timesheet, payroll report, or project estimate and felt like the numbers didn't quite line up, that's why. It drifts between 28 and 31 days, which means the total hours per month shifts with it. Let's break it down properly.

How Many Hours in a Month (The Actual Math)

A standard month contains anywhere from 672 to 744 hours. That's the range you get when you multiply the number of days in a month (28, 29, 30, or 31) by 24.

Here's the breakdown:

• 28 days = 672 hours
• 29 days = 696 hours
• 30 days = 720 hours
• 31 days = 744 hours

February is the obvious wild card, swinging between 672 and 696 hours depending on whether it's a leap year. Every other month is more predictable — eight months of the year give you 720 or 744 hours, and only February does something different.

If you need a single average number for planning purposes, most people use 730 hours per month. That's the figure that shows up in payroll systems, freelancer contracts, and business utilities because it's the average across the full year (8,760 hours ÷ 12 months). It splits the difference between 720 and 744 and works well as a default when the exact month doesn't matter.

Why the Exact Number Matters

So who actually cares whether a month has 720 or 744 hours? More people than you'd think.

For salaried workers

If you're paid a fixed annual salary, your employer has already divided your yearly pay into 12 monthly installments, often using 2,080 work hours per year as the baseline (that's 40 hours × 52 weeks). But when they prorate — for someone starting mid-month, for example — the 730-hour average gets used as the dividing line. Knowing this helps you sanity-check your paystub.

For freelancers and contractors

At its core, where it really bites. If you charge an hourly rate, the difference between 720 and 744 hours a month isn't huge in raw terms, but over a year it adds up. On top of that, billing against a 730-hour month instead of the actual month you're working in can quietly cost you or your client a chunk of money. Some freelancers use a clean 720 to keep invoices tidy. Others go month-by-month. Both approaches work — just be consistent.

For project planning

Ever had a project that "should" take 200 hours and watched it spill over? Part of the problem might be that you estimated against an average month without checking the calendar. A 31-day month gives you more raw hours than a 28-day February, and if your deadline falls in a short month, the math changes.

The Work Hours Question

Here's where most people actually land when they ask this question. They don't want to know how many hours exist in a month. They want to know how many workable* hours are in one.

Let's assume a standard 40-hour workweek. And over a full year, that comes to 2,080 hours, and dividing by 12 gives you roughly 173 work hours per month as a flat average. But that's before you subtract weekends, holidays, and vacation.

A more realistic monthly work-hour count looks like this:

• Take the days in the month
• Subtract weekends (usually 8 to 10 days)
• Subtract any public holidays (varies by country, but typically 0–2 in a given month)
• Multiply the remaining workdays by 8

For a 30-day month with no holidays, you get roughly 22 workdays, or about 176 work hours. For February, you're looking at 20 workdays, or 160 hours, give or take.

We're talking about the number most people should actually be planning around. Think about it: the "730 hours in a month" figure is a calendar fact. The "173 work hours" figure is what fits on a timesheet.

Want to learn more? We recommend how many shots to get tipsy calculator and what is 1 4 of 2 3 for further reading.

Common Mistakes People Make With Monthly Hour Calculations

A few traps to watch out for.

Mixing calendar hours with work hours

Saying "there are 730 hours in a month" when you really mean "there are 173 work hours" is a surprisingly common mix-up. They answer different questions. Be clear about which one you need.

Forgetting leap years

February has 672 hours in three out of every four years, and 696 in the fourth. If you're calculating annual figures that include February — for billing, for project burn-down, for anything that adds up over the year — that one extra day (24 hours) matters.

Using 30 days for everything

It's tempting to round every month to 30 days for easy math. But four months a year have 31 days, and the difference between 30 and 31 days is 24 hours — a full working day. If precision matters, count the actual days.

Ignoring partial months

A month with 744 hours and a month you actually worked for 15 days are not the same. Prorated calculations need the actual start and end dates, not a convenient average.

Practical Tips for Hour-Based Planning

Some things that actually help when you're working with monthly hour figures.

Use 730 as a default, but adjust when it counts. The 730-hour monthly average is a fine baseline for rough estimates. When the number feeds into a contract, invoice, or salary calculation, switch to the actual month's day count.

Track by week, not by month. If you're managing time on a project, weekly tracking (40 hours, 35 hours, whatever your capacity) tends to be more accurate than monthly. Months are uneven. Weeks are uniform. Build your plans from weeks up.

For payroll, check what divisor your employer uses. Some use 2,080 yearly hours, some use 2,080 ÷ 12 = 173.33 per month, and some use a different figure for exempt employees. Knowing which one your pay is based on helps you spot errors.

For freelancers, pick a standard and document it. Here's the thing — if you bill monthly, decide whether you're using actual hours or an average. Because of that, put it in your contract. Clients appreciate not getting surprised by a different number every month.

FAQ

How many hours are in a 30-day month?

720 hours. That's 30 × 24.

How many hours are in a 31-day month?

744 hours. Seven months of the year have 31 days: January, March, May, July, August, October, and December.

How many work hours are in an average month?

Roughly 173 work hours, based on a 40-hour workweek averaged across 12 months. In practice, after weekends and holidays, most months fall between 160 and 184 work hours.

How many hours in February?

672 in a non-leap year, 696 in a leap year. So 2024 was a leap year. 2028 will be the next one.

How many hours are in a year?

8,760 hours in a standard 365-day year, 8,784 in a leap year. Most business calculations use 2,080 as the working-hour equivalent (40 hours × 52 weeks).

A Quick Way to Estimate

If you just need a ballpark without reaching for a calculator, remember this: every month is roughly 720 hours, give or take 24. Work hours come out to about 20% of that — somewhere around 160, depending on weekends and holidays. That's not a number to put in a contract, but it's a solid gut check when someone throws a figure at you and you want to know if it makes sense.

Most of the confusion around this topic comes from mixing levels. Also, there are hours in a month, and then there are workable* hours in a month, and then there's the version your payroll system actually uses. Still, they're all related, but they're not interchangeable. Once you know which one you need, the rest is just multiplication.