Download Time Calculator
Estimate how long a file download will take based on file size and connection speed. Supports all common file size and speed units.
Format any date and time as an ISO 8601 string. Enter year, month, day, hour, minute, second and get the properly formatted ISO date string.
Common year (365 days) | UTC offset: Z
| Format | Example | Common Use |
|---|---|---|
| Extended Date-Time | 2026-03-12T14:30:00Z | APIs, databases, JSON |
| Basic Date-Time | 20260312T143000Z | File names, compact logs |
| Date Only | 2026-03-12 | Date fields, reports |
| Time Only | 14:30:00+00:00 | Time-of-day values |
| Week Date | 2026-W11-4 | Scheduling, fiscal weeks |
| Ordinal Date | 2026-071 | Julian day, scientific logs |
| With Offset | 2026-03-12T09:30:00-05:00 | Local-time context |
| UTC (Zulu) | 2026-03-12T14:30:00Z | Universal reference |
The ISO 8601 Date Formatter generates properly formatted ISO 8601 date-time strings from individual date and time components. ISO 8601 is the international standard for date and time representation, universally used in APIs, databases, data interchange, and technical documentation.
The format follows the pattern YYYY-MM-DDTHH:mm:ssZ, where T separates date and time, and Z indicates UTC. For example, 2026-02-08T14:30:00Z represents February 8, 2026 at 2:30 PM UTC. This unambiguous format eliminates confusion caused by regional date formats like MM/DD/YYYY vs DD/MM/YYYY.
This calculator lets you enter each component separately and generates the correctly formatted string, including validation of month and day ranges. It's invaluable for developers building APIs, data engineers formatting records, and anyone who needs to produce standards-compliant date strings.
ISO 8601 is the standard date format for APIs, databases, and data interchange. Manually constructing these strings is easy to get wrong because of zero-padding requirements and separator rules. This formatter generates correct ISO strings so your dates stay standards-compliant.
ISO 8601 Format: YYYY-MM-DDTHH:mm:ssZ
Where:
YYYY = four-digit year
MM = two-digit month (01โ12)
DD = two-digit day (01โ31)
HH = two-digit hour (00โ23)
mm = two-digit minute (00โ59)
ss = two-digit second (00โ59)
T = date-time separator
Z = UTC timezone designatorResult: 2026-02-08T14:30:00Z
The components year=2026, month=02, day=08, hour=14, minute=30, second=00 are assembled into the ISO 8601 string 2026-02-08T14:30:00Z. The T separates date from time, and Z indicates UTC.
Regional date formats cause errors worldwide. Americans write March 4 as 03/04, while Europeans write it as 04/03. ISO 8601's YYYY-MM-DD format eliminates this confusion entirely. Major technology companies, international standards bodies, and governments recommend ISO 8601 for all date interchange.
Beyond the basic date-time format, ISO 8601 supports: week dates (2026-W06-1 for Monday of week 6), ordinal dates (2026-039 for the 39th day of 2026), durations (P3Y6M4DT12H30M5S), and time intervals (start/end or start/duration).
ISO 8601 is used by HTML5 date inputs, XML Schema, JSON APIs, SQL databases (as text representation), and most programming languages' standard libraries. When building any system that stores or transmits dates, ISO 8601 should be the default format.
Last updated:
ISO 8601 is an international standard for representing dates and times. It was first published in 1988 and uses the format YYYY-MM-DDTHH:mm:ssZ. Its unambiguous format makes it the preferred choice for data interchange between systems worldwide.
ISO 8601 eliminates ambiguity in date representation. Is 03/04/2026 March 4th or April 3rd? Depends on regional conventions. But 2026-03-04 is always March 4th. This clarity is critical when systems exchange data across regions.
The letter T is a separator between the date portion (YYYY-MM-DD) and the time portion (HH:mm:ss). It indicates where the date ends and the time begins. Some systems accept a space instead of T, but T is the standard.
Z stands for Zulu time, which is another name for UTC. When a date-time string ends with Z, it means the time is in UTC. If a local time offset is needed, replace Z with +HH:MM or โHH:MM.
Yes. ISO 8601 allows date-only strings like 2026-02-08, week dates like 2026-W06, and ordinal dates like 2026-039. The full date-time format is just one of several valid representations.
JSON does not have a native date type, so dates are typically serialized as ISO 8601 strings. This is the de facto standard in REST APIs, GraphQL, and most modern web services. JavaScript's JSON.stringify uses ISO 8601 for Date objects.
Estimate how long a file download will take based on file size and connection speed. Supports all common file size and speed units.
Check DST rules by region and year. See when clocks spring forward and fall back, plus the UTC offset used during each daylight saving period.
Convert time between any two time zones using UTC offsets. Enter a time and source/target UTC offsets to see the equivalent local time.