Leap Years and Leap Seconds: What’s the Difference?

Introduction

A leap year and a leap second sound like two versions of the same correction. They are related, but they solve different problems. A leap year keeps the calendar broadly aligned with Earth’s trip around the Sun by adding February 29. A leap second has been used to keep the time standard used by clocks close to the changing rotation of Earth. One adjusts the date; the other adjusts the count of seconds. Understanding the difference reveals why our everyday calendar is not a perfect astronomical clock and why modern timekeeping needs both astronomy and highly stable clocks. This guide explains the rules, the history, the practical consequences and the limits of each adjustment.

1. Why calendars need corrections

A calendar gives people whole-number dates. Earth’s orbit and the cycle of seasons do not fit neatly into a whole number of days. The seasonal cycle commonly described by the tropical year is approximately 365.2422 days. If a calendar year always had 365 days, the calendar would fall behind the seasons by roughly a quarter of a day each year.

That difference seems small. It is not small when it accumulates. After four years, the drift is close to one day. Over many decades, seasonal dates would move noticeably through the calendar. A date that is expected to fall near the beginning of spring in the Northern Hemisphere would gradually occur earlier relative to the calendar.

The leap-year system corrects most of this mismatch by adding a day at intervals. It does not make every calendar year identical to the astronomical year. Instead, it makes the average length of the calendar year close enough for civil purposes over long periods.

2. The Gregorian leap-year rule

The Gregorian calendar, the civil calendar used in most of the world, uses a rule that is easy to apply:

1. If a year is divisible by 4, it is normally a leap year.
2. If it is divisible by 100, it is not a leap year.
3. If it is also divisible by 400, it is a leap year after all.

Examples make the exception clearer:

• 2024 was a leap year because it is divisible by 4 and is not a century year.
• 1900 was not a leap year because it is divisible by 100 but not by 400.
• 2000 was a leap year because it is divisible by 400.
• 2100 will not be a leap year because it is divisible by 100 but not by 400.

This rule creates 97 leap days in every 400-year cycle. The average Gregorian year is therefore 365.2425 days. That is very close to the approximate tropical-year length, although not an exact match. The remaining difference is tiny on a human timescale but can accumulate over thousands of years.

3. Why February has 29 days

The extra day is placed at the end of February. The choice is historical rather than an astronomical requirement that February must be the month to change. The Roman calendar underwent several reforms, and February’s length and position were shaped by those earlier arrangements. The Julian calendar, introduced under Julius Caesar, established a regular leap day every four years. The Gregorian reform later refined the rule by excluding most century years.

In a leap year, February has 29 days instead of 28. The year has 366 days rather than 365. People born on February 29 are sometimes called leap-day babies, although legal rules for birthdays and age-related deadlines depend on the jurisdiction.

A leap day is a calendar convention. It does not mean Earth suddenly takes an extra day to orbit the Sun every fourth year. The extra date is a way of distributing the fractional part of the seasonal year across the calendar.

4. What a leap second is

A leap second is a one-second adjustment to Coordinated Universal Time, usually abbreviated UTC. UTC is the international time standard that underpins civil timekeeping, broadcasting, navigation and many computer systems. It is based on atomic time but is kept close to a time scale associated with Earth’s rotation.

Atomic clocks measure time using extremely stable physical transitions in atoms. Earth’s rotation, however, is not perfectly uniform. It changes slightly due to a range of physical processes, including interactions within the Earth and gravitational effects involving the Moon and Sun. As a result, the time kept by atomic clocks and the time associated with Earth’s rotation do not progress at precisely the same rate.

Historically, leap seconds were inserted when needed to keep UTC within a defined range of UT1, a time scale based on Earth’s rotation. A positive leap second made the final minute of a selected UTC day contain 61 seconds. In principle, a negative leap second could remove a second, making a minute contain 59 seconds, although no negative leap second has been used.

Unlike leap years, leap seconds do not follow a simple repeating calendar rule. They are based on observed differences and international decisions. You cannot look at a year divisible by four and predict a leap second from that fact.

5. Who decides when a leap second is needed?

Leap seconds are coordinated internationally through the timekeeping system associated with the International Earth Rotation and Reference Systems Service (IERS). The service monitors Earth-orientation data and publishes announcements about adjustments to UTC. National measurement laboratories, including the US National Institute of Standards and Technology, explain how the system works and how leap seconds affect timekeeping.

The important point is that leap seconds are not inserted because a calendar says so. They are announced based on the relationship between atomic time and Earth rotation. This makes them less predictable for ordinary scheduling than leap days.

The system has also been debated because a one-second change can be awkward for software and infrastructure. Computer systems may handle the extra second differently. Some repeat or slow a second; others use a technique called “smearing,” spreading the adjustment over a longer period. Different handling can cause systems to disagree temporarily if they are not designed carefully.

6. Why leap seconds can cause technical problems

For a person looking at a wall clock, one extra second is almost invisible. For computer systems that assume every minute contains exactly 60 seconds, it can be a real engineering challenge.

Potential issues include:

• Time stamps: Software may need a clear way to represent the unusual second.
• Distributed systems: Servers that disagree about how to handle the adjustment can produce inconsistent logs or ordering.
• Scheduling: Systems that calculate exact intervals need to distinguish clock time from elapsed time.
• Data processing: Financial, scientific and operational records may rely on precise time stamps.
• Synchronization: Networks and devices need a consistent policy for receiving and applying time updates.

This is one reason many software engineers prefer to use monotonic clocks for measuring elapsed time. A monotonic clock is designed to move forward steadily and is not intended to display civil date and time. If you want to measure how long a task takes, a stopwatch is conceptually closer to elapsed-time measurement than a calendar clock. ClownClock’s guide to stopwatch vs timer explains that everyday distinction.

7. Are leap seconds going away?

The future of leap seconds has been under international discussion because keeping civil time close to Earth’s rotation must be balanced against the technical cost of irregular adjustments. In 2022, the General Conference on Weights and Measures (CGPM) agreed to increase the permitted difference between UTC and UT1 in or before 2035. The 2026 CGPM then made the next step more specific: its Resolution 5 states that continuous UTC will become effective on 20 May 2027, with the permitted difference between UT1 and UTC set at up to 3,600 seconds. In practical terms, this is intended to end the need for future leap-second steps in UTC from that date, while allowing the difference from Earth-rotation time to grow and be published for users who need it.

As of the date this article was prepared, November 2026, that transition had been decided but had not yet taken effect. Until 20 May 2027, systems should follow the current official timekeeping announcements and their documented leap-second handling. After the transition, check BIPM and IERS guidance for how UT1-UTC information is provided. Do not assume that a leap second will occur in a particular year unless an official announcement confirms it.

8. Leap year vs leap second: the essential difference

The two adjustments have a similar purpose at a broad level: they help keep human timekeeping connected to astronomical reality. But they operate at different scales.

A leap year corrects the calendar’s relationship to the seasonal cycle. It adds a full date, February 29, according to a predictable rule. A leap second historically corrected the relationship between atomic time and Earth-rotation time. It adjusted the UTC second count when needed, according to measurement and announcement.

Think of a calendar as a map of days and a clock as a measure of hours, minutes and seconds. The map needs an occasional extra square to keep the seasons in roughly the right place. The clock system may need a one-second adjustment to remain close to the rotating Earth. One does not replace the other.

If you want to see how the basic clock display turns counted intervals into hands and numbers, read how analog clocks work. For the wider history of changing official clock rules, see the history of daylight saving time.

This article is for general information and is not medical or professional advice.