🗓️ Calendar

How to Use This Calendar

A perpetual calendar shows any month in any year, so you can check past dates, plan future ones, and settle every "what day was that" debate. Pick a month and year, or step forward and back with the Prev and Next buttons. The grid shows weekdays, highlights today when visible, and lists week numbers.

How the Calendar Math Works

Every calendar app does the same underlying arithmetic: given a month and year, find the weekday of the 1st, then lay out the days. The leap year rule is the only tricky part, and it exists because the solar year is 365.2425 days, not 365. The Gregorian reform tuned the rule so the calendar drifts only one day every few thousand years. JavaScript\'s Date object encodes all of this, which is what powers the grid above.

Worked Example

Select October 2026. The 1st falls on a Thursday, the month has 31 days, and it spans 5 calendar weeks. Halloween, October 31, lands on a Saturday, which is why 2026 is a good year for parties. Step back to February 2028 with the Prev button twelve times, or just select it: 2028 is divisible by 4 and not a century year, so February has 29 days. The grid adjusts automatically, which is the whole point of doing this with a tool instead of memory.

Practical Uses for a Perpetual Calendar

Project planning is the big one: pick the deadline month, see the weekday layout, and count back real working days instead of guessing. Event planning runs on the same logic; checking whether the 15th is a Saturday takes two seconds here. Genealogy and anniversaries need past dates, which phone calendars handle poorly beyond a few years. And the classic use: verifying old claims. "The meeting was the second Tuesday of March 2019" is checkable in one lookup, and being right about dates is a quiet superpower.

Calendar Quirks Worth Knowing

Months do not divide evenly into weeks, which is why monthly schedules always look lopsided. A 31-day month starting on Saturday touches six different week rows, the maximum. ISO week numbers, shown in the grid, are the European business standard where week 1 is the week with the first Thursday. And if you ever need the same calendar layout again, most years repeat every 5, 6, or 11 years: 2026\'s layout returns in 2037. Wall calendar publishers know this; now you do too.

A Second Worked Example: The Friday the 13th Hunt

From October 16, 2026, the next Friday the 13th is November 13, 2026, less than a month away. Step the calendar to November 2026 and there it is: the 13th falls on a Friday. The one after that: February 13, 2027 is a Saturday, March 13 a Saturday, so the next Friday the 13th after November is August 13, 2027. Friday the 13th comes in clusters because of how the weekday cycle interacts with month lengths; some years have one, some have three.

This is the perpetual calendar's party trick: any recurring date question, "when is the next...," "what day was...," answered in seconds. Birthdays, anniversaries, deadlines, and superstitions all run on the same grid.

Why February Has 28 Days

February got the short straw from Roman politics. The early Roman calendar had only ten months starting in March; January and February were added later by King Numa Pompilius around 700 BCE. Romans considered even numbers unlucky, so months got 29 or 31 days, and February, the month of purification rituals, took the leftover 28. When Julius Caesar reformed the calendar in 45 BCE, February kept its short length while the leap day landed there too.

The Gregorian reform of 1582 kept the structure and fixed the drift with the century rule: divisible by 100 is not a leap year unless also divisible by 400. That is why 2000 was a leap year and 1900 was not. The calendar you are looking at is the product of two thousand years of patching, and February is where all the patches show.

Common Calendar Mistakes

First: the century trap. Divisible by 4 is the rule most people learn; the century exception is the one they forget. 1900 was not a leap year, 2000 was. Software written by people who forgot this had a bad February in 2000. Second: week numbering. ISO weeks start Monday and week 1 contains the first Thursday; US calendars often start Sunday. The same date can sit in different week numbers depending on the system.

Third: "30 days hath September" misremembered. The knuckle trick works if you learn it right; the rhyme works if you recite it fully. Fourth: assuming the weekend. Some countries start the week on Monday, some on Sunday, and business calendars in parts of the Middle East run Sunday to Thursday. Fifth: the missing days of 1582. When the Gregorian calendar launched, ten days were skipped outright; historical dates in that window need care, which is why historians specify Old Style or New Style.

The 400-Year Cycle Nobody Notices

The Gregorian calendar repeats exactly every 400 years. That is the whole trick of the leap-year rule: years divisible by 4 are leap years, except century years, which must be divisible by 400. Over 400 years that gives 97 leap days, and 400 years is exactly 146,097 days, which is divisible by 7. So January 1, 2000 fell on a Saturday, and January 1, 2400 will too. Any perpetual calendar is really just this cycle plus an offset. Programmers love this fact; it means date math can be done with modular arithmetic instead of lookup tables, and it is why your phone never needs a calendar update.

Worked Example: What Day Was the Moon Landing?

July 20, 1969 was a Sunday. You can verify it with Zeller's congruence, but the doomsday method is faster by hand. The doomsday for 1969, the weekday of the last day of February, was Friday. In any year, July 11 is a doomsday (7/11, easy to remember), so July 11, 1969 was a Friday, and July 20 was nine days later, a Sunday. Check it against the famous footage: Mission Control's clocks and the Sunday newspaper headlines the next morning both agree. The method works for any date once you know the year's doomsday, which is three facts to memorize per century, not per year.