A practical starting point
Turn a timestamp into the right date and time
Decode a timestamp, distinguish seconds from milliseconds, and compare universal and local time before interpreting an event or log entry.
Useful starting points
Tools and resources you can explore today. External services have their own terms and availability.
A practical way forward
Identify the unit
Check the source field’s documentation for seconds or milliseconds. The current converter expects seconds: divide a millisecond value by 1,000 before entering it. Keep the original value and unit so you can verify the conversion.Compare time representations
Convert the value and note whether each result is UTC or local time. Include an explicit offset when sharing a date with someone elsewhere.Validate with a known event
Compare against an event whose time you already know. If results are unexpectedly far apart, check units and missing timezone information before editing records.
Keep in mind
- A displayed local time depends on timezone rules and may be ambiguous during clock changes.
- Avoid guessing the timezone of a date string that omits it.
Sources, not guesswork
Background for this guide. Discussion and documentation are useful signals, not proof of demand or an endorsement of every service.
- Date and timestamp reference Official guide
Documents timestamps and local versus universal-time representations.
Planned · Research
Batch time-zone checks
Research only — not available yet. Would comparing a column of event times across explicit time zones help diagnose your logs?
This feature is not available yet. We’re exploring whether it would be useful. Tell us about your task; leaving an email for follow-up is optional.