# Time Zone Converter Guide

Read a log timestamp in one zone and see the same moment in UTC, Jakarta and others.

- Tool: https://ilham.dev/tools/time-zone-converter/
- Guide URL: https://ilham.dev/guides/time-zone-converter/
- Tool guides index: https://ilham.dev/guides/tools/
- Broader guide: Dates, Timestamps, and Time Zones (https://ilham.dev/guides/dates-times-and-time-zones/)

## What it does

Paste a timestamp the way it appears in a log — for example "Sep 26, 2026 @ 00:24:20.437" — pick the zone it was written in, and every row shows that same instant in another zone. The default source is UTC because that is what most servers and container runtimes log, which is exactly the thing that is easy to forget when reading an incident. The conversion uses the browser's own time zone database, so daylight-saving changes are handled at the instant you enter, not by a fixed offset.

## Use the tool

Open https://ilham.dev/tools/time-zone-converter/, add the input the tool asks for, run it, and check the output before using it elsewhere.

## Input and output

- Input: text.
- Output: text.
- Category: Workflow.

## Privacy and processing
Processing happens locally in your browser. This tool does not upload the input to ilham.dev.

## Questions

### Why is the default source UTC?

Most servers, containers and structured loggers write UTC. Setting the default to UTC means a bare timestamp is read the way the machine that wrote it meant it. Switch the source to Local if the log was written on your own machine in local time.

### Which input formats are understood?

ISO-like dates such as 2026-09-26 00:24:20.437, month-name forms such as Sep 26, 2026 @ 00:24:20.437 or 26 Sep 2026 00:24:20, dates without a time, Unix seconds or milliseconds, and anything the browser can parse when it carries an explicit offset such as Z or +07:00. A value with an offset is taken as an absolute instant and the source-zone selector is ignored.

### How do daylight-saving changes affect the result?

The zone offset is looked up for the exact instant you entered, not for today. If a wall time falls in the hour that repeats or is skipped at a DST change, the page resolves it with the offset that is in force at that moment.