Time Converter

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

Value
From
To
1 Hour = — Minutes
Common Time Conversions
FromToResult
1 MinuteSeconds60 s
1 HourMinutes60 min
1 HourSeconds3,600 s
1 DayHours24 hr
1 WeekDays7 days
1 YearDays365.25 days
1 YearSeconds31,557,600 s
1 CenturyYears100 years

Frequently Asked Questions

A Julian year (used in astronomy) is exactly 31,557,600 seconds = 365.25 days × 24 hr × 3600 s. A calendar year has 365 days = 31,536,000 s, or 366 days in a leap year = 31,622,400 s. This converter uses the Julian year for consistency.
An average month is 365.25/12 = 30.4375 days = 2,629,800 seconds. Individual months range from 28 to 31 days. This converter uses the average month value for general purpose conversions rather than a specific calendar month.
A nanosecond is one billionth of a second (10⁻⁹ s). It is commonly used in computing — RAM access times are measured in nanoseconds, and modern CPUs execute billions of clock cycles per second. Light travels about 30 cm in one nanosecond.
A calendar year has 52 weeks plus 1 day (or 2 days in a leap year), totaling 52.18 weeks on average. A Julian year = 365.25 days / 7 = 52.1786 weeks. ISO 8601 defines the week numbering system where some years can have 53 ISO weeks.
A month averages 4.345 weeks (30.4375 days ÷ 7). Calendar months vary from 28 to 31 days, so the number of complete weeks ranges from 4 to 4.43. For payroll and financial calculations, months are often estimated as 4.33 weeks or 30 days.
A millisecond is one thousandth of a second (10⁻³ s). It is used in computing (network ping latency, mouse click response), gaming (frame render times), medicine (cardiac electrical pulses), and photography (flash duration). Human reaction time averages about 200–250 milliseconds.
A Unix timestamp is the number of seconds elapsed since January 1, 1970, 00:00:00 UTC (the "Unix epoch"). It is widely used in programming to represent points in time as a single integer. For example, 1,700,000,000 corresponds to November 14, 2023.
A UTC offset is a fixed difference from UTC (e.g., UTC+5:30 for India Standard Time). A time zone is a named region that may change its UTC offset seasonally due to Daylight Saving Time. New York is UTC−5 in winter (EST) and UTC−4 in summer (EDT).
Business days are typically Monday through Friday, excluding weekends and public holidays. In a standard week there are 5 business days. A month averages about 21–22 business days. Business day calculations matter for contracts, shipping estimates, and financial settlements (e.g., stock trades settle T+2 business days).
A Julian year has 8,766 hours (365.25 × 24). A common calendar year has 8,760 hours; a leap year has 8,784 hours. This is often relevant for electricity billing (kWh calculations), SLA uptime percentages (99.9% = ~8.76 hours of downtime/year), and annualized rate calculations.

About This Time Converter

This free time converter converts between seconds, minutes, hours, days, weeks, months, years, and more — from nanoseconds to centuries. Enter a duration in any unit and the result updates instantly.

When to use this converter

  • Converting server uptime or SLA duration metrics
  • Calculating project durations across different time units
  • Computing API timeouts, cache expiry, and scheduling intervals
  • Converting athletic race times and performance benchmarks

Standards & References

Related Converters

Speed Converter Frequency Converter Length Converter Energy Converter

Related Articles

In-depth guides and technical articles.

View all →
Converters Jul 29, 2026
UTC Is 37 Seconds Behind Atomic Time — Why Leap Seconds Exist, Why They Crash Software, and What Replaces Them After 2035
UTC and International Atomic Time (TAI) diverge by 37 seconds because Earth's rotation is slowing — atomic clocks keep perfect SI seconds, but solar noon would drift without periodic leap seconds inserted into UTC. Here's why the June 2012 leap second caused Reddit, Mozilla, and LinkedIn to go offline (a Linux kernel hrtimer bug), why GPS time is 18 seconds ahead of UTC, and why MiFID II's microsecond timestamp requirements create audit trail ambiguities around leap second boundaries.
Converters Jun 25, 2026
Why Leap Seconds Crash Websites — The Engineering Disaster That Happens Every Few Years (and Won't After 2035)
A leap second adds 23:59:60 to the clock — a second most software assumes can't exist. Here's how the 2012 Linux kernel leap second bug took down Reddit, Yelp, and LinkedIn by sending CPU usage to 100%, how Google and AWS "smear" the leap second across hours to make it disappear gracefully, and why the ITU voted in 2022 to abolish leap seconds entirely before 2035 — ending a recurring distributed systems disaster that occurs every few years.
Converters Jun 18, 2026
10,000 Hours Is 1.14 Calendar Years — But in Work Years, It's 5: Why Time Conversion Needs Context
"How long is 1,000 hours?" has an arithmetic answer (41.67 days) and a contextual answer that depends on hours per day and days per week — and two people asking the same question usually want the contextual answer. Here's why "hours to months or years" needs a working-rate input the pure conversion can't provide, the working year (2,000 hours) vs calendar year (8,760 hours) distinction for project planning, why months aren't fixed-length, and the 10,000-hours-to-mastery conversion unpacked.
Converters Jun 11, 2026
From Sundials to Atomic Clocks: How Timekeeping Precision Enabled GPS Navigation
The second was once 1/86,400 of a day. Now it's defined by caesium atom oscillations — 9,192,631,770 per second — because GPS requires nanosecond timing to achieve metre-level accuracy. Here's the history from sundials to atomic clocks, how GPS trilateration works, and why relativistic corrections are essential.
Converters Jun 10, 2026
Time Precision in Computing: Why Nanoseconds, NTP, and Leap Seconds All Matter
Nanoseconds define CPU cache speeds; milliseconds define user experience; microseconds determine whether distributed database clocks can be trusted. Here's the computing time hierarchy, NTP clock synchronisation, why leap seconds cause outages, and what P99 latency means.