Number Of Hours In A Month

Ever stared at a timesheet and wondered whether your brain math was right? You're not alone. The number of hours in a month is one of those things most people think* they know, then second-guess the moment they actually need to write it down.

Here's the short version: it depends on the month. But let's go deeper than that, because depending on why you're asking, the answer changes in a way that actually matters.

What "Hours in a Month" Really Means

When someone asks how many hours are in a month, they're usually asking one of three different questions — and they don't always realize it. There's the calendar math version, the work-hours version, and the billing/payroll version. Each one gives a different number.

The calendar version is the simplest. That gives you the total hours from midnight to midnight, every day, no exceptions. You take the number of days in the month and multiply by 24. Easy.

The work-hours version is what freelancers, salaried employees, and contractors usually mean. How many working* hours are in the month? That depends on your schedule — full-time, part-time, four-day week, weird rotating shifts — and on which days holidays fall.

The billing version is its own thing. But a lot of service businesses quote monthly retainers and need to know how many billable hours a given month contains so they can plan capacity. That usually means working hours, not calendar hours.

So the "right" answer really depends on which version of the question you're asking.

How Many Calendar Hours Are in Each Month

Let's just get the math out of the way, because this is the foundation everything else builds on.

A non-leap year has 8,760 hours total. A leap year has 8,784. Spread across twelve months, you get a moving target:

January — 744
February (non-leap) — 672
February (leap) — 696
March — 744
April — 720
May — 744
June — 720
July — 744
August — 744
September — 720
October — 744
November — 720
December — 744

The pattern is obvious once you see it. On top of that, 31-day months give you 744 hours. February is the odd one out at 672 (or 696 in a leap year). 30-day months give you 720. The total for a non-leap year comes to 8,760, which lines up with the standard figure used in engineering and scientific calculations.

If you just need a rough average to keep in your back pocket, it's about 730 hours per month — which is the number a lot of payroll systems and billing calculators quietly use as a default.

Why February Throws Everyone Off

February is the reason most people get this wrong. It's the only month that changes length based on the year, and its quirks leak into every calculation built around it.

Want a real headache? And try calculating work hours for February in a leap year across a payroll system that assumes 22 working days. Because of that, the math drifts. Some industries — media buying, cloud infrastructure pricing, ad ops — actually publish different rate cards for February because of this. Most people ignore it. The ones who don't tend to bill more accurately.

How to Calculate Working Hours in a Month

This is the part that actually matters for most readers. And it has a few moving parts.

Start with the month's total working days. For a standard Monday-through-Friday schedule in the US:

31-day month: usually 21 or 22 working days
30-day month: usually 20 or 21 working days
February: 19 or 20 working days

The exact count shifts depending on where weekends fall and which federal holidays land in that month.

Then multiply working days by hours per workday. The most common assumption is 8 hours per day, which gives you:

A 22-day month = 176 work hours
A 21-day month = 168 work hours
A 20-day month = 160 work hours

If you work a 7.5-hour day, knock 10–15 hours off the monthly total. If you work compressed four-day weeks at 10 hours each, the total stays similar but the rhythm is totally different.

The Quick Formula

Want a fast mental shortcut? That's it. Most months will land somewhere between 160 and 176 working hours. Practically speaking, take the number of working days in the month and multiply by 8. If you're rounding for a quote or estimate, 160 is a safe floor and 176 is a safe ceiling for full-time US work.

Where People Get the Numbers Wrong

I've seen a lot of mistakes in this area, and most of them come from a few common traps.

Treating every month as identical. They aren't. A 31-day month has 24 more hours than a 30-day one. That might not sound like much, but it adds up across a year — and in client billing, it can be the difference between undercharging and breaking even.

Forgetting about holidays. US federal holidays in a given month can quietly remove 4 to 8 working hours from the calendar. Over a year, that adds up to real money if you're billing hourly or running a salaried team with paid time off.

Using 30 days as a universal default. The "30-day month" is a budgeting and accounting convention. It isn't a calendar fact. It exists to make financial averages easier. If you're using it for any kind of precise planning, you're working with a fiction.

Ignoring leap year entirely. February 29 only shows up once every four years, but if your planning model ignores it, your quarterly comparisons will be off by about 0.3% — annoying if you're dealing with large numbers or tight margins.

Want to learn more? We recommend how many days until december 31 and what time will it be 8 hours from now for further reading.

Practical Uses for This Number

You might need this calculation for a few reasons, and the way you approach it should match the goal.

For Payroll and Salaried Pay

