Tool
UTC ISO 8601 Builder
Build an unambiguous ISO 8601 timestamp from a date and a city, with copy-ready variants for logs and APIs.
What makes this different
The DST awareness is the differentiator. If the chosen date and time does not exist (spring forward) or is ambiguous (fall back), the tool flags it before producing the timestamp.
How to use it
- Pick a city.
- Pick a date and time (local in that city).
- Read the four formats and copy whichever your stack needs.
The hardest part of writing a log line that includes a timestamp is making sure the reader knows which timezone you meant. ISO 8601 with an explicit offset solves this. This tool takes a date and a city, and emits the standard formats (ISO 8601 with offset, RFC 3339, Unix epoch in seconds and milliseconds), each with a "copy" button.
Frequently asked questions
What is the difference between ISO 8601 and RFC 3339?
RFC 3339 is a strict subset of ISO 8601, designed for use in internet protocols. Most APIs accept either. The tool emits both.
Why is the offset sometimes a Z (UTC)?
Because the timestamp you entered is the same as UTC for the chosen city at the chosen date — e.g. London in winter.
What if my time is in the spring-forward gap?
The tool flags it as "non-existent" and asks you to choose the next valid wallclock time. Most software stores the actual UTC instant anyway, but the displayed local time would be ambiguous.