Somewhere in a project plan you'll find a cell that says "Week 27" and a stakeholder who asks what that means in terms of actual dates. If your company uses a European or ISO reporting cadence — manufacturing, logistics, finance, government contracting — week numbers show up as naturally as dates do elsewhere. And getting them wrong by a week at a year boundary has real consequences: reports filed late, sprint boundaries that drift, compliance windows that close before you thought they did.
There's a sharp gotcha lurking here: "first week of the year" is not defined the same way by every system. The ISO 8601 standard — the one used across the EU, most of Asia, and in any context that says "ISO week" — defines Week 1 as the week containing the first Thursday of the Gregorian year. Equivalently, it's the week that contains January 4th. Weeks start on Monday and run ISO-year 2024 Week 1 from Monday January 1, 2024 (since January 1, 2024 was a Monday). But if January 1 falls on a Friday, Saturday, or Sunday, those early days belong to the last week of the previous ISO year — which could be Week 52 or 53 of the year before. December 29–31 can similarly fall into Week 1 of the following ISO year. That's correct, consistent, and deeply counterintuitive the first time you hit it.
The US convention (and the default in Excel's WEEKNUM without arguments) anchors Week 1 to the week containing January 1st, with weeks starting on Sunday. A third common variant keeps Monday starts but still anchors to January 1. These three systems disagree by a week at the start of roughly one year in five — enough to matter whenever a "Week 53" exists in ISO and not in the US system, or vice versa.
This tool takes any date and returns its ISO week number (01–53), the ordinal day within that Monday-to-Sunday week, and the full Monday–Sunday range of that ISO week. It also shows the US-convention week number in parallel so you can see when they diverge. In the other direction, enter a year and week number and get the Monday and Sunday dates that bound that ISO week — useful for setting sprint start dates or fiscal report windows.
The 53-week question trips people up regularly. A year has 53 ISO weeks when January 1 falls on a Thursday, or on a Wednesday in a leap year. This happens about every five to six years, and it's the answer to "why does our 52-week rolling total have an orphan week at the end of this year?" in financial reporting pipelines. The tool flags 53-week years explicitly.
Real situations where this matters: a German team filing reports in "KW 53" while their US colleagues already consider Week 1 of the new year, a developer writing a cron job that fires on Monday and needing to log the ISO week number for audit purposes, an accounting team reconciling month-end vs week-end closing rules across calendar systems, a manufacturer whose Kanban cadence is keyed to ISO week numbers, a teacher planning a semester that crosses a year boundary where January straddles two week-years, and an API that returns {"week": 53, "year": 2023} for December 31 — which looks like a bug but is actually correct ISO behavior.