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

Convert a date and time between IANA time zones with exact daylight-saving handling, inspect a zone's offset and transitions, or list a country's zones.

What it does

Convert a date and time between IANA time zones with exact daylight-saving handling, inspect a zone's offset and transitions, or list a country's zones. It runs in seconds, needs no login and no API key of your own, and can process up to 1000 items in one run (batch mode).

Examples:

• Berlin night to New York (the evening before): {"op": "convert", "datetime": "2026-03-29T01:30:00", "from_tz": "Europe/Berlin", "to_tz": "America/New_York"}
• Offset, DST flag and the neighbouring clock changes: {"op": "info", "tz": "Asia/Jerusalem", "datetime": "2026-07-01T12:00:00"}
• All time zones of the United States: {"op": "list", "country": "US"}
• A UTC instant to Japan time: {"datetime": "2026-06-15T09:00:00Z", "to_tz": "Asia/Tokyo"}

Input

Field	Type	Required	Description
op	select	no	One of: convert, info, list. Allowed: convert, info, list.
datetime	string	no	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	string	no	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	string	no	convert: target zone, an IANA name or a fixed offset. Required for convert.
tz	string	no	info: the zone to describe, an IANA name or a fixed offset (from_tz is accepted as an alias). Required for info.
country	string	no	list: ISO 3166-1 alpha-2 code, e.g. US. Omit to list every zone.
query	string	no	list: only zones whose name contains this text (case-insensitive), e.g. york or europe/
items	array	no	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:

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

Output

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.

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.

Pricing

You pay per successfully processed item (the current price is on the Pricing tab). A failed item is not charged.

Run it through the API

Python, with the apify-client package:

from apify_client import ApifyClient

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

JavaScript, with the apify-client package:

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('v0iddo/time-zone-converter').call({"op": "convert", "datetime": "2026-03-29T01:30:00", "from_tz": "Europe/Berlin", "to_tz": "America/New_York"});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

One HTTP call that waits for the run and returns the rows (for runs that finish within 5 minutes):

curl -X POST "https://api.apify.com/v2/acts/v0iddo~time-zone-converter/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"op": "convert", "datetime": "2026-03-29T01:30:00", "from_tz": "Europe/Berlin", "to_tz": "America/New_York"}'

Use it from an agent (MCP)

Claude, Cursor, VS Code and other MCP clients can call this actor as a tool through the Apify MCP server. Add it to the client's MCP configuration:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=v0iddo/time-zone-converter",
      "headers": {
        "Authorization": "Bearer <YOUR_APIFY_TOKEN>"
      }
    }
  }
}

FAQ

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.

How am I charged?

Per successfully processed item, at the price on the Pricing tab for your Apify plan. A failed item is not charged, the platform usage of the run is included, and your spending limit for a run is always respected.

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.

Something is missing or wrong. Where do I report it?

Open an issue on the Issues tab of this actor with the run link, or write to data@voiddo.com.

Other ways to use it

The same engine is also available as an API at https://data.voiddo.com and as browser tools at https://utils.voiddo.com.

Support

Questions or a case that does not work: data@voiddo.com. We answer within one business day.