Format Date & Convert Timezone

The Format Date & Convert Timezone module parses almost any date input, converts it between IANA timezones with correct daylight saving time handling, and formats the result with simple tokens.

How it works

The module runs three steps in one call:

Parse the input. Accepted formats: ISO 8601, epoch seconds or milliseconds, YYYY-MM-DD, DD.MM.YYYY and DD/MM/YYYY, each with an optional time part.
Convert the wall-clock time from the input timezone to the output timezone, with DST applied correctly for the specific date.
Format the result using the tokens you define.

Module Fields

Field	Description	How to use it
Connection	Links the module to the CustomJS service	Select or create a connection using your API key
Date Value	The date or time to process	Map any supported value: ISO 8601, epoch seconds or milliseconds, `YYYY-MM-DD`, `DD.MM.YYYY` or `DD/MM/YYYY`, each with optional time
Input Timezone	The timezone the input is written in	IANA timezone, default UTC. Ignored when the value already carries an offset (`Z`, `+02:00`) or is an epoch value
Output Timezone	The timezone to convert into	Required. IANA timezone, default UTC
Output Format	How the result is formatted	Text, default `YYYY-MM-DD HH:mm:ss`. Tokens: `YYYY` `MM` `DD` `HH` `mm` `ss`, plus `MMM`/`MMMM` for month names and `ddd`/`dddd` for weekday names

Usage example

Convert a German appointment time to US Eastern time:

Settings:

Date Value: 23.08.2026 10:00
Input Timezone: Europe/Berlin
Output Timezone: America/New_York
Output Format: dddd, MMMM DD, YYYY HH:mm

Output (Formatted): Sunday, August 23, 2026 04:00

Berlin is on CEST (UTC+2) on that date and New York is on EDT (UTC-4), so 10:00 becomes 04:00. The module applies the correct DST rules for the specific date on both sides.

Output

Output	Description
Formatted	The date formatted with your Output Format tokens, in the output timezone
ISO 8601 (UTC)	The same moment as an ISO 8601 string in UTC
Epoch (ms)	Milliseconds since 1970-01-01 UTC
Epoch (s)	Seconds since 1970-01-01 UTC
Output Timezone	The IANA timezone the result was converted into
Weekday	The weekday name in the output timezone

Good to know

DST is handled correctly. The offset is calculated for the specific date, not from a static table, so summer and winter conversions both come out right.
Difference to Make's formatDate: the built-in formatDate function can format a date, but it cannot re-interpret a wall-clock time written in one IANA timezone as a time in another with correct DST. "10:00 in Europe/Berlin, what is that in America/New_York" is exactly what this module does in one step.
Offsets win. If the input already contains Z or +02:00, or is an epoch value, the Input Timezone field is ignored because the moment in time is already unambiguous.