Free Day of Week Calculator Online

Day of Week Calculator: Find What Day of the Week Any Date Falls On

A day of week calculator answers one simple question precisely: given a date, what weekday was — or will — it be? Type a date into the field and the tool immediately names the weekday in large text, then backs it up with a small grid of related figures: the day-of-year count, the ISO week the date falls in, which calendar quarter it belongs to, and whether that particular year is a leap year.

The math behind it is pure calendar arithmetic done entirely in your browser — no server round trip, no account, nothing saved — using what's called the proleptic Gregorian calendar, meaning the same rules the modern Gregorian calendar uses today are projected consistently backward and forward across all dates, rather than switching to older calendar systems for historical periods. The identical weekday-lookup logic also runs as a metered API endpoint for anyone who needs the same calculation inside their own code.

How to Use the Calculator

There's just one input, and the result appears the moment it's filled in:

1. Click the date field and pick a date using your browser's native date picker, or type one directly.
2. The weekday name appears immediately in large, bold text — Sunday through Saturday — as soon as a complete, valid date is entered.
3. Below the weekday name, four smaller boxes fill in at the same time: Day of Year (shown as a count out of 365 or 366), ISO Week (formatted like "2026-W29"), Quarter (Q1 through Q4), and Leap Year (a simple Yes or No).
4. Changing the date field recalculates everything instantly — there's no separate "calculate" button to click.
5. An invalid or incomplete date simply produces no result rather than a wrong weekday, since the underlying date picker itself only allows valid calendar dates to be selected.

Why People Look Up a Specific Weekday

Knowing exactly which day of the week a date lands on comes up in a range of everyday and less-everyday situations:

• Checking whether a deadline falls on a weekend. A due date that turns out to be a Saturday often means the real, practical deadline is actually the Friday before or the Monday after, depending on the policy in play.
• Verifying a recurring meeting or event pattern. Confirming that "the second Tuesday of the month" or a similar recurring rule actually lands where you expect for a specific future month.
• Historical curiosity. Looking up which weekday a birthday, anniversary, or historical event fell on — a common trivia question that's genuinely tricky to work out in your head for dates more than a few years away.
• Travel and event planning. Confirming that a flight, hotel check-in, or ticketed event date falls on the weekday you assumed before locking in a booking.
• Programming and QA testing. Developers testing date-handling code sometimes need a quick, independent answer for what weekday a specific test date falls on, to confirm their own code's output.

How the Weekday Is Actually Calculated

The calculator parses the date you enter and works entirely in UTC calendar math rather than reading local browser-clock components back out — a distinction that matters because reading a date-only value with local getters instead of UTC ones can shift the reported weekday by a full day for anyone using a browser set to a timezone west of UTC. Two fixed reference points show the method working correctly at either end of recent history: January 1, 2000 lands on a Saturday, and July 17, 2026 lands on a Friday, both computed the same way regardless of where in the world the calculation happens to run.

Weekday	Index used internally
Sunday	0
Monday	1
Tuesday	2
Wednesday	3
Thursday	4
Friday	5
Saturday	6

That numeric index, returned by the API alongside the weekday's name, starts the week on Sunday at zero, which is the standard JavaScript convention — worth noting separately from the ISO week number shown in the same results grid, since ISO-8601 weeks themselves start counting from Monday even though this index doesn't.

The Limits of Projecting Today's Calendar Backward

"Proleptic Gregorian" is a precise but slightly technical term worth unpacking, because it comes with an honest limitation. The Gregorian calendar most of the world uses today wasn't adopted everywhere at once — some countries switched from the older Julian calendar in 1582, others not until the 20th century — and the days skipped or realigned during each region's individual switchover mean that real historical records from before a given country's adoption date were often kept in the Julian calendar, not the Gregorian one. This calculator always applies today's Gregorian rules uniformly to any date you type, including centuries-old ones, which makes it internally consistent and mathematically well-defined, but it also means a very old date's calculated weekday may not match what a historical calendar or record from that era actually showed at the time.

Why UTC-Safe Math Prevents an Off-by-One Weekday

