Read logs
Convert Unix timestamps into human-readable local and UTC times while debugging events.
Timestamp Converter
Convert timestamps and date strings
Convert Unix seconds, Unix milliseconds, ISO strings, and local date-time values. Everything runs in your browser using your local timezone.
-Unix seconds
-Unix milliseconds
-ISO UTC
-Local time
-UTC date
-Your timezone
Common uses
Use this when reading API logs, database rows, analytics exports, scheduled jobs, and event timestamps from different systems.
Timestamp conversion guide
Timestamp Converter helps translate Unix timestamps, ISO strings, UTC time, and local browser time while reading logs, database records, analytics exports, scheduled jobs, and API responses.
Compare systems
Check whether an API, database, and browser are using the same timezone assumptions.
Prepare reports
Turn machine timestamps into readable dates for support notes or incident timelines.
Sample review notes for timestamp conversion
Timestamp conversion is most useful when it preserves the original evidence while making events readable across systems and timezones.
Expected result
Seconds, milliseconds, ISO strings, UTC, and local time are clearly identified, and event order remains consistent after conversion.
Failure signals
A 13-digit millisecond value is treated as seconds, local browser time is used for server ordering, or daylight saving changes explain a one-hour mismatch.
Reviewer action
Keep original timestamps beside converted values and use UTC as the baseline for incident timelines or support notes.
Real workflow note: incident timelines
Incident notes often combine browser logs, API records, queue jobs, and database rows. Timestamp conversion is most valuable when it preserves event order and keeps the original values auditable.
Identify units
A 10-digit Unix timestamp is usually seconds; a 13-digit value is usually milliseconds. Mixing them can produce dates in the wrong year.
Normalize to UTC
Use UTC for the technical timeline before translating key moments into a customer's local time.
Keep original values
Put converted values beside the source timestamp rather than replacing the original evidence.
Case study: building a UTC incident timeline
A failed export appears in browser logs, an API log, and a queue event. The team converts seconds, milliseconds, and ISO strings to UTC, sorts events by time, then adds local time only for the customer-facing explanation.
- Identify seconds, milliseconds, and ISO values before conversion.
- Use UTC for cross-system ordering.
- Keep original values next to converted times in incident notes.
Recommended workflow
- Identify whether the source timestamp is seconds, milliseconds, or ISO text.
- Convert to UTC first when comparing events across systems.
- Use local time only when explaining an event to a person in that timezone.
- Check daylight saving transitions for historical or scheduled times.
Quality checks before using the result
- Identify whether the source value is seconds, milliseconds, or an ISO string before interpreting the date.
- Use UTC as the comparison baseline when events come from servers, browsers, queues, or analytics exports.
- Keep the original timestamp beside the converted value in support notes or incident timelines.
Questions about this tool
Why is my timestamp off by 1000x?
Unix timestamps may be stored in seconds or milliseconds. Mixing them produces dates that are far in the past or future.
Should logs use UTC?
Yes. UTC avoids confusion across users, servers, and daylight saving changes.
Can timezone names be ambiguous?
Yes. Abbreviations like CST can refer to multiple regions, so use full IANA timezone names when possible.