Time Zone Converter: IANA Zones, DST, Offsets, Batch

What you get

Each processed item adds one row to the dataset with the result fields (convert: {input, output, offset_from, offset_to, dst_from, dst_to, utc, ...}; info: {tz, offset, abbreviation, dst, previous_transition, next_transition}; list: {country, zones, count}), plus credits and ms. A failed item adds a row with error and status instead; the run fails only when every item failed.

The main fields of each row:

• # (index)
• Input time (input)
• From zone (from_tz)
• Converted time (output)
• Offset from (offset_from)
• Offset to (offset_to)
• Daylight saving at target (dst_to)
• Day change (day_offset)

Run it on Apify

1. Open time-zone-converter on Apify and sign in, or make an Apify account.
2. On the Input tab, fill in the fields listed below. The form opens with example values filled in.
3. Click Start. Rows appear on the Output tab while the run works.
4. Export the rows as JSON, CSV, Excel, XML or HTML, or read them through the Apify API.
5. To run it again on a schedule, save the input as a task and add a schedule in the Apify Console.

What you can set

• Op (op): One of: convert, info, list. Options: Convert, Info, List. Default: convert.
• Datetime (datetime): ISO 8601, e.g. 2026-03-29T01:30:00 (wall clock in from_tz / tz) or 2026-03-29T00:30:00Z / 2026-03-29T01:30:00+01:00 (exact instant). Required for convert and info.
• From Tz (from_tz): convert: source zone, an IANA name such as Europe/Berlin or a fixed offset such as +05:30. Required when datetime has no offset.
• To Tz (to_tz): convert: target zone, an IANA name or a fixed offset. Required for convert.
• Tz (tz): info: the zone to describe, an IANA name or a fixed offset (from_tz is accepted as an alias). Required for info.
• Country (country): list: ISO 3166-1 alpha-2 code, e.g. US. Omit to list every zone.
• Query (query): list: only zones whose name contains this text (case-insensitive), e.g. york or europe/.
• Batch items (items): Optional. A list of input objects with the same fields as above; every object is processed in its own right and the top-level fields act as shared defaults. Leave empty to process the single input above (up to 1000 items per run).

Example input

This is the input the actor is tested with every day.

{
  "op": "convert",
  "datetime": "2026-03-29T01:30:00",
  "from_tz": "Europe/Berlin",
  "to_tz": "America/New_York"
}

Run it from Python

The official apify-client package starts the run, waits for it and reads the rows. It needs your own Apify API token.

# pip install apify-client
from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")  # your own API token, from the Apify Console
run_input = {
    "op": "convert",
    "datetime": "2026-03-29T01:30:00",
    "from_tz": "Europe/Berlin",
    "to_tz": "America/New_York",
}
run = client.actor("v0iddo/time-zone-converter").call(run_input=run_input)
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

Limits

• Up to 5 seconds per item.
• Input size up to 4,096 bytes per item.
• URLs must be public http(s) addresses; private and local addresses are refused, robots.txt is respected where pages are fetched.
• No logins, no captcha solving, no personal-data lookups.
• Each run sends one short usage record to the developer: the Actor and run IDs, the number of results, whether the run succeeded (and if not, the kind of error, such as "blocked" or "input problem"), whether the account is on a paid Apify plan, how the run was started (for example from the Console, the API or a schedule) and a one-way fingerprint of the account (a hash, not the account ID), so that repeat runs of one account count once. It contains nothing from your input or results.

Questions

Do I need an account or an API key?

No key of your own. You only need an Apify account to start the actor.

How many items can one run process?

One item from the fields above, or up to 1,000 in items (batch mode). Each item becomes one row in the dataset.

Where are the results?

In the run's dataset: export it as JSON, CSV, Excel or HTML from the Output tab, or read it through the API.

Can I run it on a schedule or from another tool?

Yes. Save the input as a task and schedule it in the Apify Console, or start it from Make, Zapier, n8n, a webhook or the API calls above.

More

• All our scrapers on the Apify Store