Transform

Shift timestamp columns across global time zones with full daylight saving time accuracy

Shift timestamps between UTC and local regional time zones with full daylight saving support.

🛡️ Your rows never leave your browser.
Why Onfyt: Uses IANA zone definitions to adjust for historical and future daylight saving time boundaries rather than naive static hour math.

Interactive Sample Data

order_idtimestamp_utcamount
1012026-03-15 14:30:0099.00
1022026-07-20 09:15:00145.50
1032026-11-10 22:45:0042.00

How this tool works

Database logs, Stripe webhook exports, and cloud analytics platforms almost universally record timestamps in Coordinated Universal Time (UTC / GMT). However, business stakeholders, finance teams, and customer service managers need to see transaction times in their local business day (e.g., Eastern Time, Pacific Time, Central European Time, or East Africa Time). Converting time zones manually in Excel by adding or subtracting fixed hourly offsets (such as subtracting 5 hours for EST) is a dangerous trap because of Daylight Saving Time (DST). In the US, for example, the offset shifts between UTC-5 (Eastern Standard Time) in winter and UTC-4 (Eastern Daylight Time) in summer. Applying a static -5 hour formula corrupts half the dates in your year by exactly one hour. DataFix uses the browser's internationalization engine (Intl.DateTimeFormat) coupled with the official IANA time zone database (e.g. 'America/New_York', 'Europe/London', 'Africa/Nairobi'). Every timestamp is parsed, evaluated against the exact DST transition rules in effect on that calendar day, and formatted into clean ISO 8601 or local timestamp strings.

Things that usually go wrong

  • Timestamps without timezone info (naive timestamps) are assumed to be in the source timezone specified.
  • DST (daylight saving time) transitions are handled correctly — an ambiguous local time gets the standard time interpretation.

Edge cases we tested

🧪 Daylight Saving 'Fall Back' and 'Spring Forward' transitions

Calculated with exact minute accuracy according to official IANA rules.

🧪 Timestamps with existing timezone offsets ('2026-05-01T10:00:00+02:00')

Parsed accurately to UTC before shifting to target zone.

🧪 Date-only strings without time components ('2026-05-01')

Preserved or flagged to prevent shifting dates into previous calendar days.

Frequently Asked Questions

What timestamp formats are supported?

ISO 8601 (2024-10-05T14:30:00Z), Unix epoch (integer seconds), and common formats like '2024-10-05 14:30:00'.

Are all IANA timezones supported?

Yes — America/New_York, Africa/Nairobi, Europe/London, etc.

How does the tool handle ambiguous times during DST transitions?

During 'fall back' transitions, the same local clock time occurs twice. The tool uses the first (standard time) occurrence by default, and flags ambiguous timestamps in a separate column.

Can I convert an entire CSV of timestamps from multiple source timezones?

Currently the tool applies a single source timezone to the entire column. For mixed-timezone data, add a timezone column and use the Add a Calculated Column tool to compute UTC offsets per row.

Related tools

Transform

Column to Comma-Separated List

Extract a CSV column and convert it to a comma-separated list for SQL IN clauses or code arrays.

Open Tool →
Transform

Comma-Separated List to Column

Convert a comma-separated, line-separated, or SQL IN list into a single-column CSV.

Open Tool →
Transform

Lines to CSV

Convert plain-text newline-delimited records into structured CSV tables.

Open Tool →