What is the Bulk Timestamp Converter?#
The Bulk Timestamp Converter reads the timestamps in pasted text and rewrites each one in UTC. Every line is parsed on its own, so text that mixes formats — ISO dates next to Unix timestamps or syslog lines — converts in one pass.
Each line keeps its original text, and every detected timestamp is shown with its UTC value. Lines with no recognizable timestamp stay as they are.
How to Use#
Paste your text. The results update as you type, and each detected time is converted on the spot. From there you can copy a single time, copy the results as CSV, or copy the whole text with the timestamps replaced.
Supported Formats#
Offsets are honored when present. Without one — and for a syslog line without a year — the UTC/local setting and the current year apply.
- ISO 8601 / RFC 3339:
2026-10-01T12:34:56+09:00,2026/10/01 12:34:56, and a date on its own such as2026-10-01. The offset may be written asZ,+09:00,+0900, or+09. - Unix timestamps: 10 digits are seconds, 11–13 digits are milliseconds. Other lengths are skipped.
- RFC 2822:
Wed, 01 Oct 2026 12:34:56 +0900, withGMT,UT,UTC, or a numeric offset. A date followed by a short word of 2–5 letters, such asJSTorINFO, is left alone rather than guessed. - syslog:
Oct 1 12:34:56, picked out of a line that has no year. - Apache/nginx common log:
01/Oct/2026:12:34:56 +0900, picked out of the surrounding access log line.
When a line holds more than one timestamp, only the first converts. Converted values are always UTC in ISO 8601, and milliseconds appear only when the source had them.
Common Use Cases#
- Aligning timestamps from several services and logs to UTC during an outage.
- Reading epoch values buried in application text as dates.
- Comparing exported data from different servers before their formats are unified.
FAQ#
A date on its own is read as midnight in the UTC/local setting, then converted to UTC. If you only want dates that carry a time to convert, leave bare dates out of the text.
Copy the results as CSV to get each line as a row with the line number, format, original text, and UTC value. Lines that were not recognized are included, with the format and value left empty.
No. Line breaks are normalized to LF, so text pasted with CRLF or CR line breaks comes out with LF.
No. Everything runs in your browser, and your text never leaves your device.
Notes#
- Unix timestamps in microseconds or nanoseconds are not supported.
- Any bare 10–13 digit number inside the date range can read as a Unix timestamp — even an ID or a counter.
- A time recorded in a zone other than UTC or your local time cannot be resolved unless it carries an offset.
- Input over 1,000,000 characters is not parsed.