The Decan Priests: How 24 Got Chosen
Around 2100 BCE, Egyptian priests tasked with tracking the annual Nile flood noticed that certain bright stars �?Sirius, Orion's belt, specific stars in Canis Major �?rose just before dawn at roughly 10-day intervals throughout the year. They identified 36 of these star groups, called decans. Each decan "ruled" for 10 days. At night, during the 12 hours of darkness (Egyptian nights are roughly 12 hours year-round, thanks to latitude), 12 decans would rise in sequence �?one per hour �?marking the passage of the night on the eastern horizon. The 12 "night hours" were born from counting decans. The 12 "day hours" were invented to match, creating a 24-hour cycle.
This system passed from Egypt to Greece (Hipparchus, Ptolemy), from Greece to Rome, from Rome to medieval Islam, and from Islam back to Europe through the translations of the 12th century. The 24-hour day survived the fall of every empire that used it. It survived Copernicus, who rearranged the solar system but kept the 24-hour day. It survived the French Revolution, which metricated time itself �?hours, minutes, seconds, the calendar �?and lost. It survived the invention of the atomic clock, which revealed that the Earth's rotation is not a constant 24 hours but varies by milliseconds. The cesium atom's hyperfine transition defines the second. The Earth's rotation defines the day. The factor of 86,400 that connects them �?24 × 60 × 60 �?is a 4,200-year-old compromise between a group of priests watching stars over the Nile and a 20th-century quantum mechanical definition of the second that those priests could not have conceived of. The conversion has outlasted every civilization that contributed to it. It will outlast ours.
1793: the French Tried to Decimalize the Day. It Did Not Go Well.
The same revolutionary government that gave the world the meter and the kilogram also attempted to decimalize time. The French Republican Calendar divided the day into 10 hours, each hour into 100 minutes, and each minute into 100 seconds �?100,000 decimal seconds per day versus 86,400 conventional seconds. The decimal second was 0.864 conventional seconds, slightly shorter. Decimal clocks were manufactured and installed in the Tuileries Palace and other government buildings. The law mandating their use passed on October 5, 1793.
The public ignored it. The 10-hour workday was unpopular because it was actually longer than a 12-hour conventional workday (the decimal hour was 144 minutes). The decimal clock face, with 10 numerals instead of 12, was visually alien to everyone who had learned to read a clock. Watchmakers objected because every clock in France would need to be replaced. Church officials objected because the canonical hours of prayer were tied to the 24-hour cycle. The decimal time system was suspended in 1795 and formally abolished by Napoleon in 1805. The French decimal calendar �?12 months of 30 days each, with 5 or 6 complementary days at the end of the year �?lasted until 1805 as well, then was abandoned. The metric system succeeded where decimal time failed because the metric system replaced chaos (250,000 local units of measurement in pre-revolutionary France) with order, while decimal time replaced a single universally accepted system (24 hours) with another single system (10 hours) that offered no clear advantage. The metric system solved a real problem. Decimal time created one.
Mars Time: When ×24 Is the Wrong Multiplier
A Martian sol �?one rotation of Mars �?is 24 hours, 39 minutes, and 35.244 seconds. That's 88,775.244 seconds, or roughly 24.6597 Earth hours. The 39-minute difference per day accumulates: after 10 sols, a Mars rover operator's shift has drifted by roughly 6.5 hours �?half a workday. After 36 sols, the operator is working the night shift relative to Earth. The Spirit, Opportunity, Curiosity, and Perseverance rover teams all operated on Mars time during the primary mission phase. Engineers wore Mars watches �?custom timepieces programmed to run 39 minutes slow per day. Meetings were scheduled on Mars calendars. The rover's downlink windows �?the times when the rover could communicate directly with Earth �?occurred once per sol, and the ground team had to be awake to receive the data, analyze it, plan the next sol's activities, and uplink the commands before the rover's next wake cycle. If the ground team missed the window, the rover sat idle for a sol �?wasting a day of a $2.5 billion mission.
One sol = 24.6597 Earth hours. The days-to-hours conversion on Mars is not ×24. It's ×24.6597. The only humans who regularly perform this conversion work at the Jet Propulsion Laboratory in Pasadena. The rest of us can use ×24 and move on with our lives.
hours = days × 24
Worked Examples
1 day �?24 hours
The definition. One rotation of the Earth relative to the Sun. Give or take a few milliseconds of tidal friction �?the Earth's rotation slows by roughly 1.8 milliseconds per century, so the day was about 22 hours long 600 million years ago. The 24-hour day we now measure is a snapshot in a 4.5-billion-year deceleration.
3 days �?72 hours
The standard Amazon Prime delivery window. The 72-hour visa-free transit policy in several countries. The maximum time a pizza is theoretically still safe in the fridge according to USDA guidelines �?not that anyone follows them.
7 days �?168 hours
One week. 168 hours. Subtract roughly 56 hours of sleep (8 per night), 40 hours of work, and 21 hours of eating �?leaves roughly 51 hours of discretionary time. The week is the only time unit with no astronomical basis: it's roughly one lunar phase (7.38 days), but the 7-day week is a Babylonian religious convention that passed through Judaism, Christianity, and Islam to become a global civil standard.
30 days �?720 hours
A standard billing month. Cloud providers bill by the hour. A server running 24/7 for 30 days costs 720 × the hourly rate. The "30-day month" is a financial convention �?only 4 of the 12 months have exactly 30 days. The other 8 require a calendar lookup.
365 days �?8,760 hours
A non-leap year. 8,760 hours. That's the denominator in every annual uptime SLA calculation: 99.9% uptime allows 8.76 hours of downtime per year. 99.99% allows 0.876 hours �?52.6 minutes. Every additional "9" divides the allowable downtime by 10. The days-to-hours conversion is the first step in the arithmetic that keeps websites online.
Common Days to Hours
| Days | Hours | Context |
|---|---|---|
| 1 day | 24 h | One Earth rotation. The definition. |
| 3 days | 72 h | Amazon Prime. Visa-free transit limit. Leftover pizza window. |
| 5 days | 120 h | Work week. 40 hours of work, 80 hours of everything else. |
| 7 days | 168 h | One week. The Babylonian unit that conquered the world. |
| 14 days | 336 h | Fortnight. Two weeks. A standard vacation. Biweekly payroll. |
| 30 days | 720 h | Cloud billing month. Free trial period for most SaaS products. |
| 90 days | 2,160 h | Standard probation period for new hires. One season. |
| 365 days | 8,760 h | One year. The annual SLA denominator. |
Engineering Context
The days-to-hours conversion (×24) is exact and invariant in civil timekeeping. A day is defined as 24 hours by international agreement, and the hour is defined as 60 minutes = 3,600 seconds. The second is the SI base unit, defined by the cesium-133 hyperfine transition. The chain: 1 day = 24 h × 3,600 s/h = 86,400 s. This chain is what makes the Unix epoch (seconds since 1970-01-01T00:00:00Z) meaningful: every Unix timestamp is a count of 86,400-second days since the epoch, plus the intra-day seconds, minus the 27 leap seconds that have been inserted since 1972. The days-to-hours conversion is the first multiplication in every time-related software engineering problem. For the reverse direction, see hours to days. For the full time conversion ladder: hours to minutes (×60), hours to seconds (×3,600), and minutes to seconds (×60). For the larger scale: days to weeks and days to months handle the calendar conversions where the factor varies by month.
More: hours to days · hours to minutes · hours to seconds · minutes to seconds · Time Guide
Related Unit Converters
Frequently Asked Questions
Why 24 hours and not 10 or 20?
The Egyptians used base-12 counting �?three finger joints on each of four fingers, counted with the thumb as a pointer, gives 12 per hand. The 12 night decans (stars that marked the hours) gave 12 night-hours. The 12 day-hours were symmetrical. No surviving Egyptian text explains why they didn't use 10 (fingers) or 20 (fingers and toes). The most plausible theory: base-12 is more divisible than base-10 (12 divides by 2, 3, 4, 6; 10 divides only by 2 and 5), and ancient accountants and astronomers valued divisibility over decimal convenience. The same reason the Babylonians chose base-60 for minutes and seconds. A number with many divisors is a number that prevents arguments.
Is a day exactly 24 hours?
For civil timekeeping, yes �?by definition. For astronomy, no. A solar day (noon to noon) varies by roughly ±30 seconds over the course of a year due to the Earth's elliptical orbit and axial tilt. The mean solar day averages 24 hours exactly. A sidereal day �?one rotation relative to the fixed stars �?is 23 hours, 56 minutes, 4.0916 seconds. The 3-minute-56-second difference is the extra rotation needed to bring the Sun back to the same position after the Earth has moved in its orbit. The day you live by is the solar day. The day a telescope tracking a star lives by is the sidereal day. The conversion from days to hours is always ×24. The definition of "day" changes depending on what you're measuring it against.
How does daylight saving time affect the days-to-hours conversion?
A 23-hour day (spring forward) and a 25-hour day (fall back) exist in civil time but not in physical time. The Earth's rotation does not change. The clock on the wall does. The days-to-hours conversion in physical time is always ×24. In civil time, on DST transition days, the conversion is ×23 (spring) or ×25 (fall). Software that assumes every day has exactly 24 hours will produce a result that is one hour wrong on DST transition days �?an error that has caused billing discrepancies in hotel reservation systems, payroll errors in shift scheduling software, and at least one satellite ground station pass that was scheduled in local time and missed the first hour of the pass window. Store times in UTC. Convert to local time only for display. The rule is simple. The violations of it fill postmortem documents.
How do you calculate SLA uptime in hours from a percentage?
Downtime hours per year = (100% �?SLA%) × 8,760 / 100. For 99.9%: 0.1% × 8,760 / 100 = 8.76 hours/year = 526 minutes/year. For 99.99%: 0.01% × 8,760 / 100 = 0.876 hours = 52.6 minutes. For 99.999% ("five nines"): 0.526 minutes = 31.5 seconds per year. Every additional nine in the SLA reduces allowable downtime by a factor of 10. The arithmetic starts with 365 days × 24 hours/day = 8,760 hours. The days-to-hours conversion is the denominator beneath every uptime guarantee ever written into a cloud contract. Get it wrong and the SLA is a lie. Get it right and the SLA is still mostly aspirational �?but at least the math checks out.