A date-only value like "2026-07-17" carries no time-of-day or timezone information by itself — it's just a calendar date. A subtle bug shows up when code parses that string into a date object, which JavaScript actually interprets as UTC midnight on that day, and then reads the weekday back out using the browser's local timezone getters instead of the UTC ones. For anyone in a timezone west of UTC, UTC midnight on July 17th is still late in the evening of July 16th in their own local time, so a local-getter readout can report the previous day's weekday instead of the correct one — a wrong answer that only shows up for users in certain timezones, which makes it an easy bug to miss during testing done from a single location.

This calculator avoids that trap by never mixing UTC parsing with local reading: the date is parsed as UTC midnight, and every downstream figure — the weekday index, the day-of-year count, the leap-year check — is read back out using UTC getters as well, so the two stay consistent no matter which timezone the device calculating the result happens to be set to. That consistency is exactly why the two reference dates mentioned earlier produce the same weekday no matter where in the world someone opens this page to check them.

The API's Parameters and Response Fields

Calling the endpoint directly takes one required parameter, a date string in "YYYY-MM-DD" format, and returns the same figures shown on the page: the weekday name, its numeric weekdayIndex (Sunday at 0 through Saturday at 6), the dayOfYear count, and an isLeapYear boolean for that date's calendar year. Returning the numeric index alongside the weekday's name means a calling application doesn't need to build its own lookup table just to test whether a date is, say, a weekend — checking whether the index equals 0 or 6 is enough, without string-matching against day names in a particular language or capitalization.

Like the other date-based endpoints on this site, a date string that doesn't parse into a real calendar date is rejected with a descriptive error rather than silently producing a wrong or blank weekday, and every request is metered at the same flat rate no matter which century the date being checked falls in.

Figuring Out a Weekday by Hand vs. Using This Calculator

There's more than one way to work out a weekday, with varying reliability:

• Doomsday-style mental math tricks. Techniques exist for computing a weekday in your head using anchor dates and a memorized formula, genuinely fast once practiced, but easy to slip on a small arithmetic step that flips the answer without any warning.
• Counting forward on a physical calendar. Reliable for a date within the current or next year but tedious and slow for a date decades in the future or the past.
• A phone's calendar app search. Works well if the app lets you jump directly to an arbitrary date, though not every calendar app makes that jump quick or obvious.
• Zeller's congruence or a similar formula, worked out by hand. Mathematically solid, but the formula itself is easy to misremember or apply with an off-by-one month or year adjustment.
• This calculator's API. Software that needs to confirm a weekday programmatically — a scheduling validator, a form that rejects weekend-only bookings, a test suite generating fixture dates — can call the same lookup as a metered endpoint that returns the weekday name, its numeric index, day-of-year, and leap-year flag together; see the API documentation for the full parameter list.

Does this calculator account for the historical switch from the Julian to the Gregorian calendar?

No — it applies the modern Gregorian calendar's rules uniformly to every date, including ones from before 1582, rather than switching to Julian-calendar rules for older dates. That keeps the math internally consistent, but it means a very old date's result may not match a historical record kept under the Julian calendar at the time.

Why does the result also show an ISO week number and a quarter, not just the weekday?

Those figures come from the same underlying date and are useful alongside the weekday for the same lookup — knowing a date is a Friday is often paired with knowing which ISO week or quarter it falls in for reporting or planning purposes, so the calculator surfaces all of them together rather than requiring a second lookup.

Does the numeric weekday index start at Sunday or Monday?

Sunday is index 0 in this calculator's internal numbering, running through Saturday at index 6 — the standard convention used by JavaScript's date functions. That's a separate convention from ISO-8601 week numbering, which starts its own week count on Monday instead.

How exactly does the leap year flag get determined?

A year is flagged as a leap year if it divides evenly by 4, except that century years must divide evenly by 400 rather than just 100 to still count — so 2000 was a leap year but 1900 was not, and that same century-year exception is applied here rather than the simpler "divisible by 4" rule alone.

Does the calculator work just as well for a date decades in the future as for a historical one?

Yes — the proleptic Gregorian math runs the same fixed arithmetic regardless of which direction a date sits from today, so a date centuries ahead is computed with exactly the same reliability as one centuries behind. Nothing about the calculation depends on the current date or on any lookup table with a limited range.

Related Time Tools

To see which numbered ISO week a date belongs to on its own, in a copy-and-paste-friendly format, the week number calculator covers that in more depth. If you're searching for the next date a particular weekday occurs, or shifting a date by a set interval, the date pattern calculator handles that arithmetic, and the world clock is useful if the date in question also needs to line up across several timezones.