When Is the Next Leap Year? The 2028 Date and the Math Behind It

The next leap year is 2028. Leap day falls on Tuesday, February 29, 2028. After that, the following leap years are 2032 and 2036. The reason is arithmetic, not astronomy alone: Earth's orbit does not divide evenly into whole days, so the calendar inserts an extra day to stay aligned with the seasons.

That answer is simple. The system that produces it is not. The leap-year rule has three nested corrections, and each one exists to fix a specific error the previous rule could not. Understanding those corrections explains why 2100 will not be a leap year, why 2000 was, and why the pattern is not the tidy four-year cycle most people learn in school.

The mechanism: why an extra day is needed

A solar year, the time Earth takes to complete one orbit around the Sun relative to the Sun's position, is about 365.2422 days. That figure is measured against the tropical year, the cycle that governs the return of the seasons. The fractional 0.2422 is the entire problem. A calendar that uses only 365 whole days drifts against the seasons by roughly one day every four years.

The Julian calendar, introduced in 45 BCE, handled this by adding one day every fourth year. That produced an average year of 365.25 days, which overshoots the tropical year by about 0.0078 days, or roughly 11 minutes per year. Small, but it compounds. By the late 16th century the drift had accumulated to about 10 days, and the spring equinox had slipped from its traditional date.

The Gregorian reform of 1582 replaced the simple four-year rule with a three-part test. A year is a leap year if it is divisible by 4, except years divisible by 100, which are not leap years unless they are also divisible by 400. That structure brings the average calendar year to 365.2425 days, within about 0.0003 days of the tropical year. The remaining error is about one day every 3,000-plus years, which is why no further correction has been adopted.

The mechanism matters because it shows the rule is a filtered count, not a single condition. Each tier removes a specific fraction of the error the tier above it leaves behind.

The arithmetic, quantified

The numbers behind the rule are small but decisive. The tropical year is approximately 365.2422 days. The Gregorian average of 365.2425 days differs by about 0.0003 days per year, or roughly 26 seconds. Over a century that is about 43 minutes; over a millennium, about 7 hours.

The three-tier filter produces a repeating 400-year cycle. Within any 400 consecutive years there are exactly 97 leap years. The count works out because 400 years contain 100 years divisible by 4, minus 4 century years that are not divisible by 400, plus 1 year (the one divisible by 400), giving 100 − 4 + 1 = 97. Multiply 97 leap days across 400 years and the average year lands at 365 + 97/400 = 365.2425 days.

Here is how the three rules compare in long-run drift:

The Revised Julian calendar, used by some Orthodox churches, applies a 900-year filter and tracks the tropical year more closely than the Gregorian rule. That is a professional caveat worth knowing: the Gregorian calendar is the civil standard, not the most precise possible design.

Edge cases: centuries, the 400 rule, and calendar boundaries

The century rule is where most predictions go wrong. Years divisible by 100 are not leap years unless divisible by 400. So 1700, 1800, and 1900 were not leap years, even though each is divisible by 4. The year 2000 was a leap year because it is divisible by 400. The next skipped century is 2100, which will not have a February 29.

This means the four-year rhythm has a visible break every century or so. Someone counting "every four years" from 2028 would incorrectly predict 2100 as a leap year. The correct sequence near that boundary is 2096, then 2104, with 2100 skipped entirely.

A second edge case involves the date line and time zones. Leap day is defined by the civil calendar in each jurisdiction, so February 29, 2028 exists everywhere the Gregorian calendar is used. Businesses operating across time zones can still misalign on payroll or contract dates if one system treats the day as invalid.

A third edge case is historical. The Gregorian calendar was adopted on different dates in different countries, and some regions used the Julian calendar for centuries afterward. Dates between 1582 and the early 20th century can therefore be ambiguous depending on jurisdiction. For modern scheduling, this is irrelevant, but for genealogy or historical research it is a real hazard.

Misconceptions and a counterintuitive detail

The most common misconception is that leap years occur strictly every four years. They do not, because of the century exception. A second misconception is that the leap day is necessary to keep the calendar from "falling behind the seasons." It actually corrects in both directions across different eras: the Julian rule overshot, and the Gregorian rule trims that overshoot.

A third misconception is that February 29 is the only place the extra day could go. Several calendar reform proposals placed the extra day at the end of December or added a leap week instead. The choice of February is historical convention, not astronomical necessity.

The counterintuitive detail: adding a leap day does not simply add 24 hours to the year. It inserts a calendar date, and the underlying timekeeping still runs continuously. The atomic clocks and time standards that govern modern systems do not pause for February 29. Leap seconds, which are a separate mechanism, are occasionally added to atomic time to keep it aligned with Earth's rotation, and they are unrelated to the Gregorian leap-day rule. Confusing the two is a common error in technical writing.

Practical actions for planning around 2028

For most people, the practical question is scheduling. A few concrete steps reduce the chance of error:

Verify the leap status of any year ending in 00 by checking divisibility by 400, not just by 4. A year like 1900 fails the test; 2000 passes. In payroll and billing systems, confirm that February 29 is treated as a valid date and that daily-rate calculations use 366 days for 2028, not 365. For contracts with annual terms, check whether the anniversary date is defined as February 28 or March 1 when the start date is February 29. These produce different results in non-leap years. When counting days between dates spanning 2028, include February 29 explicitly; a spreadsheets' serial-date functions handle this automatically, but manual counting does not. For historical research, confirm which calendar was in force in the relevant jurisdiction before treating a date as Gregorian. Red flag: any system that hard-codes a 365-day year will drift by one day against the calendar in 2028 unless it applies the leap rule dynamically.

The 2100 boundary is the one to flag in long-range planning. Any projection, depreciation schedule, or actuarial table extending past 2099 must apply the skip rule, or it will be off by one day.

Limitations: what the rule cannot fix and where precision ends

The Gregorian rule keeps the calendar aligned with the seasons to within about one day every 3,000 years, which is more than adequate for civil use. It does not track the tropical year perfectly, and it does not attempt to. The tropical year itself is not perfectly constant; it changes slowly over millennia due to variations in Earth's orbit and axial tilt. The current estimate of 365.2422 days is itself an approximation that shifts slightly across centuries.

A second limitation is that no civil calendar can satisfy both solar alignment and simple divisibility rules indefinitely. The 400-year cycle is a compromise, and proposals to improve it, such as the Revised Julian 900-year rule, exist but have not displaced the Gregorian calendar in most civil contexts. The practical consequence is that predictions beyond a few thousand years carry increasing uncertainty that has nothing to do with the arithmetic.

A third limit is definitional. "Leap year" in the Gregorian sense applies to the civil calendar. Other calendars, including the Hebrew and Chinese lunisolar systems, use entirely different intercalation rules, often adding a leap month rather than a leap day. A question about the next leap year in one system does not translate directly to another.

Finally, the timekeeping layer sits on top of the calendar. Leap seconds, which adjust Coordinated Universal Time to Earth's rotation, are decided by international bodies on an irregular schedule and are not predictable from the leap-year rule. For most scheduling purposes this is irrelevant, but it matters in precise timing applications, where the two mechanisms are often conflated.

The direct answer stands: the next leap year is 2028, with February 29 falling on a Tuesday. The deeper point is that this date emerges from a three-tier arithmetic filter, not a simple four-year cycle, and the boundary cases at 2100 and beyond are where careful planning separates correct schedules from drifted ones.