1What a time conversion actually is

Converting time is converting between nested containers. Seconds pack into minutes, minutes into hours, hours into days, days into weeks — each level a fixed multiple of the one below. Unlike temperature, there are no offsets: zero seconds is zero minutes in every system. It's all multiplication and division, which makes time one of the most forgiving things to convert.

The standard technique — the one our converter uses internally — is to route everything through seconds. Multiply your value by how many seconds one of your units holds, then divide by how many seconds one of the target unit holds. Hours to minutes? An hour holds 3,600 seconds, a minute holds 60: 3,600 ÷ 60 = 60 minutes per hour. You already knew that, but the same machinery handles milliseconds-to-years without breaking a sweat.

Where it gets interesting is at the top of the ladder: months and years aren't fixed containers. February has 28 days (sometimes 29), April has 30, January has 31 — so converters use averages: a month of 30.436875 days and a year of 365.25 days. Those averages are exact enough for every everyday calculation, from project planning to interest math. Just don't use them for contracts or court deadlines — there, count actual calendar days.

2The chain: 60 → 60 → 24 → 7

The everyday chain, the one worth memorizing cold:

60 seconds = 1 minute  ·  60 minutes = 1 hour  ·  24 hours = 1 day  ·  7 days = 1 week

From those four facts you can derive the greatest hits: a day holds 86,400 seconds (24 × 60 × 60). A week holds 168 hours (24 × 7) and 10,080 minutes (168 × 60). An hour holds 3,600 seconds. These are the numbers that show up in workout plans, billing disputes, server uptime SLAs, and "how many seconds old am I" party tricks.

The time chain — each step multiplies Second Minute Hour Day Week ×60×60×24×7 1 week = 168 hours = 10,080 minutes = 604,800 seconds Going down? Divide by the same numbers.
Four multiplications connect a second to a week: ×60, ×60, ×24, ×7.
Worked examples:
1. A football match: 90 minutes → hours: 90 ÷ 60 = 1.5 hours (1 hour 30 minutes).
2. A work week: 40 hours → minutes: 40 × 60 = 2,400 minutes.
3. A day in seconds: 24 × 60 × 60 = 86,400 seconds.
4. 2.5 days → hours: 2.5 × 24 = 60 hours.

3Why 60? Thank the Babylonians

Around 2000 BCE, Babylonian astronomers counted in base 60 — and the habit never died. Sixty was a brilliant choice for a pre-decimal world because it divides evenly by 2, 3, 4, 5, 6, 10, 12, 15, 20, and 30. A third of an hour is a clean 20 minutes; a quarter is 15; a sixth is 10. Fractions were easy centuries before decimal notation existed.

The 24-hour day comes from ancient Egypt, where astronomers tracked 12 "decans" (star groups) by night and 12 by day. The 7-day week also traces to Babylon, honoring the seven visible "planets" (Sun, Moon, Mercury, Venus, Mars, Jupiter, Saturn). So your watch face is a museum: Babylonian arithmetic, Egyptian astronomy, and Babylonian astrology, all still ticking.

Why 60 survived 4,000 years: it divides beautifully 60 divides evenly by ÷2 = 30÷3 = 20÷4 = 15÷5 = 12 ÷6 = 10÷10 = 6÷12 = 5÷15 = 4÷30 = 2
Ten clean divisors: that's why an hour splits so neatly into halves, thirds, quarters and fifths.

Revolutionaries tried to kill it. In the 1790s, French revolutionaries proposed decimal time — 10 hours per day, 100 minutes per hour. It lasted about as long as you'd expect: people hated it, clocks were expensive to replace, and base 60's divisibility kept winning arguments. Some standards survive because nothing better comes along.

4Days, weeks, months, years — and the averages

Up to weeks, everything is exact. Then the calendar gets wobbly:

Why 365.25 and not 365? Because the Earth takes about 365.2422 days to orbit the Sun, and the calendar has to stay in sync with the seasons. The leap-year rule (with its century exception) keeps the average year at 365.2425 days — close enough that the calendar drifts only one day every few thousand years. Good enough for popes and programmers alike.

When averages aren't enough: for contracts, visas, subscriptions, and anything with a deadline, count actual calendar days between the two dates — don't convert "3 months" to 91.3 days. Our date difference calculator does exact calendar math.

5The full ladder, milliseconds to years

Our converter handles eight units. Here's the complete ladder with each unit's size in seconds:

UnitEqualsIn secondsYou'll meet it in
Millisecond (ms)0.001 s0.001Computing, reaction times, audio latency
Second (s)base unit1The anchor everything converts through
Minute (min)60 s60Cooking, meetings, workouts
Hour (hr)60 min3,600Work, travel, billing
Day24 hr86,400Deadlines, itineraries, habits
Week7 days604,800Pay cycles, project sprints
Month (avg)30.436875 days2,629,746Rent, subscriptions, salaries
Year (avg)365.25 days31,557,600Age, interest, long plans

And the day-scale table from our tool page, handy for project planning:

DaysHoursMinutes
1241,440
7 (1 week)16810,080
1433620,160
30 (≈1 month)72043,200

6Everyday conversions you'll actually use

Billing and freelancing

You worked 7 hours 45 minutes. In decimal hours (what invoices want): 7 + 45/60 = 7.75 hours. At $50/hr, that's $387.50. The decimal-hours conversion — minutes ÷ 60 — is the single most useful time math in freelance life. 15 minutes = 0.25 hr, 30 = 0.5, 45 = 0.75.

Cooking

"Simmer for 2½ hours" = 150 minutes = 9,000 seconds. Slow-cooker recipes in hours, pasta in minutes, microwave in seconds — a recipe collection spans the whole ladder, and converting keeps you from setting a 90-minute timer as 90 seconds.

