Timestamp Converter
Convert Unix timestamps to dates, auto-detecting seconds, milliseconds and microseconds
Last updated: 2026-10-09
About this tool
Developers constantly translate between the number in a log line and a human-readable date. This tool accepts a Unix timestamp at any scale, works out whether it means seconds, milliseconds or microseconds, and returns local time, UTC, ISO 8601 and relative time at once. Enter a date and time to get the matching timestamp back.
Features
Automatic scale detection
The digit count decides the scale: 10 digits means seconds, 13 milliseconds, 16 microseconds. The detected conclusion is stated explicitly so you never misread the magnitude.
Several formats at once
Get local time, UTC, ISO 8601 and the weekday together, plus a natural-language "how long ago / from now" description - useful for both log triage and documentation.
Date to timestamp
Type a common format such as 2026-10-09 12:30:00 to get the timestamp, ready to copy into code or an API parameter.
Specific error messages
Not-a-number, out-of-range and unrecognised-date cases are reported separately instead of one generic failure.
How to use
- 1
Paste a timestamp
Drop a timestamp from a log or database into the field; the scale is detected and results update live.
- 2
Or enter a date
For the reverse direction, enter something like 2026-10-09 12:30:00 to see the timestamp.
- 3
Use the result
Each row - local time, UTC, ISO 8601 - has its own copy button, ready to paste wherever you need it.
- 4
Unsure? Use "now"
Click "Use current time" to fill in the present moment and compare offsets.
Options
- Detection rule
- By absolute digit count: up to 11 is seconds, 12-14 milliseconds, 15 or more microseconds. Microseconds are floored to milliseconds because JavaScript dates only carry millisecond precision.
- Representable range
- Supported from 1970-01-01 through 9999-12-31. Inputs outside that range are rejected rather than shown as a plausible but wrong time.
- Timezone note
- Local time is rendered in your device timezone while UTC is fixed to Coordinated Universal Time. Showing them side by side makes timezone-related offsets easy to spot.
Common use cases
- Turn a log timestamp into a readable time to pin down when an issue occurred
- Check which day a created_at column in the database actually refers to
- Generate an accurate timestamp for an API parameter or a test case
- Compare frontend and backend times to see whether a timezone misconfiguration is at play
- Convert dates into numeric timestamps for documentation or data analysis
- Work out how long ago a point in time was, to judge whether a cache has expired
FAQ
Questions you may have about this tool
How do I tell seconds from milliseconds?
Digit count is the easiest signal: 10 digits is seconds (until year 2286), 13 is milliseconds and 16 is microseconds. This tool detects the scale for you and labels the conclusion, so you never multiply or divide by 1000 by hand.
Why is the converted time a few hours off from what I expected?
That is almost always a timezone difference. The tool renders local time for your device and shows UTC alongside. Compare the two to tell whether the offset comes from timezone settings or from the timestamp itself.
Do timestamps depend on the timezone?
No. A Unix timestamp counts seconds since 1970-01-01T00:00:00Z - an absolute instant independent of any timezone. The timezone only affects how it is displayed as text.
What does a negative timestamp mean?
A negative value would refer to a moment before 1970-01-01. This tool does not accept negative input, since it is not needed in practice and mistakes are easy to make.
Does it work beyond 2038?
Yes. The year 2038 problem stems from 32-bit signed integer overflow, whereas JavaScript represents time as a double-precision float - well within this tool’s range up to year 9999.
Why are microseconds truncated?
JavaScript Date objects only have millisecond precision, so the sub-millisecond part is floored. If you truly need microsecond precision, trust the raw value on the server or in the database.
Which date formats are accepted?
Common forms such as 2026-10-09 12:30:00, 2026-10-09, 2026/10/09 and 2026-10-09T12:30:00Z are all accepted. Unrecognised input produces a clear message.
Is any data uploaded during conversion?
No. The whole conversion runs in the browser without any request, so timestamps never leave your device.