Article — Hours to Weeks Converter
Hours to weeks conversion: the exact 168-hour week
One week contains exactly 168 hours — 7 days multiplied by 24 hours per day. The factor is a calendar definition, not a measurement, and it never rounds. To convert hours to weeks, divide by 168. To go the other direction, multiply weeks by 168. For 40-hour work weeks (the US/UK full-time standard), divide hours by 40 instead.
The calculator above handles both directions instantly with quick picks for the hour counts that come up most: 24 (one day), 40 (a work week), 168 (one calendar week), 720 (about one month), and longer project spans. This article covers the math, the difference between calendar weeks and work weeks, and the surprising history behind the 40-hour work week.
How many hours are in a week?
A calendar week contains exactly 168 hours. The number falls out of two definitions: a week is 7 days long, and a day is 24 hours long. Both conventions trace to ancient Babylonian and Egyptian astronomy, were standardised by the Romans, and survive in the modern Gregorian calendar.
The 168-hour week is not a US convention; it is universal. Every country that uses the Gregorian calendar uses the same 7-day, 168-hour week. The ISO 8601 standard codifies it, with Monday as day 1 of the week and Sunday as day 7. The US convention starting the week on Sunday is a calendar-display difference, not a count difference: the week still contains 168 hours either way.
The Soviet Union experimented with a 5-day continuous week from 1929 to 1931 and a 6-day week from 1931 to 1940 in an effort to keep factories running without weekend shutdowns. The continuous week assigned workers to staggered "colour days" off, so production never stopped. The experiment failed because family members ended up with different days off. The standard 7-day, 168-hour week returned in 1940.
Converting hours to weeks step by step
The conversion is one division. For calendar weeks: hours ÷ 168. For work weeks at the FLSA 40-hour standard: hours ÷ 40. Always state which one you mean — the difference is over 4×.
h → calendar weeks h / 168h → 40-hour work weeks h / 40weeks → h (calendar) weeks × 168weeks → h (work) weeks × 40h → months h / 730.5For a worked example, take a 500-hour project. Calendar weeks: 500 ÷ 168 = 2.976 calendar weeks (about 2 weeks 6 days 14 hours of continuous time). Work weeks: 500 ÷ 40 = 12.5 work weeks (twelve and a half 40-hour weeks of staff time). The two numbers differ by a factor of 4.2 = 168 / 40.
Calendar week vs. work week
Calendar weeks measure elapsed time. Work weeks measure paid labour. Confusing the two is one of the most common errors in project estimating and HR budgeting.
A 1,000-hour software project takes 5.95 calendar weeks of elapsed time but represents 25 work weeks of engineer effort. If you have five engineers working full-time, the project ships in 1.19 calendar weeks; with one engineer, it takes 25 calendar weeks (six months). Always ask: are we talking elapsed time or person-hours?
A common estimating mistake: "We need 1,000 hours, so it takes about 6 weeks". That is only true if you have one full-time person dedicated to the project. With shared resources, 1,000 hours can take three months of elapsed time. Always specify person-hours per calendar week.
Hours to weeks in payroll
US payroll runs on a 2,080-hour work year: 40 hours per week × 52 weeks. That is the FLSA convention for full-time salaried employees. Hourly workers are paid by actual hours worked; overtime kicks in at 40 hours per week (or 8 hours per day in some states).
The 2,080 hour year is a simplification. Calendar years actually contain 8,766 hours (365.25 days × 24). The work year is 23.7% of total calendar time; the remaining 76.3% is sleep, weekends, evenings, and holidays. Many salaried professionals work more than 2,080 hours per year — the FLSA defines minimum coverage, not maximum effort.
For PTO conversion, use the 8-hours-per-day convention: 120 hours of PTO = 15 days = 3 work weeks. The 168-hour calendar-week factor is wrong here because no employer compensates employees for vacation hours during sleep. Always use 40 (work week) or 8 (work day) for PTO math.
Hours to weeks in project planning
Software, consulting, and construction projects all estimate in hours and report in weeks. The conversion depends on the staffing model:
- Single-resource project — hours ÷ 40 = calendar weeks
- Half-time allocation — hours ÷ 20 = calendar weeks
- Team of 5 full-time — hours ÷ 200 = calendar weeks
- 10,000-hour rule (Gladwell) — 250 work weeks (5 years full-time) to reach expertise
- 2,080-hour year — standard FLSA full-time year (40 h × 52 weeks)
- 8,766-hour year — calendar year (365.25 days × 24 hours)
Software teams using two-week sprints can complete 400 person-hours per sprint with five engineers (5 × 40 × 2). Project managers should plan in person-hours and convert to calendar weeks at the staffing level, not the other way round.
Why 40 hours became the work week
The 40-hour work week became US law in 1938 with the Fair Labor Standards Act, which set the overtime threshold at 40 hours. It built on a labour movement that began in the 1860s and accelerated after Henry Ford adopted a 40-hour, 5-day week in his factories in 1926 (without cutting wages).
Ford's reasoning was practical: shorter shifts produced fewer mistakes and lower worker turnover, which more than offset the lost hours. Other manufacturers followed by competitive necessity. By 1940, two-thirds of US manufacturing was on a 40-hour schedule; the FLSA codified what had already become standard practice.
Globally, the 40-hour week is now standard in most developed economies. France introduced a 35-hour week in 2000 as a labour-policy experiment; the cap remains in place but is widely worked around through overtime and salaried-exemption rules. The ILO recommends a maximum of 48 hours per week as an international floor.
Common hours-to-weeks mistakes
Using 168 for work weeks. Dividing 1,000 hours by 168 gives 5.95, which is calendar weeks. For payroll or staffing estimates, divide by 40 to get 25 work weeks instead. The two answers are not interchangeable.
Treating "4 weeks" as one month. Four work weeks at 40 hours = 160 hours. An average month is 30.44 days = 730.5 hours of calendar time, or 174 hours at the 40-hour standard. "One month" and "4 weeks" differ by about 14 hours of work time and most of a calendar week of elapsed time.
Forgetting overtime. Hours above 40 per work week trigger overtime pay in the US (1.5× the regular rate). 1,500 hours per year in a salaried position is normal; 2,500 hours per year as an hourly worker means 420 of those hours were paid at overtime rates.
Confusing the 10,000-hour rule. Malcolm Gladwell's "10,000 hours to expertise" is 250 work weeks of full-time deliberate practice, or 5 years of 40-hour work. It is not 10,000 calendar hours, which would be 14 months of continuous practice without sleep.
Mixing pay-period definitions. US biweekly payroll covers 80 work hours (2 work weeks). US semi-monthly payroll covers 86.67 work hours on average (2,080 / 24 periods). The two are not the same, and they round differently across the year.