Unit Converters

Time Converter

Convert seconds, minutes, hours and days.

Converted value

60초

Reference rate1 분 = 60 초
Note: Month (30 days) and year (365 days) are approximations; actual calendar lengths vary.
What is time unit conversion?

Time conversion translates a value between milliseconds, seconds, minutes, hours, days, weeks, months and years. This tool converts every unit through a common second (s) base so any pair can be computed instantly.

How to use it

Enter a value, choose the from and to units, and the result updates automatically. Use Swap units to flip the two selections.

Result = value × (from-unit seconds) ÷ (to-unit seconds)

Unit reference & notes

Common conversions: 1 minute = 60s, 1 hour = 3,600s, 1 day = 86,400s, 1 week = 604,800s.

For reference only: month (30 days) and year (365 days) are approximations for convenience; use the date-difference calculator for exact calendar spans.
Why a 365.2422-day year needs a 3-step leap-year rule, plus Unix time

The actual time it takes Earth to orbit the Sun (a tropical year) isn't exactly 365 days — it's about 365.2422 days. Counting every year as 365 days would accumulate roughly 24.22 days of drift per century, pushing the calendar out of sync with the seasons, so the Gregorian calendar applies a 3-step correction: ① a year divisible by 4 is a leap year (adds Feb 29), ② but one also divisible by 100 reverts to a common year, ③ unless it's also divisible by 400, in which case it's a leap year again. Applying these three steps gives the Gregorian calendar an average year length of 365 + 1/4 − 1/100 + 1/400 = 365.2425 days, narrowing the gap with the true tropical year (365.2422 days) to about one day every 3,300 years. That's exactly why 2000 (divisible by 400) was a leap year while 1900 (divisible by 100 but not 400) was not.

Computer systems, meanwhile, don't store dates in human-readable form — they use Unix time: the number of seconds elapsed since 00:00:00 UTC on January 1, 1970 (the epoch, 0). Most server logs, API timestamps and database columns use this format. Adding 86,400 seconds per day, 31,536,000 for a common year (365 days), or 31,622,400 for a leap year (366 days) to a Unix timestamp lets you compute dates directly.

Comparing year-length figures
BasisYear lengthNote
True tropical year365.2422 daysMeasured Earth orbit
Gregorian average365.2425 days365+1/4−1/100+1/400
Simple common year365 daysApproximation, no leap
Leap year366 daysAdds Feb 29
How many seconds are in a day?
A day has 86,400 seconds (60 × 60 × 24).
How many days is a month here?
For convenience, this tool approximates a month as 30 days (2,592,000 seconds). Actual calendar months range from 28 to 31 days, so use the date-difference calculator for exact spans.
How many hours are in a year?
A year (365-day basis) is 8,760 hours, or 31,536,000 seconds. Leap years (366 days) are not reflected in this approximation.
1900 is divisible by 4 — why wasn't it a leap year?
1900 is divisible by 4, but also by 100, and not by 400, so under the Gregorian calendar's 3-step rule it's a common year. 2000, on the other hand, is also divisible by 400, so it was a leap year.
What is Unix time?
Unix time counts the seconds elapsed since 00:00:00 UTC on January 1, 1970 (treated as 0). Most servers, databases and APIs store and transmit this integer instead of a human-readable date.
How far off is the Gregorian average year (365.2425 days) from the true tropical year (365.2422 days)?
The gap is about 0.0003 days (roughly 26 seconds) per year, accumulating to about one day of drift every 3,300 years — negligible for everyday date math.