What this guide covers
Convert week-year/week/weekday values and year/day-number values correctly. Examples cover week 53, New Year boundaries, leap days and invalid inputs.
Recognize three different date labels
A calendar date names a year, month and day, such as 2027-01-01. An ordinal date names a calendar year and a day number within that year. An ISO week date names an ISO week-year, week number and weekday. They can describe the same date while using different year labels.
Choose the converter that matches the source. The Day of Year Converter needs a calendar year and ordinal day. The ISO Week Date Converter needs all three week-date components. A week number alone is incomplete.
Use the ISO week-one anchor
ISO weeks run Monday through Sunday. Week one is the week containing January 4. Find January 4 in the entered ISO week-year, move backward to that week’s Monday, then add full seven-day groups for the later weeks.
The weekday component runs from one for Monday to seven for Sunday. To find week 10, weekday three, advance nine complete weeks from week one’s Monday and then two additional days. Keep this weekday numbering separate from programming conventions that may use zero for Sunday.
Work through the New Year boundary
January 4, 2026 falls on Sunday, so week one of ISO week-year 2026 starts Monday, December 29, 2025. Advancing 52 weeks reaches Monday, December 28, 2026, the beginning of week 53. Its fifth weekday is Friday, January 1, 2027.
| ISO week date | Calendar date | Calendar year |
|---|---|---|
| 2026-W53-1 | December 28, 2026 | 2026 |
| 2026-W53-5 | January 1, 2027 | 2027 |
| 2026-W53-7 | January 3, 2027 | 2027 |
| 2027-W01-1 | January 4, 2027 | 2027 |
The ISO week-year belongs with its week number even when the resulting calendar date has another year. Saving only “week 53 of January 2027” loses the actual week-year relationship.
Validate whether week 53 exists
An ISO week-year contains 52 or 53 full weeks. A 53rd week is not valid for every year. The converter constructs the requested date and checks its ISO week-year and week number again, rejecting a request that rolled into another week-year.
ISO week-year 2026 has week 53; ISO week-year 2027 does not. Asking for 2027-W53-1 is therefore an invalid input, not a reason to silently return a date in 2028. Use the ISO Week Number tool to inspect a known calendar date from the opposite direction.
Convert an ordinal day by counting from January 1
Ordinal day one is January 1. To locate day N, add N minus one calendar days to January 1 of the selected year. The subtraction of one matters: adding 60 days to January 1 would locate ordinal day 61 rather than day 60.
A common year has 365 valid day numbers and a leap year has 366. The converter validates the selected year before accepting the final number. It does not allow day zero, and it does not turn an invalid day 366 into January 1 of the following year.
See how the leap day changes ordinal dates
In 2027, January contributes 31 dates and February contributes 28, so day 60 is March 1. In leap year 2028, February contributes 29 dates, so day 60 is February 29 and day 61 is March 1.
The year is essential even when the day number is known. After February, the same month-and-day label has an ordinal number one larger in a leap year. Compare a specific date in the Day of the Year tool rather than relying on a common-year lookup table for every year.
Do not mix ordinal dates with other day counters
A day-of-year number starts over each January 1. It differs from a running day count since an epoch and from an astronomical Julian Date. A file labeled “Julian day” may use an informal ordinal-day meaning, so inspect the format documentation before converting it.
Leading zeros can help make an ordinal label consistent, such as year plus a three-digit day number. That formatting does not explain the calendar or counting convention by itself. Keep the source’s field definition alongside the converted date when importing records from another system.
Store complete values and check them both ways
Preserve all ISO week-date components together, or preserve the calendar year with its ordinal number. Test an ordinary midyear value and a New Year boundary value before converting an entire data set. The boundary case reveals assumptions that a midyear check can miss.
Convert the result back with the calendar inspection tools and compare the original components. The lab calculates these Gregorian labels for the selected year, including future years. Four-digit years from 0001 through 9999 are supported, with boundary validation where an ISO week date would extend outside that calendar range.
Frequently asked questions
Does week one always begin January 1?
No. It begins Monday in the week containing January 4.
Why can the two year labels differ?
ISO weeks remain complete seven-day periods across the calendar-year boundary.
Is Sunday zero?
Not in ISO week dates. Sunday is seven.
Is ordinal day 60 always March 1?
No. It is February 29 in a leap year.
Is an ordinal day a Julian Date?
No. They are different date representations; check the source terminology.
Sources and further reading
These sources explain the calendar, time-zone or published schedule conventions discussed here. Worked examples use the lab's stated calculation rules.
Python: date, duration and ISO calendar definitionsUS Naval Observatory: Gregorian leap-year rules