Timezone Converter

Convert datetimes between any timezones in bulk — IANA names, UTC offsets, and common abbreviations all supported. Get UTC offsets, DST status, and day of week for every result.

What does Timezone Converter do?

Timezone Converter converts datetime values between any two (or more) timezones in a single run. You provide a list of conversion requests, and the actor returns the converted datetime for each target timezone along with the UTC offset, DST status, and day of the week.

Key capabilities:

• 🕐 Bulk conversions — convert dozens or hundreds of datetimes in one run
• 🌍 All timezone formats — IANA names (America/New_York), UTC offsets (+05:30), abbreviations (EST, JST, CET)
• ⏰ Current time — use "now" as the datetime to get the current time in any timezone
• 📅 Multi-target — convert one datetime to many target timezones at once
• 📋 Three output formats — ISO 8601, human-readable, or Unix timestamps

The fastest way to try it: open the actor on Apify Store, click Try for free, and run the pre-filled example input — it converts a sample datetime to four timezones in under a second.

Who is Timezone Converter for?

Software developers and DevOps engineers scheduling jobs, cron tasks, or deployments across servers in different regions. Convert "run at 9 AM EST" into the equivalent UTC and Tokyo times before setting up a scheduler.

• Convert server maintenance windows to all regional team timezones
• Validate timezone handling in applications by generating expected datetime outputs
• Build test fixtures with known datetime conversions

Data analysts and business intelligence teams working with datasets from multiple geographies. Meeting notes, transaction records, and log files often carry timestamps in a single timezone that need to be normalized for analysis.

• Normalize timestamps from CRM exports before loading into a data warehouse
• Convert sales transaction times to local timezone for regional reporting
• Cross-reference event logs from servers in different AWS regions

Global operations and scheduling teams coordinating across offices in New York, London, Dubai, and Singapore. Instead of pulling up multiple world clocks, run a bulk conversion once and export the table.

• Calculate meeting times across offices in 5 cities at once
• Plan event schedules for a global product launch
• Determine overlapping business hours for cross-timezone collaboration

Travel and logistics professionals planning routes, flight connections, or shipment arrival times across timezones.

• Convert departure and arrival times to local timezones for all stops
• Calculate business day windows for international shipments
• Verify that a delivery "by 5 PM local" meets the UTC deadline in the SLA

Why use Timezone Converter?

• ✅ Pure computation — no proxy, no anti-bot — 100% reliable, results in milliseconds
• ✅ Bulk support — convert hundreds of datetimes in one API call
• ✅ Multi-target — each request can target many timezones simultaneously
• ✅ Flexible timezone input — IANA names, UTC offsets, or abbreviations
• ✅ DST-aware — powered by Luxon with the full IANA timezone database
• ✅ Three output formats — ISO 8601, human-readable, Unix timestamp
• ✅ Graceful error handling — bad inputs produce error rows instead of crashing the run
• ✅ Pay-per-event pricing — pay only for conversions performed, no subscription
• ✅ API and scheduling ready — integrate via Apify API, Zapier, Make, or cron

What data does Timezone Converter output?

Each conversion produces one output row per source-target timezone pair:

Field	Type	Description
input	string	The original datetime string you provided
fromTimezone	string	Source timezone name as provided
fromUtcOffset	string	UTC offset of the source timezone (e.g., -04:00)
targetTimezone	string	Target timezone name as provided
convertedDatetime	string	Converted datetime in the requested format
utcOffset	string	UTC offset of the target timezone (e.g., +09:00)
dayOfWeek	string	Day of the week at the target timezone (e.g., Saturday)
isDST	boolean	Whether DST is active in the target timezone at that time
error	string / null	Error message if the conversion failed, otherwise null

How much does it cost to convert timezones?

This Actor uses pay-per-event pricing — you pay only for successful conversions performed. No monthly subscription. All platform costs are included.

	Free	Starter ($29/mo)	Scale ($199/mo)	Business ($999/mo)
Per conversion	$0.00115	$0.001	$0.00078	$0.0006
1,000 conversions	$1.16	$1.01	$0.79	$0.61
10,000 conversions	$11.65	$10.01	$7.81	$6.01

