Date & Time
ISO 8601 Converter
Parse and create ISO 8601 date/time values.
ISO 8601 Converter tool
Loading tool…
Jump to a section
About This Tool
Convert ISO 8601 timestamps into practical UTC, local-time, offset, and Unix representations, or build a normalized UTC ISO value from a local date, time, and selected timezone. It is useful for API debugging, scheduled jobs, logs, test fixtures, and any workflow where a timestamp must represent one exact moment instead of an ambiguous wall-clock time.
How To Use It
- Choose whether to parse an existing ISO 8601 value or build one from local date/time fields.
- When parsing, paste a complete timestamp such as 2026-08-20T14:30:00Z or one with an explicit offset such as 2026-08-20T20:00:00+05:30.
- When building, enter the local date and time, then choose the timezone those fields belong to.
- Review the normalized UTC ISO string, UTC display, local display, Unix seconds, and UTC offset.
- Copy the normalized ISO string when you need a portable timestamp for code, APIs, logs, or fixtures.
Examples
Check an API timestamp
Paste a value like 2026-08-20T14:30:00Z to see the equivalent UTC display, local-time display, Unix seconds value, and offset label.
Create a timestamp for testing
Build a valid ISO value from local date, local time, and timezone fields before adding it to a request, fixture, or scheduled job.
Normalize an offset timestamp
Paste 2026-08-20T15:30:00+05:30 to get the equivalent normalized UTC value, 2026-08-20T10:00:00.000Z.
Useful Notes
Offset handling
ISO strings with Z are treated as UTC. Strings with an explicit offset are converted from that offset into one normalized instant, so two different-looking timestamps can represent the same moment.
Building from local time
Build mode treats the entered date and time as wall-clock time in the selected timezone, then converts that moment to a UTC ISO string. This is safer than manually adding or subtracting offsets, especially around daylight saving changes.
Unix seconds
Unix seconds are counted from 1970-01-01T00:00:00Z. They represent the same instant as the normalized ISO value, just in a compact numeric form used by many APIs and databases.
Validation
Parse mode accepts the common extended ISO form with a calendar date, T separator, hours and minutes, and either Z or an explicit numeric offset. It rejects impossible calendar values, timezone-free timestamps, date-only values, and non-ISO prose so copied output always identifies one exact instant.
FAQ
What does the Z mean in an ISO timestamp?
Z means the timestamp is in UTC, also called Zulu time.
Can ISO 8601 include a timezone offset?
Yes. Values can end with Z for UTC or an explicit offset such as +05:30, and both forms represent an exact moment in time.
Why does the copied value end with Z?
The copied value is normalized to UTC. The Z suffix means the timestamp represents that exact instant in UTC, even if the original input used another offset or was built from a local timezone.
Should I paste a date-only value?
No. Parse mode requires a complete date and time with Z or an explicit offset because a date alone does not identify one exact instant. Use build mode when you want to combine local date and time fields with a named timezone.
Does the converter change the moment in time?
No. Parsing mode converts the same instant into different representations. Build mode creates an instant from the local date, time, and timezone you choose.