Leap Year Checker

Check if a year is a leap year with detailed explanation

100% free. Runs entirely in your browser - your files and data never leave your device and nothing is uploaded to any server.

All dates and times follow your device's time zone

cancel
Not a leap year2026 · 365 days

event The next 29 February is a Tuesday in 2028 - 493 days from today.

February 202628 days
MoTuWeThFrSaSu12345678910111213141516171819202122232425262728

Leap Year Algorithm

cancel
Step 1: 2026 ÷ 4
= 506.5 → not divisible
Not a leap year. Stop.

Century map 2000-2099

25 leap years

Leap year Selected

Batch Checker

Enter multiple years, one per line.

Famous Leap Years

About this tool

A year is 365 days, except the Earth takes about 365.2422 days to orbit the Sun. Ignore that quarter-day and the calendar drifts against the seasons by roughly 24 days per century - which is exactly what happened under the Julian calendar, until by the 1500s the spring equinox had slid ten days out of place. The Gregorian reform fixed it with a three-part rule that is more subtle than most people remember. A year is a leap year if divisible by 4, unless it is also divisible by 100, unless it is further divisible by 400. That is why 2000 was a leap year and 1900 was not, despite both dividing neatly by 4 and by 100. The second exception is the part that gets forgotten, and it caused real software failures in 2000 when systems implemented only the first two rules. The remaining error is about one day in 3,000 years. Checks run in your browser.

How to use this tool

  1. Enter a yearAny year, past or future. The Gregorian rules apply from 1582 onwards, when the calendar was adopted.
  2. Read the answerLeap year or not, with the reasoning shown rather than just a yes or no.
  3. Follow the rule chainDivisible by 4, then the 100 exception, then the 400 exception - seeing which applied is the useful part.

Leap year rules, with examples

A year is a leap year if it divides by 4 - except years that divide by 100, which are not, unless they also divide by 400. So 2024 and 2028 are leap years; 1900 and 2100 are not; 2000 was.

People born on 29 February usually celebrate on 28 February or 1 March in other years.

Key features

  • Applies all three rules, including the 400-year exception most people and some software forget.
  • Explains the reasoning rather than returning a bare yes or no.
  • Works for any year, historical or far future.
  • Runs in your browser with no account.
  • Useful for checking date logic in code as well as everyday questions.

Common uses

  • Confirming whether February has 29 days in a particular year.
  • Checking date handling when writing or testing software.
  • Working out how a 29 February birthday or anniversary falls.
  • Settling the question for a historical date.
  • Explaining the rule to someone who has only heard the "divisible by 4" version.

Tips for better results

  • The full rule is three parts, not one. Divisible by 4, except centuries, except centuries divisible by 400.
  • 2000 was a leap year; 1900 and 2100 are not. Those are the examples that make the rule stick.
  • When writing date code, use your language's date library rather than implementing the rule yourself - that is where the 2000 bugs came from.
  • Leap seconds are a completely separate mechanism for a different problem, and are not part of leap year rules.
  • For dates before 1582, the Gregorian rules are applied retrospectively rather than describing what any calendar actually did at the time.

Mistakes to avoid

  • Remembering only "divisible by 4", which gets 1900 and 2100 wrong.
  • Implementing the rule by hand in code instead of using a tested date library.
  • Assuming every century year is skipped, which misses 1600, 2000 and 2400.
  • Confusing leap years with leap seconds, which correct for the Earth's rotation rather than its orbit.
  • Forgetting 29 February exists when validating date input, which is a persistent source of form bugs.

Frequently asked questions

A year is a leap year if it's divisible by 4, EXCEPT if it's also divisible by 100 - unless it's also divisible by 400, in which case it IS a leap year after all. This is why 2000 was a leap year but 1900 was not, despite both being divisible by 100.

Earth's orbit around the sun takes approximately 365.25 days, not exactly 365 - leap years add an extra day roughly every 4 years to keep our calendar synchronized with the actual solar year over long periods.

Yes. Note that the Gregorian rules were adopted in 1582, so for earlier years the answer applies the modern rule retrospectively rather than describing the calendar in use at the time.

Both are divisible by 4 and by 100, which would normally exclude them. But 2000 is also divisible by 400, and that third rule puts it back in. This is the part of the rule most often forgotten - and it caused genuine software failures in 2000 for systems that implemented only the first two conditions.

The three-rule system leaves an error of roughly one day in 3,000 years. The Julian calendar it replaced drifted about 24 days per century, which is why the equinox had slipped ten days out of place by the time of the reform.

There is no legal universal answer, and it varies by jurisdiction and organisation. Most people mark it on 28 February or 1 March, and different systems handle the edge case differently - which is itself a common source of software bugs.

Leap years fall every four years in the current period: 2028, 2032 and 2036 are leap years. The next century year skipped by the rules is 2100, which will not be a leap year.

Usually 24, because the century year itself is skipped. Every fourth century has 25, since years divisible by 400 - like 2000 - are leap years after all.

It can. An annual salary paid daily or interest calculated per day spreads over 366 days instead of 365, and some contracts specify which count to use. Check the day-count rule in your agreement.