Plus a one-time $0.01 start fee per run (covers actor initialization).

Real-world cost examples:

Task	Conversions	Duration	Cost (Free tier)
Convert 1 datetime to 4 timezones	4	< 1s	~$0.01
Convert 100 datetimes to 3 timezones	300	~1s	~$0.36
Convert 1,000 datetimes to 5 timezones	5,000	~5s	~$5.79

Free plan estimate: With $5 in free Apify credits, you can perform approximately 4,300 conversions.

Higher-tier plans receive volume discounts — see the tier table above.

How to convert timezones with Apify

1. Go to Timezone Converter on Apify Store
2. Click Try for free — you'll be taken to the actor's input page
3. In the Conversions field, enter your conversion requests as a JSON array. Each request needs:
   • datetime — an ISO 8601 datetime string (e.g., "2024-06-15T14:30:00") or "now" for the current time
   • fromTimezone — source timezone (IANA name, UTC offset, or abbreviation)
   • toTimezones — array of target timezone(s)
4. Choose your Output Format: ISO 8601, human-readable, or Unix timestamp
5. Click Start — results appear in the Dataset tab within seconds
6. Export results as JSON, CSV, or Excel using the export button

Example input — convert a New York meeting time to global offices:

{
    "conversions": [
        {
            "datetime": "2024-09-10T15:00:00",
            "fromTimezone": "America/New_York",
            "toTimezones": [
                "Europe/London",
                "Europe/Paris",
                "Asia/Dubai",
                "Asia/Singapore",
                "Australia/Sydney"
            ]
        }
    ],
    "outputFormat": "ISO"
}

Example input — get current time in multiple timezones:

{
    "conversions": [
        {
            "datetime": "now",
            "fromTimezone": "UTC",
            "toTimezones": [
                "America/New_York",
                "America/Los_Angeles",
                "Europe/London",
                "Asia/Tokyo"
            ]
        }
    ],
    "outputFormat": "human"
}

Example input — bulk convert using abbreviations and UTC offsets:

{
    "conversions": [
        {
            "datetime": "2024-12-25T00:00:00",
            "fromTimezone": "EST",
            "toTimezones": ["PST", "GMT", "IST", "+05:30", "JST"]
        }
    ],
    "outputFormat": "ISO"
}

Input parameters

Parameter	Type	Required	Default	Description
conversions	array	Yes	—	Array of conversion requests. Each item must have datetime, fromTimezone, and toTimezones.
conversions[].datetime	string	Yes	—	ISO 8601 datetime string (e.g., "2024-06-15T14:30:00") or "now" for current time.
conversions[].fromTimezone	string	Yes	—	Source timezone. Accepts IANA name, UTC offset, or common abbreviation.
conversions[].toTimezones	string[]	Yes	—	One or more target timezones. Same format as fromTimezone.
outputFormat	string	No	"ISO"	Output format for converted datetimes: "ISO", "human", or "unix".

Supported timezone formats:

• IANA names: America/New_York, Europe/London, Asia/Tokyo, Australia/Sydney, UTC
• UTC offsets: +05:30, -07:00, +0530, +05, UTC+5, UTC-5:30
• Abbreviations: EST, EDT, CST, CDT, MST, MDT, PST, PDT, GMT, BST, CET, CEST, EET, EEST, IST, JST, KST, SGT, HKT, AEST, AEDT, NZST, NZDT, GST, PKT, SAST, UTC, and more

Output examples

ISO 8601 format (default):

{
    "input": "2024-06-15T14:30:00",
    "fromTimezone": "America/New_York",
    "fromUtcOffset": "-04:00",
    "targetTimezone": "Europe/London",
    "convertedDatetime": "2024-06-15T19:30:00.000+01:00",
    "utcOffset": "+01:00",
    "dayOfWeek": "Saturday",
    "isDST": true,
    "error": null
}

Human-readable format:

