Time Conversion: Clean Weeks, Averaged Years

Below a month, time converts like any other unit: fixed factors, no surprises. At months and years the calendar refuses to cooperate — months run 28 to 31 days and years 365 or 366 — so the Time Converter resolves the ambiguity by fixing precise definitions for the big units. Here are those definitions, stated plainly, so you know exactly what an "answer in months" means.

Everything pivots through seconds

Like every converter on the site, the tool is one factor table: multiply the input to seconds, then divide out each target unit:

1 ms  = 0.001 s
1 s   = 1 s           (the pivot)
1 min = 60 s
1 h   = 3,600 s
1 d   = 86,400 s
1 w   = 604,800 s
1 mo  = 2,629,800 s   (30.4375 days)
1 y   = 31,557,600 s  (365.25 days)

Enter 90 min and the tool computes 5,400 s once, then reports 1.5 h, 0.0625 d, and every other unit from that figure. One pass, one pivot, no chained roundings to accumulate.

The clean ladder below a month

From milliseconds up to weeks, every factor is an exact definition: 60 seconds per minute, 60 minutes per hour, 24 hours per day, 7 days per week. The day's 86,400 seconds is not a measurement of any particular day — it is the definition of a civil day, and the week's 604,800 s is just seven of them. Nothing in this range is approximate, which is why duration arithmetic in code (timeouts, leases, cache TTLs) is always written in these small units rather than months.

Months and years: the tool picks an average

Above the week, no exact factors exist, so the converter adopts conventional averages: the month is 2,629,800 s, which is 30.4375 days — exactly one twelfth of a 365.25-day year — and the year is 31,557,600 s, the Julian year, the same 365.25-day year a light-year is built on. For comparison, the mean Gregorian calendar year is 365.2425 days = 31,556,952 s, so the tool's year runs about 648 s (eleven minutes) long. Over a decade that is under two hours — negligible for estimates, but the reason contracts and subscriptions say "30 days" when they mean a month: a calendar month is 2,419,200 s (28 days) to 2,678,400 s (31 days), and no single number can stand in for all of them.

Where the second itself comes from

The SI second is defined atomically — 9,192,631,770 oscillations of a cesium-133 atom — and the 86,400-second day is a definition layered on top of it. The real Earth runs slightly irregularly, which is why leap seconds occasionally stretch a calendar day to 86,401 seconds. For converting durations, the definitions are exactly what you want; the wobble belongs to clockkeeping, not to arithmetic.

Durations are not clock times

Converting 90 minutes to 1.5 hours is duration math, and this tool's whole job. "What time is it in Tokyo" is a different problem: time zones shift the reading on the clock without changing how long anything lasts. A meeting that lasts one hour lasts one hour in every zone; only its start and end labels move. That second job belongs to the Time Zone Converter. And when time appears as the denominator — pace, speed, throughput — the same factors feed rates, covered alongside the units of motion in Speed and Time Units.

Try it yourself

Enter a duration you can verify — say 3 days — in the Time Converter and confirm 259,200 s, 72 h, and 0.4286 weeks appear from one input. Then convert a calendar span like "6 months" and read it as 0.5 years, the averaged convention, not six named months. For clock arithmetic across cities, switch to the Time Zone Converter, and for anything expressed per hour — speeds, flow rates — the Speed Converter picks the rate up where durations end.