Time Zone Converter and World Clock
Pricing
from $0.01 / 1,000 results
Time Zone Converter and World Clock
Convert any time across IANA time zones and get a world clock in one run. Each row gives the local time, UTC offset, DST status, zone abbreviation, weekday, and Unix timestamp. Fully offline, no API and no key, so it never breaks on a rate limit or a site change.
Pricing
from $0.01 / 1,000 results
Rating
0.0
(0)
Developer
Mangudäi
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
Convert a single moment into local time across as many IANA time zones as you want. Give it a date and time and a source zone, and it returns one row per target zone with the local time, the UTC offset, whether daylight saving is active, the zone abbreviation, and the Unix timestamp. Ask for every zone and you get a full world clock snapshot for that instant.
It runs fully offline. The time zone data comes from the IANA database bundled through Python's zoneinfo and the tzdata package, so there is no API to call, no key to manage, and nothing to rate limit. That makes it reliable in a way that scrapers of clock websites are not.
What you can do with it
Plan a meeting time and see it at once in New York, London, Bangalore, and Sydney. Build a world clock for a dashboard. Check whether a city is on daylight saving right now. Turn a naive timestamp from a log file into the correct wall clock time for each office. Feed the clean table straight into a spreadsheet, a database, or another Actor.
Input
| Field | Type | Default | Notes |
|---|---|---|---|
| datetime | string | now | ISO 8601 such as 2026-07-10T09:00:00, or now for the current instant. A value with no offset is read in the source zone. |
| sourceTimezone | string | UTC | IANA name the input is expressed in, for example America/New_York. |
| targetTimezones | array | 15 major hubs | IANA zones to convert to. One row per zone. |
| includeAllTimezones | boolean | false | Add a row for every IANA zone, about 350 in total. |
Example input:
Output
One row per target zone. For the example above, 9:00 in New York during summer maps to 14:00 in London, 22:00 in Tokyo, and 23:00 in Sydney.
| Field | Meaning |
|---|---|
| targetTimezone | IANA name of the zone |
| localDatetime | Local time as ISO 8601 with offset |
| localDate | Local calendar date |
| localTime24h | Local time, 24 hour |
| localTime12h | Local time, 12 hour with AM or PM |
| dayOfWeek | Weekday name in the target zone |
| abbreviation | Zone abbreviation such as EDT, BST, JST |
| utcOffset | Offset from UTC as +HH:MM |
| utcOffsetHours | Offset as a number of hours |
| isDST | True when daylight saving is active |
| hoursFromSource | Hours ahead of or behind the source zone |
| unixTimestamp | Seconds since the Unix epoch |
| sourceTimezone | The source zone you supplied |
| utcDatetime | The same instant in UTC |
Results are stored in the dataset and shown in the Time zones table view. Export to JSON, CSV, or Excel, or read them through the API.
How it handles daylight saving
Offsets and abbreviations come from the IANA rules for each zone at the exact instant you convert. A time in July shows EDT for New York and GMT stays GMT for London in January. The isDST flag tells you when a zone is on summer time, so a converted meeting time is correct for the season, not just the standard offset.
Notes
Zone names follow the IANA convention, Area/City, like Europe/Paris or Asia/Kolkata. An unknown name does not stop the run; that row carries an error message instead so the rest of the table still comes through.
