Paste a chunk of log output and every ISO 8601 timestamp or Unix epoch value gets your local time appended right next to it. No more mentally converting UTC log lines one by one.
How it works
Conversion runs two regular expressions over the pasted text: one matches ISO 8601 timestamps (with optional fractional seconds and a Z or offset suffix), the other matches 10-digit (seconds) or 13-digit (milliseconds) integers as plausible Unix epoch values, then appends each match's local time in the selected timezone using Intl.DateTimeFormat — epoch matches are further filtered to years between 2001 and 2100 so ordinary large integers like PIDs or byte counts don't get misread as timestamps.
FAQ
Why didn't it convert a large number that is actually a timestamp?
The epoch matcher only accepts exactly 10 or 13 digits (seconds or milliseconds since 1970) and discards anything that decodes to a year before 2001 or after 2100, since those are the lengths and range real timestamps actually fall in — a legitimately different epoch format, like microseconds, will be skipped by design to avoid misreading ordinary large numbers as dates.
Does it modify or remove the original timestamps in the log?
No — it appends the converted local time in parentheses right after each match rather than replacing it, so the original UTC or epoch value stays exactly as it was, and you can still see both.
Free, unlimited, no account. If this saved you a paid tool, a small thanks is appreciated.