If you've ever logged hours on a timesheet, tracked a freelance project, or planned a sprint, you've probably had to answer a question that sounds simple but isn't: "how many days is that, really?" The honest answer depends on what kind of day you mean. This calculator handles both, and this page explains why the distinction matters more than it looks.
How to Convert Hours to Working Days
Divide your total hours by your workday length (8 hours by default) to get working days. For example, 40 hours ÷ 8 = 5 working days. Adjust "Hours Per Working Day" above if your organization uses a different shift length. For elapsed time rather than work hours, use the plain 24-hour conversion shown below the result.
Working Days vs. Calendar Days — Why It Matters
These two conversions answer completely different questions, and mixing them up is the single most common mistake people make with hours-based math.
Working days asks: "if I'm putting in 8-hour shifts, how many shifts does this add up to?" It's the right conversion for timesheets, freelance invoicing, project estimates, and anything tied to a working schedule. A task quoted at "16 hours" on an 8-hour-a-day schedule takes 2 working days — but that's 2 business days, which could span a full calendar week if a weekend falls in between.
Calendar days asks: "how much clock time has actually passed?" It's the right conversion for elapsed-time questions — a flight delay, a server outage, a fasting window, a rental period. 72 hours is always exactly 3 calendar days, day or night, weekday or weekend, because a calendar day is a fixed 24-hour block regardless of anyone's work schedule.
Quick Reference Table
| Hours | Working Days (8 hr/day) | Calendar Days (24 hr/day) |
|---|---|---|
| 8 | 1.0 | 0.33 |
| 24 | 3.0 | 1.0 |
| 40 | 5.0 | 1.67 |
| 80 | 10.0 | 3.33 |
| 160 | 20.0 | 6.67 |
Notice how far apart the two columns get as the hours grow — 160 hours is exactly 20 working days on a standard 8-hour schedule (a full working month), but only 6.67 calendar days if you were counting non-stop elapsed time. Same number of hours, two very different real-world answers.
Practical Examples
Freelance invoicing: You logged 37.5 hours on a project this week at 7.5-hour working days. Set "Hours Per Working Day" to 7.5, and 37.5 hours converts to exactly 5.0 working days — useful when a client asks for a day-rate breakdown instead of a raw hour count.
Project estimation: A task is scoped at 120 hours of effort. On an 8-hour day, that's 15 working days — but remember, working days aren't the same as calendar days once weekends are involved. Pair this with the Working Days Calculator to translate 15 working days into an actual calendar deadline.
PTO / leave balance: Your leave balance shows 56 hours remaining and your standard day is 8 hours. That's 7 full days off — handy for quickly sanity-checking an HR portal's hour-based balance against actual days you can take off.
Common Mistakes
- Using 24-hour conversion for work hours. If a client says a task will take "80 hours," they almost always mean 80 working hours (10 working days at 8 hrs/day) — not 3.3 calendar days. Using the wrong conversion here understates the real timeline by a wide margin.
- Assuming every workplace uses 8-hour days. Many industries run 7, 7.5, 9, or even 10-hour shifts. Always confirm the actual shift length before converting — this calculator's editable "Hours Per Working Day" field exists specifically for this.
- Forgetting that working days ≠ calendar days. "5 working days" from a Wednesday doesn't land on the following Monday if there's a public holiday in between — for that kind of date-accurate answer, use the Working Days Calculator instead of a pure hours conversion.
Frequently Asked Questions
How many working days is X hours?
Divide the number of hours by your workday length. At 8 hours/day: 40 hours = 5 working days, 30 hours = 3.75 working days, 100 hours = 12.5 working days.
Can I change the hours-per-day assumption?
Yes — edit the "Hours Per Working Day" field above to match your organization's shift length (e.g. 7, 8, or 9 hours). The result updates instantly.
What's the difference between working days and calendar days here?
Working days divide your hours by a workday length (default 8) — useful for timesheets and project estimates. Calendar days divide by 24 — useful when you're converting pure elapsed time, like "how many days is 72 hours."
Does this account for weekends or holidays?
No — this is a pure hours-to-days unit conversion, not a calendar-date calculation. It doesn't know which calendar dates your hours fall on. If you need to know an actual finish date accounting for weekends and holidays, use the Working Days Calculator instead, which works from real start/end dates.
Why is 160 hours not exactly 4 weeks?
160 hours at 8 hours/day is exactly 20 working days, which is 4 working weeks (5 working days per week) — but only if none of those days were skipped for weekends or holidays. It is not the same as "4 calendar weeks" (28 calendar days), which would be 672 hours if every hour counted.
How many working days is a typical full-time month?
At 8 hours/day, a common full-time monthly hour bank of 160-176 hours converts to 20-22 working days — the exact figure depends on how many weekdays the calendar month actually contains, which varies month to month.
Can I use decimal hours, like 7.5 or 37.25?
Yes — both the total hours and hours-per-day fields accept decimals, which is useful for organizations that track time in quarter-hour or half-hour increments rather than whole numbers.
Is this the same as a business-days-between-dates calculation?
No. This tool converts a raw hour count into an equivalent number of working days using a fixed hours-per-day assumption. If you instead want to know how many working days fall between two specific calendar dates, accounting for weekends and public holidays, use the Working Days Calculator.