Blucalculator Open Tool

Time Unit Converter

Convert time between nanoseconds, seconds, minutes, hours, days, weeks, months, years, and centuries.

Embed This Calculator

Copy the code and paste it into any webpage to embed this calculator.

WordPress users: add a Custom HTML block (not the Embed block) and paste the code there.

More embed options

Free to use. A small "Powered by Blucalculator" credit is appreciated but not required.

How to use this calculator

Three inputs. The result shows multiple equivalents at once.

Time value is the number you’re converting. Type it in the field. Decimals work. Very large and very small numbers work too, though the output may display in scientific notation for anything beyond a few orders of magnitude.

From unit is your source unit. The dropdown covers: Nanosecond (ns), Microsecond (µs), Millisecond (ms), Second (s), Minute (min), Hour (hr), Day, Week, Month, Year, Decade, Century.

To unit is your target. Same list.

Click Calculate and the blue results panel shows the converted value plus a breakdown across the most common units: seconds, minutes, hours, days, and years all displayed at once. Scientific notation (like 2.778e-4) appears for very small numbers; that’s 0.0002778, meaning 1 second is 0.0002778 hours.

The Duration Scale below the results uses a log-scale bar chart to show your input and output alongside each other. Because time spans 20+ orders of magnitude from nanoseconds to centuries, a log scale is the only way to meaningfully visualise the relative sizes.

Example: converting 1 second to all units

Time value: 1 / From unit: Second

Results panel shows:

  • Seconds: 1
  • Minutes: 0.0167
  • Hours: 2.778e-4 (0.0002778)
  • Days: 1.157e-5 (0.00001157)
  • Years: 3.169e-8 (0.0000000317)

One second is a tiny fraction of a year (about 1/31.5 million), but a very large number of nanoseconds (1 billion of them).

Scientific notation in the output (like 1.157e-5) means move the decimal point 5 places to the left: 0.00001157. The calculator uses this format to keep small numbers readable rather than printing a long string of leading zeros.


What the duration scale shows

The Duration Scale section is a log-scale bar chart. This needs a brief explanation because log scales are unfamiliar to most people.

On a normal scale, 10 and 20 are the same distance apart as 1,000 and 1,010. On a log scale, each step represents a 10× increase. So the distance from 1 to 10 is the same as the distance from 1,000 to 10,000.

Time units span such extreme ranges that a normal scale is useless. If you drew seconds and years on a linear chart, years would be so far to the right that seconds would be invisible. The log scale compresses the enormous range so you can see where every unit sits relative to every other.

The bars for each unit (seconds, minutes, hours, days, years) show proportional length on this log scale. A full bar means the current input value. A tiny sliver means the converted value is tiny relative to the input. It’s a visual answer to “how much bigger is X than Y?”


The formulas

All conversions go through seconds as the base unit. Every unit has a fixed number of seconds, and the calculator converts by dividing through seconds.

Result = (Input × seconds_per_input_unit) / seconds_per_output_unit

The seconds-per-unit values:

1 nanosecond = 0.000000001 seconds (10⁻⁹)
1 microsecond = 0.000001 seconds (10⁻⁶)
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 month = 2,629,800 seconds (average: 365.25 days / 12)
1 year = 31,557,600 seconds (365.25 days)
1 decade = 315,576,000 seconds
1 century = 3,155,760,000 seconds

Month conversions use an average month of 30.4375 days (365.25 / 12). Real months vary from 28 to 31 days. For anything requiring calendar-accurate month counting (contract durations, billing cycles, age calculations), use the actual calendar dates rather than this calculator’s approximation.


Seconds to all time units: full conversion table

SecondsMinutesHoursDaysWeeksYears
10.01670.0002780.00001160.000001653.17e-8
6010.016670.0006940.00009921.90e-6
600100.16670.006940.0009921.90e-5
3,6006010.041670.005950.000114
86,4001,4402410.142860.002738
604,80010,080168710.01916
2,629,80043,830730.530.444.3480.08333
31,557,600525,9608,766365.2552.181
315,576,0005,259,60087,6603,652.5521.810
3,155,760,00052,596,000876,60036,5255,218100

Hours, minutes and seconds: the everyday range

The conversions people reach for most often.

