The YYYY-DDD ordinal date format.

What the format solves

Month-based dates are intuitive for people, but they are irregular. Months vary in length, some date formats swap the month and day, and international notation changes from one country to another. Ordinal dates remove that ambiguity by treating the year as a single numbered sequence.

That makes the format useful in operations, manufacturing, agriculture, environmental science, and internal scheduling systems where the exact position of a date inside the year matters more than its calendar month.

How to read it

The first part is the four-digit year. The second part is a three-digit day number padded with zeros on the left. So 2026-001 is January 1, 2026-032 is February 1 in a common year, and 2026-365 is December 31.

In leap years, dates after February 28 shift by one day because the year has 366 days instead of 365. That is why any reliable ordinal-date tool needs leap-year logic built in.

Where people encounter ordinal dates

Manufacturing labels often use a compressed year-plus-day code. Aviation and military operations use ordinal dates because they are compact and reduce month-day ambiguity. Data pipelines and scientific workflows use them because they sort naturally and map cleanly to year progress.

The format also sits close to what many users call a “Julian date” in logistics contexts, even though the astronomical Julian date is a different system entirely. That overlap is one reason this page exists separately from the main day-of-year hub.