2026-10-15 · 2 min read
Pick an IANA time zone before you schedule
Filter the browser's IANA zone list and copy the exact id, plus the offset that applies right now.
Key takeaways
- Copy the zone id exactly, such as America/New_York. Abbreviations like EST are not the stored value.
- The offset is the current one. It changes when daylight saving starts or ends, and this list does not show a past offset.
Workflow
Type a city, a region, or part of the id. Read the header count so you know the filter is still too wide. Copy one full id into the schedule, the handover note, or the timezone field on Timestamp Converter.
Pair that id with Cron Parser when the schedule is a cron expression. The parser explains the fields. It does not apply a zone or compute the next run. The zone id is what makes 09:00 mean the same clock for the next person.
Limits
Names come from Intl.supportedValuesOf("timeZone") in the runtime that executes the tool. An older runtime can expose a shorter list than a current one.
The offset is formatted for the current instant. A job that crosses a daylight-saving change needs a calendar. This snapshot will not show both offsets.
What this tool does not do
It does not remember a preferred zone, and it does not rewrite cron expressions.
It does not treat POSIX abbreviations as ids. If a teammate writes EST, look up America/New_York or the zone you actually mean, and store that string.
FAQ
Why do I only see 200 zones?
An empty box lists the first 200 names and prints how many exist in total. Type a region or city, such as Europe or Kolkata, to narrow the match. The cap stays 200 rows.
Does this convert a Unix timestamp?
No. It only lists zone ids and the current short offset. Use Timestamp Converter when you need a clock time in that zone.