How to use
- Paste the log into Log text. The formats can differ from line to line. The page opens with a sample log.
- For timestamps without a zone, such as
2026-03-02 14:07:11, choose the zone to read them in under Time zone for timestamps without one. If the server logged in Korean time, pick Seoul. - Choose the Convert to format (ISO 8601 UTC, ISO 8601 chosen zone, epoch seconds or epoch milliseconds) and you get the log back with every timestamp rewritten. Anything that is not a timestamp stays as it was.
- In the table below, check each timestamp’s line number, original text, format and converted values, and download them as CSV.
Formats it finds
| Format | Example | Zone |
|---|---|---|
| ISO 8601 and common | 2026-03-02T14:07:11.123+09:00, 2026-03-02 14:07:11,123 |
used if present, otherwise assumed |
| Slash or dot date | 2026/03/02 14:07:11, 2026.03.02 14:07:11 |
assumed |
| 14 digits | 20260302140711 |
assumed |
| Apache, nginx | 02/Mar/2026:14:07:11 +0900 |
as written |
| HTTP, mail date | Mon, 02 Mar 2026 05:07:11 GMT |
as written |
| syslog | Mar 2 14:07:11 |
assumed (year also from your input) |
| Epoch | 10-digit seconds, 13-digit ms, 16-digit µs, 19-digit ns | UTC based |
Fractional seconds keep the source’s digit count. ,123 (logback) and .123456 (microseconds) are read, and the epoch milliseconds 1772428034567 becomes 2026-03-02T05:07:14.567Z in ISO, keeping three digits.
Conversion example
Converting the sample log to ISO 8601 (UTC) with Seoul as the assumed zone gives the following. All seven lines land within the same seconds (05:07:11 to 05:07:17 UTC).
2026-03-02T05:07:11.123Z INFO server started
2026-03-02T05:07:12Z WARN slow query
2026-03-02T05:07:13Z ERROR upstream timeout
2026-03-02T05:07:14.567Z DEBUG retry
192.0.2.10 - - [2026-03-02T05:07:15Z] "GET / HTTP/1.1" 200 512
2026-03-02T05:07:16Z host sshd[123]: Accepted publickey
Date: 2026-03-02T05:07:17Z
Choosing ISO 8601 (chosen zone) with Seoul gives +09:00 endings such as 2026-03-02T14:07:11.123+09:00.
Where time zones trip you up
- A timestamp without a zone is a guess. The log alone does not say whether the server ran in UTC or local time. Rows whose last column
assumed_zoneistrueare guesses, so check the server setting and pick the right zone. - syslog has no year. The year you enter is used, so logs spanning December and January should be converted in separate parts.
- Daylight saving in places like New York and London changes the offset by date, and is applied automatically.
- The epoch range read is 2001 to 2099 (for 10-digit seconds, 1,000,000,000 up to but not including 4,100,000,000). Other numbers, and digits attached to words, are left alone. Still, a 10, 13, 16 or 19-digit number within range is read as a time even if it is an order number, so check the result.
FAQ
How are epoch seconds and milliseconds told apart?
By digit count. Epoch seconds from 2001 to 2286 have 10 digits and milliseconds have 13. To convert a single value with a unit you choose, use the Unix Timestamp Converter.
How do I convert to Korean time (KST)?
Set Convert to to “ISO 8601 (chosen zone)” and pick Seoul as the Output time zone. Converting to epoch always gives UTC-based values whatever the zone.
What if my log uses a format that is not listed?
Only the notations this tool reads are changed, and everything else is left as is. To work out a pattern for your own format, try the Regex Tester. For zone conversion alone, the Time Zone Converter is handier.
Can the log be very long?
Up to 1,000,000 characters and 20,000 timestamps are converted. Split anything bigger.
Is my log sent to a server?
No. Everything happens inside this page and nothing is sent or stored, so internal logs stay with you.
Related tools
- To convert a single value between units, use the Unix Timestamp Converter, and to compare times across cities the Time Zone Converter.
- To check job run times, use the Cron Expression Parser.
- To compare logs before and after conversion, there is Text Diff.
The log you enter is processed only in your browser and never sent to a server.