Converting Time Units: The One Division Behind Seconds to Years

A project plan counts in days, a meeting invite counts in minutes, a server timeout is set in milliseconds, and an uptime target is quoted per year. These are all the same kind of quantity — a duration — just counted in different-sized chunks, so converting between any two is one multiplication and one division through a common base.

The method: convert through a fixed base unit

This tool uses seconds as the base. Every other time unit is a fixed number of seconds — a minute is always 60, an hour is always 3,600, a day is always 86,400. To convert a value from one unit to another: multiply by the source unit's seconds-per-unit, then divide by the target unit's seconds-per-unit.

answer = value × (source seconds-per-unit) ÷ (target seconds-per-unit)

That's the whole method. Minutes to weeks, milliseconds to hours — same formula, different pair of numbers.

The numbers

• 1 second = 1 second (the base)
• 1 millisecond = 0.001 seconds
• 1 minute = 60 seconds
• 1 hour = 3,600 seconds
• 1 day = 86,400 seconds
• 1 week = 604,800 seconds
• 1 year = 31,557,600 seconds (365.25 days — see below for why)

A worked example: 90 minutes into hours

90 × 60 seconds per minute = 5,400 seconds. Divide by an hour's 3,600 seconds: 5,400 ÷ 3,600 = 1.5 hours — the arithmetic behind reading "90 min" on a meeting invite as an hour and a half.

A worked example: how long is a million seconds, really

1,000,000 ÷ 86,400 seconds per day = 11.574074… days, or about 11 days and 14 hours (0.574074 × 24 ≈ 13.78 hours). It's a useful gut check: a "million" of something sounds enormous, but a million seconds is under two weeks.

A worked example: how long is a billion seconds

1,000,000,000 ÷ 31,557,600 seconds per year = 31.69 years. That thousand-fold jump from an 11-day million to a 32-year billion is the whole point of doing the division rather than trusting intuition about "big numbers."

Why a year is 365.25 days here, not 365

A calendar year is 365 days three years out of four and 366 on a leap year, which averages to 365.25 days over a four-year cycle — the Julian year, a standard reference length used so multi-year conversions don't drift. It means a year here is 8,766 hours exactly (365.25 × 24), a quarter-day more than the 8,760 hours you'd get by assuming a flat 365-day year. For a single calendar year that quarter-day is easy to miss; over a decade of "per year" math it's 2.5 full days of difference.

A sanity check: is a year exactly 52 weeks?

31,557,600 ÷ 604,800 seconds per week = 52.178571… weeks, not a clean 52. That's honest, not a bug: 52 weeks is only 364 days, so every calendar year runs about 1.25 weeks longer than "52 weeks" — which is exactly why a yearly event doesn't land on the same weekday the following year.

What the tool adds

The seven numbers above are everything you need, on paper, for any pair of time units. The tool's job is just speed — type the value, pick the two units, and it runs the same multiplication instantly, entirely on your device.