{
    "input": "2024-06-15T14:30:00",
    "fromTimezone": "America/New_York",
    "fromUtcOffset": "-04:00",
    "targetTimezone": "Asia/Tokyo",
    "convertedDatetime": "Sunday, June 16, 2024 3:30 AM",
    "utcOffset": "+09:00",
    "dayOfWeek": "Sunday",
    "isDST": false,
    "error": null
}

Unix timestamp format:

{
    "input": "2024-01-01T00:00:00",
    "fromTimezone": "UTC",
    "fromUtcOffset": "+00:00",
    "targetTimezone": "America/New_York",
    "convertedDatetime": "1704067200",
    "utcOffset": "-05:00",
    "dayOfWeek": "Sunday",
    "isDST": false,
    "error": null
}

Error row (invalid timezone):

{
    "input": "2024-06-15T09:00:00",
    "fromTimezone": "INVALID_TZ",
    "fromUtcOffset": "",
    "targetTimezone": "Europe/London",
    "convertedDatetime": "",
    "utcOffset": "",
    "dayOfWeek": "",
    "isDST": false,
    "error": "Invalid source timezone: INVALID_TZ"
}

Tips for best results

• 💡 Start small — test with 2-3 conversion requests first to verify the format before running hundreds
• 🕐 Use "now" for live data — great for monitoring dashboards that need the current time in multiple offices
• 🌍 Prefer IANA names — they're unambiguous. EST is always Eastern Standard Time, but IANA America/New_York automatically handles both EST and EDT based on the date
• 📋 Use ISO output for programmatic use — ISO 8601 includes the UTC offset and is easy to parse in any language
• 📅 Use human format for reports — Saturday, June 15, 2024 7:30 PM is ready for display without further formatting
• 🔢 Use unix for storage and comparisons — Unix timestamps are timezone-agnostic integers, ideal for databases and sorting
• 🔁 Schedule runs — use Apify's built-in scheduler to run the actor on a cron and push results to Google Sheets or Slack

Integrations

Timezone Converter → Google Sheets: Schedule a daily run that converts your global team's working hours to UTC and writes the results directly to a Google Sheet. Use the Apify → Google Sheets integration in Console to keep a live table of office hours for each timezone.

Timezone Converter → Slack: Set up a webhook to post converted meeting times to a Slack channel. For example, every Monday morning, convert the week's scheduled events from EST to the timezones of all attendees and post the list to #team-global.

Timezone Converter → Make / Zapier: Use as a step in a Make or Zapier automation. Trigger on a new row in a Google Sheet (e.g., a meeting scheduler), convert the time to target timezones, and update the sheet with the results.

Batch normalization pipeline: Use the Apify API to call Timezone Converter as a preprocessing step in a data pipeline. Pass in an array of event timestamps from a CRM export, get back ISO datetimes normalized to UTC, and load them into your data warehouse.

Monitoring and alerting: Combine with a data monitoring actor to alert when a scheduled maintenance window in UTC conflicts with business hours in a specific timezone. Run on a cron, convert the UTC window to local times, and trigger a Slack alert if it lands during peak hours.

Using the Apify API

You can run Timezone Converter programmatically via the Apify API. Replace YOUR_API_TOKEN with your token from Apify Console → Integrations.

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'YOUR_API_TOKEN' });

const run = await client.actor('automation-lab/timezone-converter').call({
    conversions: [
        {
            datetime: '2024-09-10T15:00:00',
            fromTimezone: 'America/New_York',
            toTimezones: ['Europe/London', 'Asia/Tokyo', 'Australia/Sydney'],
        },
    ],
    outputFormat: 'ISO',
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

from apify_client import ApifyClient

client = ApifyClient('YOUR_API_TOKEN')

run = client.actor('automation-lab/timezone-converter').call(run_input={
    'conversions': [
        {
            'datetime': '2024-09-10T15:00:00',
            'fromTimezone': 'America/New_York',
            'toTimezones': ['Europe/London', 'Asia/Tokyo', 'Australia/Sydney'],
        }
    ],
    'outputFormat': 'ISO',
})

items = client.dataset(run['defaultDatasetId']).list_items().items
print(items)

cURL

curl -X POST "https://api.apify.com/v2/acts/automation-lab~timezone-converter/runs?token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "conversions": [
      {
        "datetime": "2024-09-10T15:00:00",
        "fromTimezone": "America/New_York",
        "toTimezones": ["Europe/London", "Asia/Tokyo", "Australia/Sydney"]
      }
    ],
    "outputFormat": "ISO"
  }'