HoursMinutesSecondsDays
0.25159000.01042
0.5301,8000.02083
1603,6000.04167
1.5905,4000.0625
21207,2000.08333
318010,8000.125
424014,4000.16667
636021,6000.25
848028,8000.33333
1272043,2000.5
241,44086,4001
482,880172,8002
724,320259,2003
16810,080604,8007

Days, weeks, months and years

DaysWeeksMonths (avg)Years
10.14290.032850.002738
710.22990.01916
1420.45980.03833
304.2860.98560.08214
30.444.34810.08333
608.5711.9710.16427
9012.862.9570.24641
18025.715.9140.49281
365.2552.18121
730.5104.36242
1,826260.9605
3,652.5521.812010
36,5255,2181,200100

The small end: nanoseconds, microseconds, milliseconds

Used in computing, electronics, and physics. These numbers are counterintuitive because they’re so small.

UnitSecondsNanosecondsMicrosecondsMillisecondsContext
1 nanosecond10⁻⁹10.0010.000001One CPU clock cycle at 1 GHz
1 microsecond10⁻⁶1,00010.001WiFi packet timing, camera flash
1 millisecond0.0011,000,0001,0001Audio sample at 1 kHz, blink duration
10 ms0.0110,000,00010,00010Human reaction time (lower bound)
100 ms0.1100,000,000100,000100Perceptible audio/video lag
250 ms0.25250,000,000250,000250Average human reaction time
1 second11,000,000,0001,000,0001,000Heartbeat (60 BPM)

Time at scale: perspective on large numbers

Some durations people frequently need to convert or contextualise.

DurationSecondsWhat it means
1 minute60
1 hour3,600
1 day86,400
1 week604,800
1 month (avg)2,629,800
1 year31,557,600~31.6 million seconds
4 years126,230,400US presidential term, Olympic cycle
10 years315,576,000~316 million seconds
18 years568,036,800Age of majority in most countries
75 years2,366,820,000Average human lifespan (developed world)
100 years3,155,760,000~3.16 billion seconds
1,000 years31,557,600,000A millennium
1 million years3.156 × 10¹³Geological epoch
Age of universe~4.35 × 10¹⁷~13.8 billion years

Real-world examples

Software timing: API timeout

A developer sets a network request timeout at 30,000 milliseconds. Is that reasonable?

API timeout in human terms

From unit: Millisecond / To unit: Second

30,000 ms = 30 seconds

That’s an unusually long timeout for a web API. Most production systems use 3,000-10,000 ms (3-10 seconds). 30 seconds would leave users staring at a loading spinner for half a minute before seeing an error. Typical REST API timeouts: 5,000-15,000 ms.

Project management: sprint planning

A software team works in 2-week sprints. A project is estimated at 6 months. How many sprints is that?

Sprints in a project

6 months = 6 × 30.44 days = 182.6 days

1 sprint = 14 days

Sprints = 182.6 / 14 = 13.04 sprints, so 13 full sprints

In practice, a 6-month project has 13 sprints with a small buffer, or 12 sprints and a 2-week release/stabilisation period at the end.

Physics: speed of light across distances

Light travels at 299,792,458 m/s. How long does it take to travel from the Sun to Earth (~150 million km)?

Light travel time: Sun to Earth

Distance: 150,000,000 km = 150,000,000,000 m Speed of light: 299,792,458 m/s

Time = 150,000,000,000 / 299,792,458 = 499.9 seconds

From unit: Second / To unit: Minute

499.9 seconds = 8.33 minutes

Light from the Sun takes about 8 minutes 20 seconds to reach Earth. When the Sun “disappears” from our sky, it already disappeared 8 minutes ago.

Loan duration: mortgage in seconds

A 30-year mortgage. How many seconds is the borrower committed for?

30-year mortgage in seconds

30 years × 365.25 days × 24 hours × 3,600 seconds

= 30 × 31,557,600 = 946,728,000 seconds

Nearly 1 billion seconds. Put another way: signing a 30-year mortgage commits you for 947 million heartbeats (at 60 BPM).

Computing: billion operations per second

A processor runs at 3 GHz (3 billion cycles per second). How long does each cycle take?

CPU cycle duration

Frequency: 3,000,000,000 Hz

Period = 1 / 3,000,000,000 = 0.000000000333 seconds

From unit: Second / To unit: Nanosecond

= 0.333 nanoseconds per cycle

In that 0.333 ns, light travels about 10 cm. Every CPU clock cycle, the processor completes more instructions than light travels across a hand.


Common mistakes people make

