Last updated: October 2026
Unix timestamp converter online free — epoch to date in one click
Short answer: paste a timestamp above, pick seconds, milliseconds or microseconds, and click Convert to date — you get the date in local time, UTC, ISO 8601 and relative form. The reverse direction works too. No signup, nothing leaves your browser.
Seconds, milliseconds or microseconds?
A Unix timestamp counts time since 1 January 1970. Seconds is the classic 10-digit format you'll see in APIs and databases (e.g. 1700000000). Milliseconds is the 13-digit format JavaScript's Date.now() returns — if your timestamp has 13 digits, pick this. Microseconds is the 16-digit format some databases and high-precision systems use. A quick rule: 10 digits = seconds, 13 = milliseconds, 16 = microseconds.
Timezones, handled
The Local row shows the date in your browser's timezone — handy for reading logs. The UTC and ISO 8601 rows are timezone-independent, so use those when pasting timestamps into tickets, docs or code that teammates in other timezones will read.
What is Unix time?
Short answer: Unix time (also called epoch time or POSIX time) is the number of seconds that have elapsed since 00:00:00 UTC on 1 January 1970 — leap seconds not counted. Right now it's a 10-digit number around 1.79 billion, ticking up by one every second.
Because it's just a plain number, Unix time is the lingua franca of timestamps in APIs, databases, log files and JWT tokens. When you see a 10-digit number where a date should be, you're almost certainly looking at Unix time in seconds; 13 digits means milliseconds, 16 means microseconds.
Unix time vs epoch time — is there a difference?
No — Unix time, epoch time, epoch timestamps and POSIX time all describe the same thing: seconds counted from the 1970-01-01T00:00:00Z epoch. Different communities just prefer different names — systems programmers say "epoch", web developers say "Unix timestamp". This epoch converter handles every variant: paste any of them above and pick the right unit.
How to convert Unix time to a date
Short answer: paste the number into the Timestamp field above, select seconds, milliseconds or microseconds to match its digit count (10, 13 or 16 digits), and click Convert to date. You get the local time, UTC, ISO 8601 and a relative reading like "2 days ago".
Going the other way is just as fast: pick a date and time, click Convert to timestamp, and you get the epoch value in whichever unit you selected. The Use current time button fills in this exact second's timestamp — handy when you need a "now" value for code or a database row.
Negative timestamps aren't broken
Seeing a negative timestamp like -86400 and assuming the converter glitched is a common reaction — but it's correct. Unix time counts seconds from 1 January 1970, so any moment before that is a negative number; -86400 is simply 31 December 1969. Negative timestamps are perfectly valid and widely used in historical datasets; some older tools mishandle them, but the math is sound. For the full definition, see Wikipedia's article on Unix time.
Working with more developer staples? The Base64 encoder/decoder and the URL encoder/decoder live in the same toolbox.
Frequently asked questions
How do I convert a Unix timestamp to a date?
Paste the timestamp into the box above, pick seconds, milliseconds or microseconds, and click Convert to date. You'll see the date in your local timezone, UTC, ISO 8601 format and as relative time like "3 hours ago".
How do I convert a date to a Unix timestamp?
Pick a date and time in the second box and click Convert to timestamp. You get the epoch value in seconds, milliseconds or microseconds depending on the unit you selected.
What's the difference between seconds, milliseconds and microseconds?
A Unix timestamp counts time since 1 January 1970. Seconds is the classic 10-digit format (e.g. 1700000000). Milliseconds is the 13-digit format JavaScript's Date.now() returns. Microseconds is 16 digits, used by some databases and high-precision systems.
What timezone does the converter use?
By default it uses your browser's timezone. The Timezone dropdown lets you switch to any IANA timezone (e.g. UTC, Asia/Riyadh) — the top result row then shows the date in that zone, and date → timestamp inputs are interpreted in it. The UTC and ISO rows are always timezone-independent.
Is my data private?
Completely. Conversion runs entirely in your browser — nothing is uploaded, stored or tracked.
What is Unix time?
Unix time — also called epoch time or POSIX time — is the number of seconds since 00:00:00 UTC on 1 January 1970, not counting leap seconds. It's the standard way computers store dates: a single plain number instead of a formatted string.
Is Unix time the same as epoch time?
Yes. Unix time, epoch time, epoch timestamps and POSIX time are different names for the same count of seconds since 1 January 1970 UTC. This converter handles them all — just pick seconds, milliseconds or microseconds to match.
What is the current Unix timestamp?
Click "Use current time" in the tool above and it fills in the timestamp for this exact second. As of late 2026 it's a 10-digit number around 1.79 billion, growing by one every second.
What is the Year 2038 problem?
Older systems store Unix timestamps in a signed 32-bit integer, which maxes out at 2,147,483,647 — that's 03:14:07 UTC on 19 January 2038. One second later the counter overflows to a negative number, and those systems read it as 13 December 1901. Modern 64-bit systems won't hit their limit for about 292 billion years, but the bug is still live in embedded devices, old database schemas and MySQL TIMESTAMP columns (DATETIME is unaffected).
How do I get the current Unix timestamp in code?
Every language has a one-liner. JavaScript: Math.floor(Date.now() / 1000) (Date.now() alone returns milliseconds). Python: int(time.time()). PHP: time(). Bash: date +%s. They all return the same number of seconds since 1 January 1970 UTC.
Can a Unix timestamp be negative?
Yes. Dates before 1970 are negative numbers: -1 is 23:59:59 UTC on 31 December 1969. Most modern libraries handle this fine, but unsigned database columns reject negatives outright and some old date functions return garbage, so test before committing to a schema that stores history.
Why does my timestamp show the wrong date?
Almost always a unit mismatch. If your dates land in the year 57,000, you're treating 13-digit milliseconds as seconds — divide by 1,000. If everything shows January 1970, you're treating 10-digit seconds as milliseconds — multiply by 1,000. Count the digits: 10 means seconds, 13 milliseconds, 16 microseconds.
Does Unix time count leap seconds?
No — Unix time pretends leap seconds don't exist. When one occurs, the timestamp simply repeats for that second. That keeps the arithmetic dead simple (every day is exactly 86,400 seconds) at the cost of being slightly off astronomically.