Use with AI agents via MCP

Timezone Converter is available as a tool for AI assistants that support the Model Context Protocol (MCP).

Add the Apify MCP server to your AI client — this gives you access to all Apify actors, including this one:

Setup for Claude Code

$claude mcp add --transport http apify "https://mcp.apify.com"

Setup for Claude Desktop, Cursor, or VS Code

Add this to your MCP config file:

{
    "mcpServers": {
        "apify": {
            "url": "https://mcp.apify.com"
        }
    }
}

Your AI assistant will use OAuth to authenticate with your Apify account on first use.

Example prompts

Once connected, try asking your AI assistant:

• "Use automation-lab/timezone-converter to convert 3 PM New York time on March 15 to London, Tokyo, and Sydney timezones"
• "What is the current time in Dubai, Singapore, and Johannesburg? Use the timezone converter actor"
• "Convert these meeting times to UTC: 9 AM PST on Monday, 2 PM CET on Tuesday, 11 AM IST on Wednesday"

Learn more in the Apify MCP documentation.

Is it legal to use Timezone Converter?

Yes — this actor performs pure timezone arithmetic. It does not scrape any website, access any third-party API, or collect any personal data. The IANA timezone database used by Luxon is an open-standard, publicly maintained dataset. There are no legal concerns with using this actor.

FAQ

How fast is the conversion? Each conversion takes under 1 millisecond — it's pure in-memory arithmetic. A batch of 1,000 conversions typically completes in 1-3 seconds, including actor startup time.

How much does it cost? $0.001 per conversion on the Starter plan, plus a $0.01 one-time start fee per run. A batch of 100 conversions costs about $0.11 total. Free plan users get $5 in credits — roughly 4,300 conversions.

Does it handle Daylight Saving Time (DST)? Yes. The actor uses Luxon, which includes the full IANA timezone database with historical and future DST rules. The isDST field in the output tells you whether DST is active at the target timezone for the given datetime. Abbreviations like EST are always mapped to the correct IANA timezone (e.g., America/New_York) to ensure DST is handled properly.

Why is my conversion result wrong? The most common cause is using ambiguous timezone abbreviations. For example, CST could mean Central Standard Time (UTC-6) or China Standard Time (UTC+8). To avoid this, use IANA timezone names like America/Chicago or Asia/Shanghai. The actor's abbreviation map always resolves ambiguous abbreviations to a specific region — check the supported abbreviation list in the Input parameters section.

Why does my conversion return an error row instead of failing the whole run? This is by design. Bad inputs (unparseable datetimes or unknown timezones) produce an error row in the dataset instead of crashing the run. This lets you process large batches where a few inputs may be malformed, without losing the rest of the results. Check the error field in each row.

What datetime formats does the actor accept? The datetime field accepts ISO 8601 format (e.g., 2024-06-15T14:30:00, 2024-06-15T14:30:00.000Z) and the special value "now". RFC 2822 is also attempted as a fallback. If you need to convert datetimes in other formats, normalize them to ISO 8601 first.

Can I convert to many timezones at once? Yes — each conversion request has a toTimezones array that accepts any number of target timezones. You can convert one source datetime to 50 target timezones in a single request. Each target timezone produces one output row and one charge event.

Other developer tools

• Broken Link Checker — find and audit broken links on any website
• Canonical URL Checker — verify canonical tags and redirect chains
• Domain Availability Checker — check if domain names are available for registration
• DMARC Record Checker — validate DMARC, DKIM, and SPF email authentication records
• SPF Record Checker — audit SPF records and identify email spoofing vulnerabilities
• Accessibility Checker — run WCAG accessibility audits on any web page
• Website Uptime Checker — monitor website uptime and response times