Most US companies pay salaried employees the same amount every month regardless of working days. Even so, if that's you, the monthly hours number is mostly academic. But if you do any kind of hourly overtime calculation, salaried proration, or PTO accrual based on hours worked, you'll want the actual number for that specific month, not an average.

For Freelancers and Consultants

Hourly billing makes the monthly hours number directly relevant to your income. A 22-day work month at 6 billable hours a day gives you 132 billable hours. Also, a 20-day month drops that to 120. If you don't adjust your expectations or pricing between them, your effective hourly rate quietly shifts month to month.

For Project Planning

If you're estimating how long a project will take, working from monthly hours is more useful than thinking in days because it forces you to account for partial effort. They're producing 4 to 6 hours of actual output surrounded by meetings, reviews, and context switching. A senior developer isn't producing 8 hours of code a day. Working in hours keeps that honest.

For Subscriptions and Recurring Costs

SaaS products, cloud services, and utility-style subscriptions often price per hour or per month based on assumed monthly usage. Knowing how many hours are in your billing cycle helps you sanity-check whether a quoted rate is reasonable.

Tools and Quick Methods

You don't need fancy software for this, but a few habits make life easier.

Mental math: Days in the month × 24 = calendar hours. For work hours, count the weekdays and multiply by your daily hours.
Spreadsheet formulas: =DAY(EOMONTH(TODAY(),0))*24 gives you the calendar hours for the current month. For work hours, a NETWORKDAYS formula adjusted for holidays does the trick.
Time tracking apps: Most modern tools (Toggl, Harvest, Clockify, and the like) auto-calculate monthly totals and even break them into billable vs. non-billable buckets. Worth using if you're billing clients by the hour.

If you're a Google Sheets user, the NETWORKDAYS.INTL function is especially handy because it lets you define custom weekends — useful if you're on a Sunday-Thursday work week or a four-day compressed schedule.

Common Questions

How many hours are in a 30-day month?

720 hours. This is the figure most budgeting and accounting tools use as a default, but it's a convention — not a calendar fact for any specific month except April, June, September, and November in a non-leap year.

How many work hours in an average month?

For a standard Monday-

Friday schedule at 8 hours per day with no holidays, the average works out to roughly 174 work hours per month, though this fluctuates based on how weekends align with the calendar and how many holidays fall in a given month.

How many work hours in February during a leap year?

Leap year February has 29 days, typically containing 20 weekdays. At 8 hours per day, that yields 160 work hours — assuming no federal or company holidays land in the month.

How many hours in a year?

8,760 hours in a standard 365-day year, and 8,784 in a leap year. For work hours, most full-time employees log between 2,000 and 2,080 hours annually, depending on holidays and any extra days off.

When the Standard Numbers Break Down

A few situations make the "standard month" framework unreliable.

Compressed workweeks, such as four 10-hour days, shift the math considerably. A 20-weekday month becomes 200 work hours instead of 160, which affects overtime thresholds and PTO accrual alike.

Shift workers and rotational schedules complicate things further because weekends and holidays lose their meaning. A nurse working 12-hour shifts on a rotating pattern might see monthly hours swing from 144 to 180 depending on how shifts fall.

International work cultures add another layer. Countries with strong "right to disconnect" norms, mandated rest periods, or shorter statutory workweeks (France's 35-hour week being the classic example) will produce very different monthly totals even for the same calendar dates.

If you operate across multiple jurisdictions, it pays to anchor calculations in local labor law rather than universal averages.

A Practical Workflow

Here's a simple way to put this into practice without overcomplicating things.

Pull the actual days in the month using DAY(EOMONTH(TODAY(),0)).
Apply NETWORKDAYS.INTL to get the working days, with parameters tuned to your weekend definition.
Multiply by your standard daily hours.
Subtract any holidays that apply to your team or jurisdiction.
Store the result in a reusable cell so you're not recalculating every time.

Once this lives in a spreadsheet or dashboard, you stop second-guessing the number and can focus on the work itself.

Final Thoughts

"How many hours are in a month" sounds like a question with one clean answer, but the reality is layered. Calendar hours, work hours, billable hours, and effective productive hours all tell different stories, and the right one depends on what you're trying to do.

If you're scheduling, planning, billing, or budgeting, taking a few minutes to calculate the actual number for your specific month — rather than defaulting to 720 or 174 — tends to surface insights that averages quietly hide. That said, the number itself isn't the point. The discipline of working it out is.

Once you build the habit, you'll find that monthly planning becomes less about guesswork and more about informed decision-making — which, over the course of a year, adds up to meaningfully better outcomes.