About the Handiwork Timestamp Converter
The Timestamp Converter translates Unix (epoch) timestamps into human-readable dates and back again. View results in ISO 8601, UTC, and your local time zone, and grab the current Unix timestamp with one click — essential for debugging logs, APIs, and databases.
How to use the Handiwork Timestamp Converter
- Enter a Unix timestamp, or pick a date and time.
- Read the converted value in ISO, UTC, and local formats.
- Copy the timestamp or formatted date you need.
What is a Unix timestamp?
A Unix timestamp is the number of seconds (or milliseconds) that have elapsed since 00:00:00 UTC on 1 January 1970, known as the Unix epoch. Because it is a single number with no time-zone ambiguity, it is the most common way to store and exchange points in time in software.
Seconds vs. milliseconds
Many systems store timestamps in seconds, while JavaScript and some APIs use milliseconds — a factor of 1000 difference. If a converted date looks wildly off (for example, far in the future), you are probably mixing the two units.
How the input is interpreted
A 10-digit number is treated as seconds and a 13-digit number as milliseconds — the digit count alone decides which unit applies, matching the length most epoch timestamps naturally have in the current era. Anything else is handed to the browser’s date parser, which understands ISO 8601 strings and many common date formats directly, so you can also type a date instead of a raw timestamp.
Relative time and current timestamp
Alongside the absolute ISO, UTC, and local values, the result includes a plain-language relative time such as “3 hours ago” or “in 2 days,” computed against your device’s current clock. A one-click button also grabs the current Unix timestamp, useful for testing an API or a default value without doing the math yourself.
Assumptions and limitations
- Seconds vs. milliseconds is inferred purely from digit count (10 vs. 13); a timestamp with a different number of digits — or one padded or truncated unusually — will not be auto-detected correctly.
- “Local time” uses this device’s browser time zone and clock, so the same timestamp can display a different local time on another device unless you compare the UTC value instead.
- The relative time (“3 hours ago”) is computed against your device’s current clock, so it will be inaccurate if your system clock is wrong.
Sources and standards
These authoritative references were used to verify the method and guidance on this page.
Frequently asked questions
What is the Unix epoch?
The Unix epoch is the reference point for Unix time: midnight UTC on 1 January 1970. Timestamps count the time elapsed since that moment.
Does the converter handle time zones?
Yes. It shows the same instant in UTC and in your local time zone so you can compare them at a glance.
How does it know if I entered seconds or milliseconds?
By digit count: a 10-digit number is read as seconds and a 13-digit number as milliseconds. If your value has a different length, convert it to one of those lengths first or enter a formatted date instead.
Can I paste a date instead of a raw timestamp?
Yes. Anything that is not exactly 10 or 13 digits is parsed as a date string, so ISO 8601 values and many common date formats work directly.