Full UTC
- Input
- 2024-01-15T14:30:00.000Z
- Expected output
- Unix: 1705330200
Recommended for APIs: no timezone ambiguity.
ISO 8601 date format
ISO 8601 date format — online converter
ISO 8601 is the international standard for dates and times, widely used in REST APIs, JSON payloads, log files and HTTP headers. Understanding its structure prevents parsing errors and timezone issues.
ISO 8601 structure
- Basic format: YYYY-MM-DDTHH:mm:ss.sssZ, where T separates date from time and Z indicates UTC. Offsets are represented as ±HH:mm (e.g. -03:00 for São Paulo). Durations use P + period (e.g. P1Y2M3DT4H).
ISO 8601 variants
Safe use
- Input
- context + tool result
- Expected output
- interpreted with limits and next steps
Use the result as technical or educational support, keeping the tool limits explicit in the workflow.
Full tool FAQ
It is the number of seconds (or milliseconds in JavaScript) elapsed since 1 January 1970 at 00:00:00 UTC. Also called Epoch time or POSIX time, it is the universal format for representing time instants in computing systems.
Frequently asked questions
What is the difference between Z and +00:00?
Semantically identical — both represent UTC (zero offset). Z (Zulu) is the compact notation; +00:00 is the explicit offset notation. Most parsers accept both, but Z is preferred in JSON and REST APIs for being shorter.
Does this page replace official or professional review?
No. It helps explain the scenario and use the tool more safely, but real decisions should consider official sources, full context and qualified guidance when needed.