Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors
page
Unix time converter icon showing a clock and timestamp

Unix Time Converter

Unix Time Converter

Convert between date/time and Unix epoch timestamps

Saved Conversions
No history yet. Calculate below to start tracking.

Unix time (also called epoch time or POSIX time) is the number of seconds that have elapsed since January 1, 1970, 00:00:00 UTC, not counting leap seconds. It's a simple, timezone-independent way to represent a moment in time as a single number.

It's widely used in server logs, APIs, databases, and programming languages because it's compact, sortable, and unambiguous across timezones. Many systems use seconds (10-digit numbers today), while JavaScript and some APIs use milliseconds (13-digit numbers).

Current Unix Time (seconds)
—
Date & Time
Interpreted in your browser's local timezone.
Epoch Seconds
Epoch Milliseconds
or convert the other way
Unix Timestamp
UTC
Your Local Time
⏲ Your Result
Relative Time
—
Enter a date or timestamp above
Quick Reference (current value)
Unix time counts seconds since January 1, 1970, 00:00:00 UTC. Provided by calculator24x7.com for informational purposes only.

Server logs, APIs, and databases frequently store timestamps as a single number rather than a readable date, this converter switches between that number and an actual date/time instantly.

How to use this Unix time converter

  1. Check the Current Unix Time displayed automatically, or tap Use Current Time.
  2. Enter a Date & Time to see its Unix timestamp, or enter a timestamp to see the corresponding date and time.

What this converter does

Unix time (also called epoch time or POSIX time) is the number of seconds that have elapsed since January 1, 1970, 00:00:00 UTC, not counting leap seconds. It’s a simple, timezone-independent way to represent a moment in time as a single number.

Unix Time = seconds elapsed since 1970-01-01 00:00:00 UTC

Why systems use Unix time instead of readable dates

Unix time is widely used in server logs, APIs, databases, and programming languages because it’s compact, sortable, and unambiguous across time zones, comparing two timestamps is a simple numeric comparison, and there’s no ambiguity about which time zone or date format is being used. Many systems use seconds (a 10-digit number today), while JavaScript and some APIs use milliseconds (a 13-digit number), so knowing which precision a given system uses matters when converting.

Frequently asked questions

What does a Unix timestamp actually represent?

The number of seconds that have elapsed since January 1, 1970, 00:00:00 UTC (the “Unix epoch”), not counting leap seconds, it’s a compact way to represent any moment in time as a single number.

Why do some systems use a 13-digit Unix timestamp instead of 10 digits?

A 10-digit timestamp counts seconds since the epoch, while a 13-digit timestamp (used by JavaScript and some APIs) counts milliseconds instead, giving finer time precision at the cost of a longer number.