Assuming 1 month = 30 days exactly. Months are 28, 29, 30, or 31 days. The calculator uses 30.44 days (365.25 / 12) as an average. For anything involving actual calendar dates (lease expiration, subscription billing, contract terms), count the specific calendar days rather than using an average.

Mixing up milliseconds and microseconds. Millisecond (ms) = 1/1,000 of a second. Microsecond (µs) = 1/1,000,000 of a second. They’re 1,000× apart. In computing contexts, latency specs and timing requirements bounce between both. A 100 µs response time is 0.1 ms, which is very fast. A 100 ms response time is 100,000 µs, which is perceptible to a user.

Not accounting for leap years. A year isn’t exactly 365 days. The Gregorian calendar uses 365.2425 days per year on average (the calculator uses 365.25, which is close but not exact). Over long periods this matters: the difference between 365 and 365.25 is 1 day every 4 years, which compounds to 25 days per century.

Treating “business days” as regular days. 10 business days is not 10 days. It’s 14 calendar days (assuming a 5-day work week with no holidays). Project timelines and legal deadlines often specify business days. The calculator converts calendar time; business day calculations require separate logic.

Reading scientific notation wrong. The calculator output shows values like 3.169e-8 for very small numbers. This means 3.169 × 10⁻⁸ = 0.00000003169. The negative exponent tells you how many places to move the decimal point to the left. 1e-3 is 0.001. 1e-6 is 0.000001. Each step of 3 in the exponent is a 1,000× change.

Sidereal time vs solar time: a day is not exactly 86,400 seconds if you’re doing astronomy. A sidereal day (relative to the stars) is 86,164 seconds. A solar day (relative to the Sun) is 86,400 seconds. For everyday use, 86,400 is correct. For orbital mechanics and telescope tracking, the 236-second difference matters enormously.


How different fields think about time

Each discipline has a “natural” time unit that everything else is measured relative to.

FieldPrimary time unitWhy
Computing / electronicsNanoseconds, clock cyclesCPU speeds and signal timing
Audio engineeringMilliseconds, samplesLatency and sample rate (44,100/s)
Human perceptionMilliseconds (10-500 ms)Reaction time, perceptible lag
Sports timingMilliseconds, hundredthsRace results and photo finishes
Everyday lifeMinutes, hoursScheduling and duration
Project managementDays, weeks, sprintsPlanning and milestones
Finance and contractsDays, months, yearsInterest periods, terms
Biology / medicineSeconds, minutes, yearsHeart rate, drug half-life, age
Geology / evolutionThousands to millions of yearsStratigraphic periods
Astronomy / cosmologyLight-years, billions of yearsCosmic distances and timescales

A light-year is a distance, not a time. It’s the distance light travels in one year: about 9.461 × 10¹² km. The “year” in light-year refers to the travel time used to calculate the distance. Don’t enter light-years as a time value into a time converter.


The bottom line

Time units span 26 orders of magnitude from nanoseconds to the age of the universe. No other measurement category covers that range in everyday use. The calculator handles all of it and shows multiple equivalents simultaneously so you’re not running conversions one at a time.

For everyday use (hours, minutes, seconds, days), the conversions are simple enough to do mentally with the table. For anything involving milliseconds, nanoseconds, or decades and centuries, just enter the value and read the result.

The one thing to remember: months are approximate. If a deadline or contract matters, count calendar days.

Frequently Asked Questions

How many seconds are in a year?

A Julian year (365.25 days) contains 31,557,600 seconds. A common calendar year of 365 days contains 31,536,000 seconds. The extra 0.25 day accounts for leap years.

How many minutes are in a day?

There are exactly 1,440 minutes in a day (24 hours × 60 minutes/hour).

How many hours are in a week?

There are exactly 168 hours in a week (7 days × 24 hours/day).

How many milliseconds are in a second?

There are exactly 1,000 milliseconds in 1 second. Higher-resolution time units include microseconds (1,000,000 per second) and nanoseconds (1,000,000,000 per second).

How long is a decade and a century?

A decade is exactly 10 years. A century is exactly 100 years. A millennium is 1,000 years. This calculator uses a Julian year (365.25 days) for consistent conversion.

How many days in a month on average?

The average month is approximately 30.4375 days (365.25 ÷ 12 = 2,629,800 seconds). Actual calendar months range from 28 to 31 days, so use this average for general conversions.