Time is the best-behaved measurement system there is — every unit is an exact multiple of the next, no 2.54s or 0.3048s anywhere. That’s precisely why the few rough edges stand out.
The clean chain
60 seconds = 1 minute
60 minutes = 1 hour
24 hours = 1 day
7 days = 1 week
~30.44 days = 1 month
365.25 days = 1 year
The first four lines are exact. The last two aren’t — months vary from 28 to 31 days, and years need the leap-day correction. Any “1 month = 30 days” conversion is an approximation.
The numbers worth knowing
- 1 day = 86,400 seconds (60×60×24 — worth memorizing; it shows up in API timeouts and uptime metrics).
- 1 year ≈ 31.5 million seconds — the standard benchmark: a billion seconds is ~31.7 years.
- 1 week = 168 hours = 10,080 minutes — the planning units for sprints and schedules.
Where time conversion bites
- Overtime and payroll: minutes to decimal hours (45 min = 0.75 h) — the most common workplace conversion error.
- Video and audio duration: media tools count in seconds; humans read mm:ss.
- “30 days” guarantees: is that a calendar month or exactly 720 hours? Contracts argue this.
Converting
The time converter covers seconds, minutes, hours, days, weeks, months, and years — with the honest caveat that month and year conversions use average values.
Time’s cleanliness is why everything else gets compared against it — speeds are “per hour,” rates are “per second.” Get the base units right, and every derived number follows.