People talk about Friday, August 28, 2026, week 35 or 2:30 p.m. Software needs representations precise and regular enough to store, compare and exchange those values.
Two formats are especially common: the ISO week number, useful for organizing calendars by week, and the Unix timestamp, widely used by software systems and APIs.
They both describe time, but they solve different problems.
What is an ISO week?
ISO 8601 defines a consistent way to number weeks. In this system, the week begins on Monday and ends on Sunday. Weeks are numbered from 1 to 52, and sometimes 53.
The year attached to an ISO week can differ from the calendar year for a few days around New Year.
The ISO Week Number Calculator takes a date and returns its week number, ISO week-year, and the Monday and Sunday dates for that week.
Why can the ISO year differ from the calendar year?
January 1 always belongs to the new calendar year, but it can still belong to the last ISO week of the previous week-year.
Likewise, some final days of December may belong to week 1 of the following ISO year.
A useful way to remember the rule is that ISO week 1 is the week containing the year’s first Thursday.
For weekly dashboards, sprint numbers, logistics and data exports, keep the ISO week number and ISO year together. Writing only “week 1” is ambiguous.
Why do some years have week 53?
A calendar year contains 365 days, or 366 in a leap year. Fifty-two weeks contain 52 × 7 = 364 days.
One or two days therefore remain, and depending on their position in the calendar, some ISO years have a 53rd week.
Do not assume every year ends at week 52.
What is a Unix timestamp?
A Unix timestamp represents time as a number counted from a conventional origin: January 1, 1970 at 00:00:00 UTC, often called the Unix epoch.
Numbers are convenient for software to store, sort, compare and transmit.
The Timestamp Converter converts a Unix timestamp to a readable date and performs the reverse conversion.
Seconds or milliseconds: a critical distinction
Not every system uses the same precision.
Classic Unix timestamps are commonly expressed in seconds since the Unix epoch. Many environments, including JavaScript, commonly use milliseconds.
The factor is 1,000. A millisecond value therefore generally has three additional digits compared with the same instant expressed in seconds.
Confusing these units can produce a date very far from the expected value. Always check the unit expected by an API, database or file format.