A practical guide to Unix timestamps
What is a Unix timestamp?
A Unix timestamp represents an instant as an offset from the Unix epoch, 1 January 1970 at 00:00:00 UTC. Many APIs use seconds, while JavaScript dates commonly use milliseconds. Both can describe the same instant, but their numeric values differ by a factor of 1,000. Negative values describe times before the epoch. The live clock above shows whole seconds using your device's current clock.
UTC is a shared time reference, whereas local time is a representation in your device's configured time zone. A timestamp does not itself contain a time zone. Converting the same instant into UTC and local time changes the displayed clock time, not the underlying moment. The UTC result uses the ISO 8601 form with a trailing Z.
Common developer uses
Timestamps appear in API responses, event logs, cache expiry settings, scheduled jobs and token claims. Developers convert them when comparing events across services or investigating why a request is considered expired. UTC is helpful when teams and servers operate in different regions; local time is useful when checking what a person saw on their device.
Enter a numeric value, choose seconds or milliseconds, and select Convert to date. To go the other way, select a date and time and choose whether it represents UTC or your local time zone. The tool reports both seconds and milliseconds. Fractional seconds are supported to millisecond precision, reflecting the underlying JavaScript date representation.
Troubleshooting common errors
A date unexpectedly thousands of years away, or near 1970, often means the wrong unit was selected. Check the documentation for the source field rather than relying only on the number of digits: timestamps can be negative or include fractions. Empty input, malformed numbers and dates outside the browser's supported range are rejected.
When converting a human date, be explicit about its time zone. The same clock reading interpreted as UTC or local time can produce different timestamps. Some local clock times do not exist when daylight saving time moves forward; the converter rejects those rather than silently shifting them. When clocks move backward, a local time can occur twice, and the browser chooses one occurrence. Use UTC or an explicit offset when that distinction matters.
Precision and privacy
Browser clocks can be wrong or adjusted, so a live timestamp is useful for inspection but should not replace a trusted server clock for security decisions. JavaScript dates have millisecond precision and a finite supported range. Conversion stays in your browser and the application does not submit your inputs to its server. Avoid placing sensitive event details in shared screenshots or clipboard contents.