Skip to content
QKQuickKit日本語
LogsLOCALRuns in your browserInput may contain sensitive information

Log Timestamp Converter

Convert one log timestamp between ISO 8601, Common Log Format, RFC 3164, journalctl, and epoch forms — entirely in your browser.

This tool handles input and primary processing in your browser and is designed not to send the input to QuickKit’s server.

Avoid live production secrets; use dummy or masked data where possible. Data handling details

Conversions

How it works

Paste one timestamp. Its format is detected — ISO 8601 / RFC 5424, Common Log Format, the RFC 3164 form used by syslog and `journalctl -o short`, `journalctl -o short-full`, or epoch seconds, milliseconds, or microseconds by digit count — and the same instant is rendered in every supported form. RFC 3164 states no year and no offset, and a `short-full` zone abbreviation such as JST names more than one offset in the general case, so nothing is converted from those until you supply the missing value; the result then says it depends on values you supplied. Set an output offset to see the same instant at a different offset, or leave it empty to use the input's own. Sub-second digits are carried through unchanged, but each output format is held to its own grammar. RFC 5424 allows at most six fractional digits (TIME-SECFRAC = "." 1*6DIGIT) and forbids leap seconds, so an input with seven or more fractional digits, or a written second 60, produces no RFC 5424 line at all — the reason is shown instead. Nothing is quietly truncated into a value that no longer matches the input. ISO 8601 and the journalctl forms keep the full precision they are allowed to carry. A written second 60 rolls into the following second in every computed value, and that is stated rather than hidden. Text after the timestamp is reported rather than ignored. Everything runs locally; nothing is uploaded, stored, or written into the URL.