Travel

A 14-hour flight is 840 minutes; a 45-minute layover is 0.75 hours. When you're adding flight + layover + drive, convert everything to minutes first, add, then convert back — mixing units mid-addition is where errors creep in.

Fitness

Marathon training plans mix everything: "run 90 minutes," "intervals of 400m in 90 seconds," "long run 2:30." Converting the plan into one unit (minutes) before the week starts means no mid-run arithmetic.

The "how old am I in…" game

Thirty years is about 30 × 31,557,600 = 946,728,000 seconds — just under a billion. It's a fun number, and it's also a decent intuition pump: a billion seconds is about 31.7 years, which is why 32-bit computer timestamps (which count seconds) needed upgrading.

7The atomic second: time's unchanging anchor

For most of history, the second was defined as a fraction of the day — 1/86,400 of Earth's rotation. The problem: Earth's rotation wobbles. Tides slow it down, earthquakes speed it up, and the "second" kept changing length by tiny amounts. For railways that was fine; for GPS satellites and physics, it wasn't.

In 1967, the second was redefined by atomic physics: exactly 9,192,631,770 oscillations of a cesium-133 atom. Atoms don't wobble. That gave time an unchanging anchor — the modern SI second — and everything else (minutes, hours, days) hangs off it. Even today the tidy system has one untidy corner: occasional leap seconds are slipped in to keep atomic clocks in step with Earth's slowing spin. Our converter uses the clean averages and skips leap seconds, which is correct for every everyday calculation.

8Mistakes and edge cases

9Time at work: shifts, overtime and billable hours

Few places convert time as constantly as the workplace. Shifts, timesheets, overtime rules, and invoices all run on time math — and small conversion slips become real money.

Decimal hours are the currency of payroll. A timesheet that says 7:45 doesn't mean 7.45 hours — it means 7 hours 45 minutes, which is 7.75 hours (45 ÷ 60). The quarter-hours to memorize: :15 = 0.25, :30 = 0.5, :45 = 0.75. A 40-hour week at 8 hours a day is really 8.0 × 5; a week of 8:30 shifts is 8.5 × 5 = 42.5 hours — 2.5 hours of overtime hiding in plain sight if you read the clock literally.

Shift patterns live in 12s and 24s. A "4 on, 4 off" 12-hour shift pattern means 42 hours a week on average (12 × 7 ÷ 2). Night shifts crossing midnight need the date attached — "11 PM to 7 AM" is 8 hours, but only if you count across the day boundary. This is where people undercount: always convert the overnight span to 24-hour time first (23:00 → 07:00 = 8 hours), then do the math.

Freelancers and consultants convert in the other direction: turning tracked minutes into invoice lines. Ninety minutes of work is 1.5 hours; at $80/hr that's $120. Most invoicing tools accept decimals, so the minutes ÷ 60 step is the whole job. Track in minutes during the day (precise), invoice in decimal hours (standard) — and round per your contract's policy, not per your generosity.

Overtime thresholds are weekly math: 40 hours is 2,400 minutes. If you're at 39.5 hours on Friday afternoon, you have exactly 30 minutes before overtime kicks in. Converting the remaining time into minutes makes the end-of-week calculation instant — and it's the number your manager's spreadsheet is using, whether you've done the math or not.

One last workplace habit worth building: convert before you commit. "Can you have it by Friday?" means very different things as 2 days, 16 working hours, or 960 working minutes — and the person asking usually means the smallest one. Translating every deadline into hours on the spot is the cheapest insurance against the classic misunderstanding where both sides heard a different number.

The one-line timesheet trick: minutes ÷ 60 = decimal hours. 7:45 → 7.75 · 8:30 → 8.5 · 9:15 → 9.25. Do it once per entry and your timesheet, invoice, and payroll will always agree.

10How to use our free time converter

Pick any two units from milliseconds to years, type in either box, and convert instantly — routed through seconds for exactness, with the 30.436875-day month and 365.25-day year for the big units. The URL updates as you type, so every conversion is bookmarkable and shareable. Free, private, no signup, runs entirely in your browser.

Convert hours, minutes, days & more

Milliseconds to years, exact factors, a 1–30 day table, worked examples. Free forever.

⏱️ Open the Time Converter

100% free · No account · Private by design

11Frequently asked questions

Why are there 60 seconds in a minute?

We inherited base-60 counting from the Babylonians around 2000 BCE. Sixty divides neatly by 2, 3, 4, 5, 6, 10, 12, 15, 20 and 30, which made fractions easy centuries before decimal notation existed.

How many seconds are in a day?

86,400 seconds: 24 hours × 60 minutes × 60 seconds. A week has 604,800 seconds, and an average year has 31,557,600 seconds.

What is a leap year?

A year with 366 days, adding February 29. It happens in years divisible by 4, except century years not divisible by 400 — so 2000 was a leap year but 1900 was not. This converter uses the average year of 365.25 days.

Why is a month 30.436875 days here?

Real months vary from 28 to 31 days, so converters use the average: 365.25 ÷ 12 = 30.436875 days. Fine for estimates — but use exact calendar dates for contracts or deadlines.

How many minutes are in a week?

10,080 minutes: 7 days × 24 hours × 60 minutes. There are 168 hours in a week.

How do I convert 90 minutes to hours?

Divide by 60: 90 ÷ 60 = 1.5 hours, which is 1 hour 30 minutes. A football match is the classic 90-minute example.

Keep exploring

Time connects to everything — these tools handle its closest neighbors:

Related guides

More step-by-step guides on this topic: