The ladder method
Every time conversion is one sentence: multiply going down the ladder, divide going up. The ladder runs seconds ← minutes ← hours ← days ← weeks ← (months) ← years. Converting 3 hours to minutes means going down one rung, so multiply: 3 × 60 = 180 minutes. Converting 9,000 seconds to hours means going up two rungs, so divide twice: 9,000 ÷ 60 = 150 minutes, ÷ 60 = 2.5 hours. Skipping rungs is fine — just use the combined factor (hours to seconds is × 3,600).
Memorize one number: 86,400
The single most useful time fact is that a day holds 86,400 seconds (24 × 60 × 60). From it, everything common falls out: a week is 7 × 86,400 = 604,800 seconds; an hour is 86,400 ÷ 24 = 3,600; a 30-day month is 30 × 86,400 = 2,592,000. Programmers live by this number — a "90-day token expiry" is 90 × 86,400 = 7,776,000 seconds, and a cron expression that fires daily is really "every 86,400 seconds." If you memorize one conversion constant this year, make it this one.
Worked example 1: seconds in a year
The classic. Start from the anchor: 86,400 seconds per day. A common year has 365 days: 365 × 86,400 = 31,536,000 seconds. A leap year adds a day: 366 × 86,400 = 31,622,400. The long-run average year (365.25 days, leap years folded in) gives 365.25 × 86,400 = 31,557,600 — the figure to use for anything measured "per year" across many years, like uptime percentages or annualized rates. The time unit converter runs all three year lengths on any amount.
Worked example 2: your age in seconds
Take 30 years: 30 × 31,557,600 = 946,728,000 seconds — just under a billion. That "billion seconds" milestone lands at about 31.69 years (1,000,000,000 ÷ 31,557,600). A billion minutes, by contrast, is nearly 1,902 years — the units you choose change the story completely, which is exactly why converting cleanly matters.
Trap 1: months are not a fixed unit
February has 28 days, most months have 30 or 31 — so "3 months in seconds" has no exact answer without naming the months. The standard convention is the average month: 30.436875 days (365.25 ÷ 12), or 2,629,746 seconds. Use it for subscriptions, rent math, and "per month" rates. But for an exact calendar stretch — January 5 to April 5 — count the days directly (31 + 28 + 31 + 5 = 95 days in a common year) instead of trusting any converter, including ours.
Trap 2: which year?
Three year-lengths circulate, and mixing them silently corrupts long calculations: common year (365 days, 31,536,000 s) for single calendar years, leap year (366 days, 31,622,400 s) when February 29 falls inside, and average year (365.25 days, 31,557,600 s) for multi-year rates. Over a 30-year mortgage, using the common year instead of the average year understates total seconds by 1,814,400 — 21 days. Pick the year deliberately, and state which one you used.
Quick-reference table
| Unit | Seconds | Notes |
|---|---|---|
| Minute | 60 | Exact |
| Hour | 3,600 | Exact |
| Day | 86,400 | Exact (civil time) |
| Week | 604,800 | Exact |
| Average month | 2,629,746 | 30.436875 days by convention |
| Common year | 31,536,000 | 365 days |
| Leap year | 31,622,400 | 366 days |
| Average year | 31,557,600 | 365.25 days, long-run |
| Decade | 315,576,000 | 10 average years |
| Century | 3,155,760,000 | 100 average years |
Practice set
Try these, then check yourself on the converter: (1) 2.5 hours in seconds — 9,000. (2) 100,000 seconds in hours — 27.78. (3) A decade in days — 3,652.5. (4) 1 million seconds in days — 11.57. The pattern never changes: convert through seconds, multiply down, divide up.