# Time Zone Converter and World Clock (`mangudai/time-zone-converter`) Actor

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.

- **URL**: https://apify.com/mangudai/time-zone-converter.md
- **Developed by:** [Mangudäi](https://apify.com/mangudai) (community)
- **Categories:** Developer tools, Open source, Travel
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.01 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Time Zone Converter and World Clock

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:

```json
{
  "datetime": "2026-07-10T09:00:00",
  "sourceTimezone": "America/New_York",
  "targetTimezones": ["America/New_York", "Europe/London", "Asia/Tokyo", "Australia/Sydney"]
}
```

### 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.

# Actor input Schema

## `datetime` (type: `string`):

The moment to convert, as ISO 8601 (for example 2026-07-10T09:00:00) or the word now for the current instant. If the value has no offset, it is read in the source time zone below.

## `sourceTimezone` (type: `string`):

IANA time zone the date and time above is expressed in, for example UTC, America/New\_York, or Europe/Paris. Used only when the value has no offset.

## `targetTimezones` (type: `array`):

IANA time zones to convert to. One row is returned per zone. Leave as is for a world clock across the major hubs.

## `includeAllTimezones` (type: `boolean`):

Add a row for every IANA time zone, a full world snapshot of about 350 zones for the chosen instant.

## Actor input object example

```json
{
  "datetime": "now",
  "sourceTimezone": "UTC",
  "targetTimezones": [
    "UTC",
    "America/Los_Angeles",
    "America/New_York",
    "America/Chicago",
    "America/Sao_Paulo",
    "Europe/London",
    "Europe/Paris",
    "Europe/Moscow",
    "Asia/Dubai",
    "Asia/Kolkata",
    "Asia/Singapore",
    "Asia/Shanghai",
    "Asia/Tokyo",
    "Australia/Sydney",
    "Pacific/Auckland"
  ],
  "includeAllTimezones": false
}
```

# Actor output Schema

## `results` (type: `string`):

One row per target time zone with local time, UTC offset, and DST status.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("mangudai/time-zone-converter").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("mangudai/time-zone-converter").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call mangudai/time-zone-converter --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=mangudai/time-zone-converter",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/BAZUndhMgBXLBSooB/builds/30K5pZuRTmfXehcxn/openapi.json