Seconds in a Year

There are 31,557,600 seconds in an average Gregorian year (365.25 days × 86,400 seconds/day). Non-leap years have 31,536,000 seconds; leap years have 31,622,400. The Microapp page also includes a converter — enter any duration in any unit and get the second-equivalent instantly. Useful for time-budget calculations, programming with timestamps, or just satisfying curiosity.

One year =
31,557,600 seconds
Gregorian-average year (365.25 days × 86,400 seconds/day). Non-leap year: 31,536,000 sec; leap year: 31,622,400 sec.
Convert any duration to seconds
1 year = 31,557,600 seconds
Quick reference
UnitSeconds
1 minute60
1 hour3,600
1 day86,400
1 week604,800
1 month (avg)2,629,800
1 year (Gregorian avg)31,557,600
1 non-leap year (365 d)31,536,000
1 leap year (366 d)31,622,400
1 decade (10 yr)315,576,000
1 century (100 yr)3,155,760,000
1 millennium (1000 yr)31,557,600,000

How to use

  1. 1

    The headline answer (31,557,600 seconds in a year) is at the top.

  2. 2

    Use the converter below to translate any duration to seconds. Pick a unit (minutes, hours, days, weeks, months, years) and enter the count.

  3. 3

    Reference the table at the bottom for at-a-glance second-equivalents of standard time units.

Frequently asked questions

Ratings & Reviews

Rate this tool

Sign in to rate and review this tool.

Loading reviews…

The Headline Answer

31,557,600 seconds in a year (using the Gregorian-average year of 365.25 days). For most practical purposes, this is the number to use.

If you need precision for a specific year:

  • Non-leap year (365 days): 365 × 86,400 = 31,536,000 seconds
  • Leap year (366 days): 366 × 86,400 = 31,622,400 seconds
  • Gregorian-average year (365.2425 days, accounting for the 400-year cycle): 31,556,952 seconds — the most accurate, but rarely necessary
Worked example. A typical human lifespan of 80 years is roughly 80 × 31,557,600 ≈ 2,524,608,000 seconds — about 2.5 billion. Each second is one heartbeat (more or less); each year is about 31.5 million heartbeats; a lifetime is about 2.5 billion. Most resting heart rates are 60-80 bpm, so this checks out.

Why 365.25 (Not Exactly 365)?

Earth orbits the Sun in approximately 365.2422 days. To keep our calendar from drifting against the seasons, we have leap years — but the simple "every 4 years" rule slightly over-corrects (it would average to 365.25 days, slightly longer than the real 365.2422).

The Gregorian calendar (introduced 1582) fixed this by adding a refinement: leap years happen on years divisible by 4, EXCEPT century years (1700, 1800, 1900...) which are NOT leap years UNLESS they're also divisible by 400 (so 1600, 2000, and 2400 ARE leap years, but 1700, 1800, 1900 weren't). This averages to 365.2425 days/year — much closer to the real 365.2422.

For most time-budget calculations (how long is X years in seconds?), 365.25 is fine — the error vs the precise Gregorian average is about 13 seconds per century.

The Standard Time-Unit Equivalents

UnitSecondsNotes
1 minute60Always exact
1 hour3,60060 × 60
1 day86,40024 × 3,600 (excluding leap seconds)
1 week604,8007 × 86,400
1 month (avg)2,629,800365.25 × 86,400 ÷ 12
1 year (avg)31,557,600365.25 × 86,400
1 decade315,576,00010 × year
1 century3,155,760,000100 × year
1 millennium31,557,600,0001,000 × year

What About Leap Seconds?

Earth's rotation isn't perfectly constant. Tidal friction, atmospheric drag, and tiny shifts in the planet's mass distribution change rotation speed by milliseconds per day. Atomic clocks (used for UTC) don't account for this naturally — so since 1972, occasional leap seconds have been inserted to keep UTC within 0.9 seconds of UT1 (mean solar time).

Leap seconds are added at the end of June 30 or December 31 when needed. Between 1972 and 2025, 27 leap seconds have been added. The most recent was June 30, 2015. The international community voted in 2022 to phase out leap seconds by 2035 — the irregular adjustments cause too many problems for distributed computer systems.

For programming and most calculations, ignore leap seconds. The error from omitting them is at most 27 seconds across 53 years — negligible for nearly any application.

Why You Might Care

Programming with timestamps. Unix timestamps count seconds since 1970-01-01 UTC. Converting between human-readable durations and second-counts is daily work for backend developers. Knowing a year is 31,557,600 seconds lets you reason about timestamp arithmetic intuitively ("31 million seconds ≈ 1 year").

Time-budget thinking. If you have one hour to learn something, that's 3,600 seconds. A 16-hour day = 57,600 seconds of waking time. A year of waking time = ~21 million seconds. Reframing time in seconds sometimes makes priorities feel sharper.

Physics and astronomy. The speed of light × seconds in a year = 1 light-year (about 9.46 × 10¹⁵ meters). Astronomical distances are typically in light-years for this reason — multiply by ~31.5 million seconds/year and you have the distance in light-seconds.

Curiosity. "How many seconds in a year?" is one of the most-searched curiosity questions on Google for a reason — it's a satisfyingly large but graspable number. About 31.5 million.

Related Tools

For computing the number of days between two specific dates, use the Days Between calculator. For more granular time arithmetic (adding hours, minutes, days, etc.), see the Date Time Calculator. For converting Unix timestamps to human-readable dates, the Unix Timestamp Converter handles those.