Unix Timestamp Converter

Convert Unix timestamps to readable dates and convert dates back to Unix time in local time or UTC.

Back to all tools on ToolForge

More in Date & Time

Input



Result

Local Time:

UTC Time:

Timestamp (sec):

Timestamp (ms):

Current Time

Now Timestamp (sec):

Now Timestamp (ms):

About Unix Timestamp Converter

This Unix timestamp converter converts between Unix timestamps and human-readable dates entirely in your browser. It handles both seconds (10 digits) and milliseconds (13 digits) automatically, and displays results in both local time and UTC for easy comparison.

What Is a Unix Timestamp?

A Unix timestamp (also called epoch time or POSIX time) represents a specific moment in time as the number of seconds or milliseconds that have elapsed since January 1, 1970, 00:00:00 UTC (the Unix epoch). The timestamp itself is always in UTC, regardless of your timezone.

Seconds vs Milliseconds

Unit Digits Example Common Uses
Seconds 10 1710000000 Unix/Linux, databases, PHP, Python
Milliseconds 13 1710000000000 JavaScript, Java, mobile apps

Common Timestamp Use Cases

Timezone Reference

Example Conversions

Timestamp to Date:

Date to Timestamp:

How to Convert Timestamps

  1. Enter your value: Type a Unix timestamp (like 1710000000) or a human-readable date (like 2024-03-09 12:00:00) into the input box.
  2. Choose conversion direction: Click "Timestamp → Date" to convert a timestamp to a readable date, or "Date → Timestamp" to convert a date to a timestamp.
  3. Review the results: The tool displays the converted date/time in both local time and UTC, along with timestamps in both seconds and milliseconds.
  4. Copy the output: Click "Copy Result" to copy all converted values to your clipboard for use in documentation, APIs, or debugging.

Quick Reference

Current timestamp (seconds): --

Current timestamp (milliseconds): --

Frequently Asked Questions

What is a Unix timestamp and how is it calculated?
A Unix timestamp (also called POSIX time or epoch time) represents the number of seconds or milliseconds that have elapsed since January 1, 1970, 00:00:00 UTC (the Unix epoch). It does not count leap seconds. For example, the timestamp 1710000000 represents March 9, 2024, at a specific moment in time.
What is the difference between timestamp in seconds vs milliseconds?
Unix timestamps can be expressed in seconds (10 digits, e.g., 1710000000) or milliseconds (13 digits, e.g., 1710000000000). JavaScript, Java, and many modern systems use milliseconds, while Unix/Linux systems, databases, and APIs often use seconds. This tool automatically detects and handles both formats.
Why is my timestamp conversion off by hours or a day?
Timezone confusion is the most common cause. Unix timestamps are always in UTC. When you see a converted date, make sure you know whether it's showing local time or UTC. Daylight Saving Time (DST) transitions can also cause apparent hour shifts. Always verify the timezone context when comparing timestamps across systems.
What is the Year 2038 problem?
Systems that store Unix timestamps as 32-bit signed integers will overflow on January 19, 2038, because the maximum value (2,147,483,647 seconds) will be reached. After this point, timestamps will wrap to negative values. Modern systems use 64-bit integers, which can represent dates for billions of years.
How do I convert a timestamp to my local timezone?
This tool automatically displays results in both local time and UTC. For manual conversion, add or subtract your timezone offset from the UTC time. For example, if you're in UTC+8, add 8 hours to the UTC result.