Convert a timestamp
Paste a timestamp or pick a date. Use the current time fills in this moment.
Local
UTC / ISO
2027-01-15T08:00:00.000Z
Seconds since epoch
Everything stays in your browser. Nothing is sent or saved.
How to use the unix timestamp converter
- Paste a timestamp in seconds (10 digits) or milliseconds (13 digits). Seconds with a fraction, like 1729584000.123, work too.
- Read it as your local time and as UTC in ISO 8601 format.
- To go the other way, pick a date and time in your own time zone and copy the seconds.
- Press Use the current time to fill both fields with this moment.
How the unix timestamp converter works
A Unix timestamp counts the seconds since midnight UTC on Jan 1, 1970, the Unix epoch, leaving out leap seconds. It is the same number everywhere in the world at the same moment, which is why systems store time this way and only turn it into a local date to show it.
Seconds or millisecondsmore than 10 digits before any decimal point is read as milliseconds
Timestamp → datethe epoch + the seconds, shown in your time zone and in UTC
Date → timestampyour local date and time, converted to UTC, in seconds
The local result uses the time zone your device is set to, so two people converting the same timestamp see different clock times for the same moment. The UTC line is the same for everyone.
- Timestamp
- 1800000000 seconds
- ÷ 86,400 seconds a day
- 20,833 days and 8 hours
- UTC / ISO
- 2027-01-15T08:00:00.000Z
- Date
- Jan 15, 2027, 08:00 UTC
In New York that is 3:00am the same day, and in Tokyo 5:00pm. Same timestamp, same moment.
Unix timestamp converter FAQ
What is a Unix timestamp?
A count of the seconds since midnight UTC on Jan 1, 1970. Databases, APIs, log files and file systems use it because it is one plain number, the same in every time zone, and easy to sort and compare.
Is my timestamp in seconds or milliseconds?
Count the digits. Today a timestamp in seconds has 10 digits and one in milliseconds has 13. JavaScript and many APIs use milliseconds; most databases and command-line tools use seconds. The converter reads anything over 10 digits as milliseconds, counting only the digits before a decimal point, so Python’s 1729584000.123 is read as seconds.
How do I read the expiry time in a token?
A JSON Web Token stores its expiry as exp, a Unix timestamp in seconds. Decode the middle part of the token with the Base64 decoder, then paste the exp number here.
Why do webhooks include a timestamp?
So the receiver can refuse old requests. The sender signs the timestamp together with the body in a hash-based signature, and you reject anything more than a few minutes old, so a captured request cannot be replayed later.
What is the year 2038 problem?
Systems that store the timestamp as a signed 32-bit number run out at 2147483647, which is 03:14:07 UTC on Jan 19, 2038. The next second wraps around to 1901. Most modern systems use 64 bits and are fine, but old devices and file formats may not be.
More developer tools
Password generatorStrong, copy-ready passwords with length, symbol and number controls, plus a strength read.JSON formatterPretty-print, minify and validate JSON with clear, human error messages when it breaks.Hash & salt labHash any text with SHA-1, SHA-256 or SHA-512 (with optional salt) via the Web Crypto API.UUID generatorBatch RFC-4122 v4 UUIDs generated locally in your browser, no server round-trip.