Today's Date and Time

Because "today" depends on local time zone. If it is already past midnight in one country but not in another, the calendar date will differ even though both places are correct locally. This page uses your device's current local time, so the answer reflects where you are right now.

Today's date in numbers is 2026-07-15 in ISO 8601 (YYYY-MM-DD), 07/15/2026 in US format (MM/DD/YYYY), and 15/07/2026 in European format (DD/MM/YYYY). ISO 8601 is the safest for software, databases, spreadsheets and international use because it sorts correctly as plain text and has no month/day ambiguity.

The clocks use your device's local system time and time-zone settings. That means the answer updates automatically when your phone or computer crosses midnight, changes time zone, or adjusts for daylight saving time. If you need another city's current time, use the world clock section below or the Time Zone Converter.

Today's Julian Day Number is shown in the format panel above — a continuous count of days used in astronomy and spaceflight. It's different from the 5-digit "Julian date" (YYDDD) stamped on food and pharmaceutical packaging. The Julian Date page shows both for today, converts any date in either direction, and explains when each format is used.

Under ISO 8601, weeks start on Monday and week 1 is the week containing the year's first Thursday — which is why early-January dates can belong to the previous year's week 52 or 53. The current week number is shown in the cards above; the Weeks in a Year page covers the full rules, including which years have 53 weeks.

A leap year has 366 days instead of 365, with the extra day added as February 29. The rule: divisible by 4, unless also divisible by 100, unless also divisible by 400. The "Week / Leap" card above shows the next leap year; the Next Leap Year page has a live countdown to the upcoming February 29, the next 20 leap years, and why the rule exists.

The seven-day week is one of the few time units with no astronomical basis (unlike days, months, or years). It originates with Babylonian astronomers, who grouped days by the seven "wandering stars" visible to the naked eye — the Sun, Moon, Mercury, Venus, Mars, Jupiter and Saturn. Those assignments survive in English weekday names via Roman and Germanic tradition: Saturday/Saturn, Sunday/Sun, Monday/Moon, then Tiw (Tuesday), Woden (Wednesday), Thor (Thursday) and Frigg (Friday). Several civilisations have tried to replace the seven-day week — revolutionary France had a 10-day week, the Soviet Union experimented with 5- and 6-day weeks in the 1930s — but all reverted.

Three conventions dominate: MDY (03/04/2026 = March 4) used in the US; DMY (03/04/2026 = 3 April) used in most of Europe, Latin America and much of Asia; and YMD (2026-03-04) used in China, Japan, Korea and the ISO 8601 international standard. The US convention likely traces to 18th-century British usage that Britain itself later abandoned. For anything cross-border — databases, schedules, filenames, international forms — ISO 8601 (YYYY-MM-DD) is the safest: it sorts correctly as plain text and has no ambiguity.

GMT (Greenwich Mean Time) is a time zone — the civil time in the UK during winter. UTC (Coordinated Universal Time) is a time standard, the reference against which all other zones are defined. They are almost identical in everyday use: UTC = GMT to within a second, always. The difference is how they're maintained. GMT is based on Earth's rotation and the position of the Sun over Greenwich; UTC is atomic-clock time, nudged occasionally with leap seconds to stay aligned with GMT. UTC officially replaced GMT as the world's time reference in 1972.

A Unix timestamp is the number of seconds elapsed since January 1, 1970, 00:00:00 UTC — a single integer that doesn't depend on time zones, DST, or locale, which is why nearly every programming language and database uses it. The current timestamp is shown in the "Today at a Glance" panel above; the Unix Timestamp Converter converts any timestamp to a date and back, with code snippets for JavaScript, Python, and PHP.

Most time zones are offset from UTC by whole hours, but not all. India (UTC+5:30) chose a single national offset at independence in 1947 rather than split the country into two zones. Nepal (UTC+5:45) is aligned to Kathmandu's actual solar time. Iran (UTC+3:30), Afghanistan (UTC+4:30), Myanmar (UTC+6:30) and parts of Australia (UTC+9:30 for South Australia, UTC+8:45 for Eucla) use other half- and quarter-hour offsets. The most unusual is the Chatham Islands (UTC+12:45). These exist because time zones are ultimately political decisions — countries pick the offset that best fits their geography, economy, and neighbours.

The one-hour shift is arbitrary — early proposals (including Benjamin Franklin's 1784 satirical letter and William Willett's 1907 pamphlet) suggested smaller, gradual shifts. When Germany became the first country to adopt DST in 1916, it picked a single one-hour change for simplicity, and every subsequent country followed. A handful of regions have experimented with 30-minute shifts (Lord Howe Island in Australia still does) but these are exceptions. Not every country observes DST — most of Asia, Africa and South America keep a single offset year-round, as do Arizona and Hawaii in the US.