Week Number Calculator — ISO 8601 & US week finder

A week number calculator answers a question that comes up constantly in business, manufacturing, and project planning: "what week is this?" — and the answer depends on which convention you're using. This tool gives you both the internationally standardized ISO 8601 week number and the more casual US week number convention for any date, along with the day-of-year count and how many days remain before the year ends. It also works in reverse: give it a year and an ISO week number, and it tells you the exact Monday-through-Sunday date range that week covers.

Arb Digital built this free tool because week numbers show up everywhere — payroll cycles, manufacturing date codes, fiscal reporting, ISO date stamps on product packaging, academic calendars, and project timelines — and the two common conventions genuinely disagree with each other several times a year, which causes real confusion if you're not sure which one a document or system is using.

What This Week Number Calculator Does

Enter any date and the tool immediately calculates its ISO 8601 week number (the standard used across Europe, in most enterprise software, and in international business), its US week number (the convention more common in American calendars and some U.S. business software), the date's position in the year as a day count from 1 to 365 or 366, and the number of days left until December 31. Switch to the reverse lookup, enter a year and a week number, and the tool returns the exact start and end dates of that ISO week.

How to Use the Week Number Calculator

1. Pick any date using the date field and click Find Week Number.
2. Read the results: the main figure shows the ISO week number, with the US week number, day-of-year, and days-remaining shown alongside it.
3. Switch to reverse lookup by entering a year and an ISO week number in the bottom fields.
4. Click Find Dates for This Week to see the exact Monday-through-Sunday date range that week covers.
5. Use both directions together — for example, confirm a date's week number, then look up the surrounding weeks to plan a project timeline.

How ISO 8601 Week Numbering Actually Works

The ISO 8601 standard, maintained by the International Organization for Standardization, defines a week as always running Monday through Sunday, and defines "week 1" of any year as whichever week contains that year's first Thursday. Equivalently, week 1 is the week that contains January 4th, since January 4th always falls within the first ISO week by definition. This rule has a perhaps-surprising consequence: the first few days of January can actually belong to the last ISO week (week 52 or 53) of the previous year, if January 1st falls on a Friday, Saturday, or Sunday — because in that case, the Monday that starts the new week comes after January 1st, and the days before it still belong to the tail end of the prior year's final week. You can review the full technical definition directly from the standard's maintainers via the ISO 8601 official reference.

Because of this Thursday-anchored rule, most years have 52 ISO weeks, but years where January 1st falls on a Thursday (or leap years where it falls on a Wednesday) end up with 53 ISO weeks instead. This tool calculates the correct week number for any date by working out which Thursday of that calendar week falls in which year, following the standard algorithm exactly, so it correctly handles these year-boundary edge cases rather than just dividing the day-of-year by seven.

ISO Week Numbers vs. the US Week Convention

The convention more commonly used in American calendars and some U.S. business contexts defines week 1 simply as the week containing January 1st, and treats Sunday (not Monday) as the first day of the week. This sounds like a small difference, but it produces genuinely different week numbers for the same date in many years. For example, if January 1st falls on a Wednesday, the ISO standard might place that date in week 1 of the new year (since the week's Thursday, two days later, is still in the new year), while the US convention also calls it week 1 but counts the days Sunday-through-Saturday instead of Monday-through-Sunday — meaning the boundaries of "week 1" itself land on different calendar dates under each system. This tool calculates both independently so you can see exactly how they diverge for your specific date, rather than assuming they always agree (they don't, several times most years).

Knowing which convention a system uses matters in practice: enterprise resource planning (ERP) and manufacturing systems frequently use ISO week numbers for date codes on product batches and quality-control records, since it's an unambiguous international standard, while some U.S. retail and payroll calendars use the simpler Sunday-first convention because it matches how most American wall calendars are printed.

Why Week Numbers Matter in Business and Manufacturing

Manufacturers frequently stamp products with a "week code" (sometimes combined with the year, like "2403" for week 3 of 2024) instead of a full date, because it's compact and still gives quality control and recall teams enough precision to trace a batch to a specific production period. Retailers and supply chain teams plan promotional calendars, inventory cycles, and staffing around week numbers rather than individual dates, since a 52-week fiscal year divides cleanly into quarters and reporting periods that a month-based calendar doesn't align with as neatly (calendar months vary from 28 to 31 days, while weeks are always exactly 7). Project managers running sprint-based or agile workflows often label sprints by week number for the same reason: it's a consistent, unambiguous unit that doesn't shift depending on how many days are in a given month.

Payroll is another common place week numbers show up quietly in the background. Many hourly payroll systems calculate overtime and pay periods against ISO week boundaries rather than calendar months, because a week is a fixed, unambiguous unit of exactly seven days everywhere in the world, while "the month" varies in length and even in which weekday it starts on from one month to the next. A biweekly payroll cycle built around ISO weeks always covers exactly fourteen days no matter which two weeks are chosen, which keeps overtime calculations, holiday pay, and shift differentials consistent from one pay period to the next — something a straightforward "1st through 15th" calendar split can't guarantee once weekends and holidays are factored in.

The Notorious Edge Case: 2021-01-01 and ISO Week 53

One of the clearest illustrations of how the Thursday-anchored rule can surprise people is January 1st, 2021. Instinctively, most people assume the first day of a new year automatically belongs to "week 1" of that year — but under the ISO 8601 standard, January 1st, 2021 actually falls in week 53 of 2020, not week 1 of 2021. That's because January 1st, 2021 was a Friday, and the ISO week containing it runs from Monday, December 28th, 2020 through Sunday, January 3rd, 2021. Since the Thursday of that week (December 31st, 2020) still falls within 2020, the entire week — including January 1st and 2nd, 2021 — is attributed to the previous ISO year's final week rather than the new year's first one. Enter that exact date into the calculator above and you'll see it confirmed directly: the tool correctly reports ISO week 53 with an ISO week-year of 2020, exactly matching the standard's rule, rather than incorrectly starting a fresh "week 1" the moment the calendar flips to January.

This particular case is a useful one to remember because it demonstrates why a naive approach — such as simply dividing a date's day-of-year number by seven — produces the wrong answer at year boundaries. Software, spreadsheets, and reports that don't correctly implement the Thursday rule will often mislabel the first few days of a new year, which can cause a manufacturing batch code, a payroll period, or a report heading to disagree with a system that calculates it correctly elsewhere. When two systems that are each supposed to be using "the ISO week number" disagree on the same date, this end-of-December edge case is one of the first places to check.

Common Mistakes to Avoid

• Assuming ISO and US week numbers always match. They frequently don't, especially in the first and last weeks of the year — always confirm which convention a system or document is using.
• Forgetting that some years have 53 ISO weeks. Dividing day-of-year by seven and rounding doesn't reliably produce the correct ISO week number — the Thursday-anchored rule has to be applied properly.
• Mixing up which day starts the week. ISO weeks start Monday; the US convention typically starts Sunday — this shifts every date's position within "its" week.
• Treating January 1st as automatically "week 1." Under the ISO standard, January 1st can actually belong to the final week of the previous year, depending on what day of the week it falls on.
• Using week numbers alone for legal or contractual dates. Always pair a week number with the actual calendar date range for anything binding, since week numbering conventions can differ between parties.

Related Free Tools From Arb Digital

Pair this with our Business Days Calculator to plan workdays within a given week, or explore our Barcode Generator and Text-to-Speech tool for other free utilities. Browse our full free online tools hub for more calculators like this one.

Frequently Asked Questions

This tool runs entirely in your browser using built-in JavaScript. Nothing you enter is uploaded, stored, or sent to any server.