Back to Home
Blog

Unix Timestamp

Convert between Unix timestamps and dates

Current Unix Timestamp

0
1/1/1970, 12:00:00 AM

Timestamp to Date

Date to Timestamp

Quick Reference

Common Timestamps

  • Unix Epoch: 0 (Jan 1, 1970)
  • Year 2000: 946684800
  • Year 2038 Problem: 2147483647
  • Max JS Date: 8640000000000000 ms

Format Examples

  • Seconds: 1609459200
  • Milliseconds: 1609459200000
  • ISO 8601: 2021-01-01T00:00:00.000Z
  • RFC 2822: Fri, 01 Jan 2021

About the Unix Timestamp Converter

A Unix timestamp is just a count of seconds since January 1, 1970 (UTC) — it's how computers, databases, and APIs quietly track time behind the scenes. The problem is that a number like 1752537600 means nothing to a human until you convert it, and doing that math by hand (accounting for time zones, leap years, and whether the value is in seconds or milliseconds) is tedious and error-prone. This tool exists for the moment you're staring at a log file, a JSON payload, or a database row and need to know exactly what date and time that number represents, or the reverse: turning a date you have in mind into the epoch value your code expects.

The page opens with a live current Unix timestamp that ticks upward in real time, so you always have a correct reference value on hand without looking it up elsewhere. Below that, you can paste in any epoch timestamp and it converts instantly to a readable date and time, or go the other direction by entering a date and getting back the corresponding timestamp. It handles both standard second-based timestamps and millisecond-precision values, which matters because JavaScript's Date.now() and many logging systems use milliseconds while Unix cron and most server tools use seconds — mixing the two up is a classic source of off-by-1000x bugs.

Because the conversion runs entirely in your browser, nothing you paste in — timestamps, dates, or anything else — is sent to a server, which makes it safe to use with values pulled from private logs or internal systems. A practical habit: if a timestamp you're converting looks wildly wrong (like landing in the year 1970 or 50000+), you're probably reading a millisecond value as seconds or vice versa — check the digit count first, since ten digits is typically seconds and thirteen digits is typically milliseconds.

How to convert Unix timestamps and epoch time

Convert between Unix epoch timestamps and human-readable dates directly in your browser.

  1. 1

    Check the live timestamp

    View the current Unix timestamp updating live at the top of the page for a quick, always-accurate reference.

  2. 2

    Paste your timestamp

    Enter the epoch value you want to decode into the input field, whether it's in seconds or milliseconds.

  3. 3

    Read the converted date

    The tool instantly displays the corresponding human-readable date and time — no button click or page reload needed.

  4. 4

    Convert a date to epoch

    Switch direction by entering a specific date and time to get its Unix timestamp back.

  5. 5

    Match the precision you need

    Choose between second-based and millisecond-based output depending on what your code or system expects.

Frequently Asked Questions

What is a Unix timestamp?

A Unix timestamp is the number of seconds (or milliseconds) that have elapsed since January 1, 1970, 00:00:00 UTC — known as the Unix epoch. It's a time zone–independent way to represent a point in time, widely used in programming and databases.

How do I convert a Unix timestamp to a readable date?

Paste your Unix timestamp into the input field and the tool instantly converts it to a human-readable date and time in your local time zone, UTC, and ISO 8601 format. Works with both second-precision and millisecond-precision timestamps.

Why do some timestamps have 10 digits and others 13?

A 10-digit timestamp counts seconds since the Unix epoch (used in most server-side languages). A 13-digit timestamp counts milliseconds (used in JavaScript's Date.now()). Our converter auto-detects which format you're using.