Unix Timestamp Converter

Convert a Unix timestamp (epoch) to a readable date, or convert your chosen date/time to a timestamp — with seconds/milliseconds support, local time and UTC side by side.

Runs 100% in your browser — the timestamp you enter is never sent anywhere.

Timestamp → Date/Time

 

Date/Time → Timestamp

Seconds
—
Milliseconds
—

Try This Next

Finished here? These might be your next step.

JSON FormatterValidate, format and minify JSON.Diff CheckerCompare two texts line by line; see added and removed lines.Hash GeneratorCompute MD5, SHA-1/224/256/512 and RIPEMD-160 for text or files — one by one or in bulk.

Frequently Asked Questions

A Unix timestamp (epoch) is a time representation that counts the seconds elapsed since January 1, 1970 00:00:00 UTC. Since it carries no timezone information, it's the simplest way to pass a date/time between servers, APIs, and databases — every system converts this single number to its own local time.

It depends on which system you're talking to. JavaScript's Date object (and Date.now()) uses milliseconds; most classic Unix-derived systems, like the Unix/Linux date command, PHP's time() function, and MySQL's UNIX_TIMESTAMP(), use seconds. If you're not sure, use the "Auto-detect" option: a 10-digit number is interpreted as seconds, a 13-digit number as milliseconds — this is usually correct, but checking the other system's documentation is the safest bet.

No. The "Year 2038 problem" is when legacy systems that store Unix time as a signed 32-bit integer overflow into a negative value (wrapping to 1901) at 03:14:07 UTC on January 19, 2038. JavaScript's Date object uses a 64-bit floating-point number and works fine for millions of years in either direction, so this tool is unaffected. However, if you're integrating with an old 32-bit system, database column, or embedded device, that side may still be affected — that's a limitation of that system, not of this tool.

Last updated: