How to use it
Paste a Unix value and compare the automatically detected unit against the source system. Review both local and UTC output, or choose local/UTC mode and enter a date to generate second, millisecond, microsecond, and nanosecond values.
Timestamp Converter Help, Examples, and FAQ
Use the timestamp converter to identify second, millisecond, microsecond, or nanosecond Unix values and compare the resulting instant in local time and UTC. You can also convert a chosen local or UTC date back to each precision. Always confirm the source unit and timezone before diagnosing a time discrepancy.
Worked example
Input
1715587200 seconds
Output
UTC: 2024-05-13 08:00:00 Local: depends on browser timezone
Useful scenarios
- Convert 1715587200 as seconds to identify the local time shown in logs.
- For a 13-digit API value, start with milliseconds, then recheck the unit if the date looks impossible.
- Enter a target date first when you need timestamp values for API test data.
- During cross-region incident analysis, compare UTC and local time to avoid mistaking timezone offset for latency.
Supported behavior and limits
- Accepts signed integer Unix timestamps in seconds, milliseconds, microseconds, or nanoseconds and uses BigInt during unit conversion.
- Outputs browser-local and UTC dates; reverse conversion accepts a datetime-local value in local or UTC mode.
- Representable calendar range is limited by the browser JavaScript Date implementation.
Privacy and data handling
Timestamp and date values are converted locally in the browser and are not sent to GoTools servers.
Frequently asked questions
- What is the difference between 10 and 13 digits? 10 digits usually means seconds; 13 usually means milliseconds.
- Why does the database show a different time? The database, server, and browser may use different default timezones.
- Can future timestamps be converted? Yes, as long as the value is within a reasonable range.