Seconds Converter (sec to min, hr, day, year)

Article — Seconds Converter (sec to min, hr, day, year)

Seconds converter: time unit conversions explained

The second is the SI base unit of time, defined exactly by 9,192,631,770 transitions of the caesium-133 atom. From seconds you can derive every other time unit: 60 s = 1 minute, 3600 s = 1 hour, 86,400 s = 1 day, 604,800 s = 1 week, 31,557,600 s = 1 Julian year. Going smaller: 1 ms = 10⁻³ s, 1 µs = 10⁻⁶ s, 1 ns = 10⁻⁹ s.

The second's odd-looking definition (9.192 billion transitions) was chosen in 1967 to match the existing astronomical second, which had been defined as 1/86,400 of a mean solar day. The atomic definition is stable to about one second per 60 million years — vastly better than Earth's rotation, which varies by milliseconds daily.

Seconds: the SI base time unit

One of seven SI base units (alongside metre, kilogram, ampere, kelvin, mole, candela). Defined since 1967 by the caesium-133 atomic transition. Modern SI reaffirms this in the 2019 redefinition: the second is whatever makes the caesium frequency ΔνCs exactly 9,192,631,770 Hz. Every other time unit derives from the second by a fixed factor.

The advantage of the atomic definition is reproducibility. Any laboratory with a caesium atomic clock can independently realise the second to ~10⁻¹⁵ accuracy. The astronomical second varied with the Earth's rotation, which speeds up or slows by milliseconds per day depending on geophysical effects (tides, earthquakes, ice melt).

Seconds to minutes and hours

60 seconds make one minute. 60 minutes make one hour. So 3600 seconds = 1 hour. The base-60 (sexagesimal) division is inherited from Babylonian astronomy via the Greeks. Sixty has more divisors than ten (1, 2, 3, 4, 5, 6, 10, 12, 15, 20, 30, 60), which is why minutes split cleanly into halves, thirds, quarters, fifths, sixths and tenths.

• 1 minute = 60 seconds
• 1 hour = 3,600 seconds = 60 min
• 1 day = 86,400 seconds = 24 hours
• 1 week = 604,800 seconds = 7 days
• 1 month (avg) ≈ 2,629,800 seconds
• 1 year (Julian) = 31,557,600 seconds
• 1 year (Gregorian) ≈ 31,556,952 seconds
• 1 century ≈ 3,155,760,000 seconds

Seconds to days and weeks

One day is exactly 86,400 seconds — by definition, ignoring leap seconds. One week is 604,800 seconds. These are the units software and science use for time intervals longer than an hour and shorter than a year. Months are awkward because they vary in length (28-31 days); database designs usually store months as 30-day approximations or compute them from calendar dates.

How many seconds in a year

The number depends on which year. A common (non-leap) year has 365 × 86,400 = 31,536,000 seconds. A leap year (366 days) has 31,622,400. The Julian year (365.25 days, used by astronomers) is 31,557,600. The Gregorian year (365.2425 days on average, the calendar most countries use) is 31,556,952.

For most software and engineering work, 31,536,000 (365 days) is good enough. Astronomers use the Julian year. Climatologists and demographers sometimes use the tropical year (365.24219 days), which is the time from one vernal equinox to the next.

Sub-second time units

Below one second the metric prefixes take over. Millisecond (ms) = 10⁻³ s; microsecond (µs) = 10⁻⁶ s; nanosecond (ns) = 10⁻⁹ s; picosecond (ps) = 10⁻¹² s; femtosecond (fs) = 10⁻¹⁵ s. Each step down opens new technological domains.

Unix epoch time in seconds

Unix epoch time is the number of seconds since 1970-01-01 00:00:00 UTC, not counting leap seconds. It's the dominant timestamp format in operating systems, databases and web APIs. As of January 2026 the epoch is around 1.77 × 10⁹ seconds — a 10-digit decimal number for at least another century.

The famous "year 2038 problem" arises because 32-bit signed integers overflow at 2,147,483,647 seconds past epoch — January 19, 2038. Modern systems use 64-bit integers, pushing the next overflow billions of years into the future. Legacy embedded firmware is a different story.

Caesium-133 and the atomic second

The SI second is defined by the resonance frequency of an unperturbed caesium-133 atom at its ground-state hyperfine transition: exactly 9,192,631,770 Hz. Counted out, one second corresponds to that many wave cycles. The choice of caesium reflects its sharp, easily-measured resonance and low sensitivity to perturbations.

Caesium fountain clocks at NIST and similar national laboratories achieve fractional accuracy near 10⁻¹⁶. Optical lattice clocks using strontium or ytterbium do even better (10⁻¹⁸ to 10⁻¹⁹). The next SI redefinition of the second is widely expected to use an optical-frequency standard rather than caesium.

Leap seconds and time keeping

UTC (Coordinated Universal Time) inserts leap seconds occasionally to keep clock time aligned with the Earth's rotation. Since 1972, 27 leap seconds have been added (always positive). The last was on 2016-12-31. The International Telecommunication Union has voted to abolish leap seconds by 2035 because of the complications they cause for software systems.

For most calculations the difference is negligible — 27 seconds spread over 50 years. But for GPS, financial trading and precise astronomy, leap seconds matter. GPS time runs about 18 seconds ahead of UTC (as of 2026) and doesn't include leap seconds. TAI (International Atomic Time) is unbroken; UTC differs from TAI by an integer number of leap seconds.

The decision to abolish leap seconds reflects the cost in software complexity. Distributed systems handle "second 60 of minute 59" inconsistently — some smooth it across a day, some skip it, some duplicate it. Google's "leap smear" spreads the extra second over 24 hours so no individual clock tick is unusual. The 2035 cutoff gives the world time to adapt without surprise.