Days to Hours (d to h)
Last updated:
Converting days to hours runs in every project-management timeline that mixes day-tier deadlines with hour-tier task estimates, every legal-contract clause that specifies completion windows in business hours against calendar-day deadlines, every parental-leave and medical-leave duration calculation, and every hourly-billing freelance contract that quotes day-rate equivalents against hourly billing. The factor is exact (one day equals 24 hours by international convention) and the arithmetic is trivial, but the practical implication of the conversion is that day-tier and hour-tier mental models compete for primacy in scheduling work — and the right unit at any given moment depends on which scale produces the most actionable figure for the audience.
How to convert Days to Hours
Formula
h = d × 24
To convert days to hours, multiply the day figure by 24. The factor is exact by international convention — the modern day-as-86,400-seconds definition derives from the historical division of the solar day into 24 equal parts and has been the canonical time-tier relationship in every standardised time system since the SI second was redefined in 1967. The arithmetic is trivial — multiply by 24 — but the practical scope of the resulting hour figure varies dramatically by application context. For project management, multiply day-tier estimates by 24 to compare against hour-tier capacity budgets. For payroll, the same multiplication produces hour-tier accruals from day-tier statutory grants. For legal SLA windows, the multiplication establishes the canonical hour-tier deadline against which actual elapsed time gets measured.
Worked examples
Example 1 — 1 d
1 day equals exactly 24 hours by international convention. The figure is the foundational time-unit relationship that underlies every multi-day duration calculation. The conversion is exact and unambiguous in everyday contexts, though leap seconds and rare timekeeping adjustments introduce sub-second corrections in atomic-precision applications.
Example 2 — 7 d
7 days (one week) equals 7 × 24 = 168 hours. The figure is the standard "week-as-hours" reference used in shift scheduling, weekly billing arithmetic, and full-time-equivalent (FTE) capacity calculations. A 40-hour FTE work week consumes 40/168 = 23.8% of available calendar hours, which surfaces in workforce-planning utilisation calculations.
Example 3 — 30 d
30 days (one calendar month) equals 720 hours. The figure is the typical month-billing reference for hourly utilities, server uptime SLAs (99% of 720 = 712.8 hours of guaranteed uptime per month, equivalent to 7.2 hours of allowable downtime), and consultancy day-rate-versus-month-rate arithmetic. The 30-day approximation rounds the actual calendar month range of 28-31 days to a clean reference for utility billing.
d to h conversion table
| d | h |
|---|---|
| 1 d | 24 h |
| 2 d | 48 h |
| 3 d | 72 h |
| 4 d | 96 h |
| 5 d | 120 h |
| 6 d | 144 h |
| 7 d | 168 h |
| 8 d | 192 h |
| 9 d | 216 h |
| 10 d | 240 h |
| 15 d | 360 h |
| 20 d | 480 h |
| 25 d | 600 h |
| 30 d | 720 h |
| 40 d | 960 h |
| 50 d | 1200 h |
| 75 d | 1800 h |
| 100 d | 2400 h |
| 150 d | 3600 h |
| 200 d | 4800 h |
| 250 d | 6000 h |
| 500 d | 12000 h |
| 750 d | 18000 h |
| 1000 d | 24000 h |
| 2500 d | 60000 h |
| 5000 d | 120000 h |
Common d to h conversions
- 1 d=24 h
- 2 d=48 h
- 3 d=72 h
- 5 d=120 h
- 7 d=168 h
- 14 d=336 h
- 30 d=720 h
- 60 d=1440 h
- 90 d=2160 h
- 365 d=8760 h
What is a Day?
The day (d) is exactly 86,400 seconds (24 hours × 3600 seconds per hour) by SI civil-day definition, fixed by the 1967 atomic-clock SI second standard. The recognised symbol is "d" (lowercase) under ISO 80000-3 conventions. The day is not part of the SI base units but is recognised by NIST and BIPM as a non-SI unit accepted for use with the SI. The civil-day at 86,400 s differs slightly from the astronomical solar-day (which varies seasonally due to Earth's elliptical orbit, averaging 86,400.002 SI seconds) and from the sidereal-day (86,164.09 SI seconds, the rotation period relative to distant stars). The IERS leap-second system absorbs the small difference between civil-day and astronomical-day length to maintain UTC within ±0.9 s of UT1. Sub-day precision uses hours, minutes and seconds; super-day precision uses weeks, months and years.
The day as a unit of time has been preserved unchanged across human history as the fundamental natural-time-cycle defined by Earth's rotation relative to the Sun (the solar day, averaging 24 hours over a year due to Earth's elliptical orbit) or relative to distant stars (the sidereal day, exactly 23 hours 56 minutes 4.0905 seconds = 86,164.0905 SI seconds). The civil "day" of timekeeping is fixed at exactly 86,400 SI seconds (24 hours × 60 minutes × 60 seconds) by the 1967 SI second-definition, with the small difference between civil-day length and astronomical-day length absorbed into the leap-second system maintained by the International Earth Rotation and Reference Systems Service (IERS). Leap seconds are inserted (or hypothetically deleted) into UTC at irregular intervals to maintain UTC within ±0.9 seconds of UT1 (a measure of Earth-rotation-based time). Like hours and minutes, the day is not part of the SI base units but is recognised by NIST and BIPM as a non-SI unit accepted for use with the SI in everyday-time-keeping, scheduling, and biological-and-medical contexts.
Everyday timekeeping and calendar systems: every modern calendar (Gregorian, Islamic, Hebrew, Chinese, Persian) denominates dates in days alongside months and years. Civil-time scheduling, meeting-and-event scheduling, and casual time-references all use days universally. Biological-and-medical research: medication-dose intervals (twice daily, once daily, every other day), clinical-trial follow-up schedules (Day 1, Day 7, Day 28 standard timepoints), pregnancy gestational-age tracking (typical 280 days from last menstrual period), and chronic-disease progression monitoring all use days as the natural time-unit for biological processes. Astronomy and space-science: orbital-mechanics calculations (planetary orbital periods in days, satellite-orbit periods in fractions of a day), space-mission-scheduling (Apollo missions in days, Mars-rover-mission time in sols-or-days), and astronomical-observation scheduling all use days as the natural time-unit for celestial-mechanics work. Employment and payroll: salary-quotation systems (US per-day rates for contractors, UK locum-medical-doctor day rates, freelancer day-rate quotations) use the day as the natural employment-time unit. Typical professional contractor day-rate is £400-£800 in the UK; salary-equivalent annual figures translate from per-day rates times typical 230 working days per year (260 weekday-days minus 30 holidays).
What is a Hour?
The hour (h) is exactly 3600 seconds (60 minutes × 60 seconds) by SI definition, derived from the Babylonian-Egyptian sexagesimal time-division system preserved unchanged into the modern SI second. The recognised symbol is "h" (lowercase) under ISO 80000-3 conventions, with "hr" appearing in some casual writing as a non-standard variant. The hour is not part of the SI base units but is recognised by NIST and BIPM as a non-SI unit accepted for use with the SI. The relationship to the second is exact (1 h = 3600 s), to the minute is exact (1 h = 60 min), and to the day is exact (1 day = 24 h). Sub-hour precision uses minutes and seconds; super-hour precision uses days, weeks, months and years. The hour is universally used across every modern timekeeping context globally.
The hour as a unit of time has been preserved unchanged from ancient Egyptian and Babylonian astronomy, where the day was first divided into 24 hours (12 daylight hours and 12 nighttime hours) by ancient Egyptian astronomy in the second millennium BC. The 24-hour day was preserved through Greek and Roman astronomy and into the modern SI time-system without modification. The unit's name derives from the Greek "hora" (season, time of day, hour). Like the minute, the hour is not part of the SI base units but is recognised by NIST and BIPM as a non-SI unit accepted for use with the SI in everyday-time-keeping, transportation, employment-and-payroll, and engineering contexts. The 1967 SI second-definition transitively defined the hour as exactly 3600 seconds (60 minutes × 60 seconds), fixed by the atomic-clock primary standard. ISO 80000-3 specifies seconds as the SI-canonical primary time unit but tolerates hours in commercial-and-everyday timekeeping contexts. The hour is universally used across timekeeping, transportation-scheduling, employment-and-payroll wage-rate specifications, and engineering-process documentation.
Everyday timekeeping: every clock, watch, smartphone, and digital display denominates time-of-day in hours alongside minutes. The 12-hour AM/PM format is dominant in US-customary timekeeping; the 24-hour format is dominant in EU-jurisdiction and most non-US timekeeping. Both express the same underlying SI hour. Transportation scheduling: every flight schedule, train timetable, ship-arrival notification, and bus schedule denominates time in hours-and-minutes format for the consumer-facing schedule display. Aviation universally uses 24-hour format (UTC for international flights, local-time for domestic); rail timetables in the EU use 24-hour format; US domestic transportation typically uses 12-hour AM/PM format. Employment and payroll: hourly wage rates (US-jurisdiction federal minimum wage at $7.25/hour, UK National Living Wage at £11.44/hour for 21+ in 2024, various state and EU national minimum-wage figures) universally use hours as the wage-rate denominator. Salary-equivalent annual figures translate from per-hour wages times typical 2080 working hours per year. Engineering and process specifications: industrial-process throughput rates, vehicle-fuel-economy figures (mpg in US, l/100km in EU, with both reflecting fuel-per-distance over operational hours), HVAC capacity ratings (BTU/h, kW), and electricity-billing units (kWh) all use hours as the time denominator.
Real-world uses for Days to Hours
Project management timeline planning
Project managers translating between day-tier sprint planning and hour-tier task estimation use the days-to-hours conversion at every estimation refinement step. A 10-day project window converts to 240 hours of available work time, but practical capacity often runs at 60-70% of nominal because of meetings, communication overhead, and context-switching. The conversion drives the gap between calendar-day deliverables and actual-hour task budgets that defines whether projects ship on schedule or slip.
Legal contract and SLA windows
Legal contracts specifying response windows or service-level agreements often denominate timeframes in hours (a 24-hour response SLA, a 72-hour cure period) but reference deadlines as calendar days. Translating between the two scales matters when business-hours-only versus calendar-hours interpretation affects whether weekend hours count toward the SLA window. A "three-day cure period" in a contract typically means 72 hours, but business-day-only interpretation excludes weekends and could extend the calendar window to 5+ days.
Maternity, paternity, and medical leave duration
Human resources and benefits administrators translating between day-tier statutory leave allowances and hour-tier payroll-system tracking convert via the 24× factor for full-day equivalence. A 12-week maternity leave equals 84 days equals 2,016 hours of paid leave at the payroll-system level. The conversion runs in HRIS configuration, statutory-leave reporting, and benefit-cost projection across every employer-sponsored leave program in jurisdictions that mandate paid leave durations in days.
When to use Hours instead of Days
Use hours when working at the granularity where individual tasks, shifts, billing increments, or SLA-window measurements live — task-tracking software, hourly billing logs, payroll-system shift records, server-uptime SLAs, and any application where hour-precision matters for the operational metric. Stay in days when communicating multi-day plans, calendar-window deadlines, leave allowances, lease durations, or any context where the day is the natural unit of expression. The conversion runs at the boundary where multi-day plans need hour-tier validation against capacity budgets — a 10-day project plan needs 240-hour capacity verification before commitment. The choice between days and hours follows the audience's mental model rather than physical correctness; both denominations describe the same elapsed time at different scales.
Common mistakes converting d to h
- Conflating calendar hours with business hours in legal SLA contexts. A "24-hour SLA" interpreted as calendar hours means the response is due exactly one day after request; interpreted as business hours, the same SLA could extend across a weekend to three calendar days. The contract language usually clarifies, but ambiguous phrasing introduces material differences in compliance windows. Always confirm the hour-counting convention before measuring SLA performance.
- Using "1 day = 8 hours" (a workday) instead of "1 day = 24 hours" (a calendar day). The 8-hour-workday convention applies in payroll and project-capacity contexts but not in legal-deadline or SLA contexts. A "10-day project" at 8 hours each yields 80 work hours; the same "10 days" interpreted as calendar elapsed time spans 240 hours. The right factor depends on whether the day-tier source figure refers to work-capacity or calendar-elapsed-time.
Frequently asked questions
How many hours in 1 day?
1 day equals exactly 24 hours by international convention. The relationship is fixed and exact in everyday contexts; leap seconds and rare timekeeping adjustments produce sub-second variations that don't affect day-to-hour arithmetic. The conversion is foundational to every time-unit calculation that spans calendar tiers.
Why do business contracts sometimes use 8-hour days?
Because work-capacity and calendar-time use different conventions. A "5-day project estimate" in consulting usually means 5 working days (40 hours) at 8 hours per day, not 5 calendar days (120 hours). Legal deadlines and SLA windows typically use calendar-day arithmetic (24 hours each). Always confirm whether a day-tier figure refers to work capacity or calendar elapsed time before doing the multiplication.
How does this conversion handle leap days?
February 29 in leap years adds one extra day to the calendar but doesn't change the days-to-hours conversion factor — every day still equals 24 hours. The leap day itself contains 24 hours like any other day. Year-tier arithmetic that counts days needs leap-year awareness (365 vs 366 days), but day-to-hour arithmetic is unaffected.
Are SLA "hours" always calendar hours?
Not always. Some SLAs specify "business hours" (9 AM to 5 PM Monday through Friday in the relevant timezone), others specify "calendar hours" (24/7 elapsed time). A 24-business-hour SLA is roughly three business days and could span a weekend; a 24-calendar-hour SLA is one full calendar day regardless of weekend. Read the contract language carefully — the difference between conventions affects compliance reporting substantially.
Can I use this for ongoing service durations like rental periods?
Yes — the conversion is purely arithmetic and applies to any duration that's denominated in days and needs to translate to hours. A 7-day vehicle rental converts to 168 hours; a 30-day apartment lease converts to 720 hours. The hourly figure becomes useful for prorated daily-rate calculations or for comparing across rental schemes that quote at different denomination scales.