EZ
EZ2Conv

Unix Timestamp Converter

Convert Unix timestamps in seconds or milliseconds to human-readable dates and back, with automatic input detection and full timezone support. Choose ISO 8601 or local output, insert the current time with one click, and see detailed conversion breakdowns as you type.

Settings

14px
0/50
Result will appear here...

Usage Examples

Timestamp Examples:
1640995200 (Seconds)
1640995200000 (Milliseconds)
-86400 (before epoch (1970))
Date/Time Examples:
2022-01-01T00:00:00Z
2022-01-01 00:00:00
January 1, 2022

How to Use

  1. Enter a Unix timestamp (seconds/milliseconds) or human-readable date in the input field
  2. Select your preferred timezone and output format from the settings panel
  3. View the converted result instantly with automatic format detection
  4. Copy the result or click 'Current Time' to insert the current timestamp

Understanding Unix Timestamps and Human-Readable Dates

What this converter does

A Unix timestamp counts the number of seconds elapsed since the Unix epoch — midnight UTC on 1 January 1970. It is a single integer, which makes it compact and unambiguous for storing a moment in time, but it is unreadable at a glance. This tool bridges that gap in both directions: paste a timestamp such as 1700000000 and it returns the matching calendar date and time; type a date and it returns the timestamp. Input detection works out whether you entered a timestamp or a date, so you rarely have to tell it which is which.

As you type, a breakdown panel shows the detected input type, the unit it settled on, and the moment it produced, so you can confirm the result rather than trust it blindly.

When to use it

Timestamps turn up throughout software: log lines, database columns, JWT expiry claims (exp), API responses, and cron records all tend to store time as an epoch integer. When you are debugging why a token expired or when an event actually fired, converting that integer to a real date is the fastest way to make sense of it.

The reverse is just as common. If an API expects a timestamp for a from/to query, or a test needs a fixed epoch value, you can enter a readable date and copy the integer straight out.

Example: a conversion

Take 1700000000. Interpreted as seconds, that is 14 November 2023, 22:13:20 UTC. Switch the timezone to Seoul (KST) and the same instant reads as 15 November 2023, 07:13:20 — the underlying moment does not move, only the wall-clock label does. Click Current Time to drop in the present epoch value, then convert it to confirm the tool and your system clock agree.

Notes and edge cases

The biggest trap is seconds versus milliseconds. JavaScript's Date.now() and many web APIs return milliseconds (13 digits today), whereas Unix tools and databases usually use seconds (10 digits). A value read in the wrong unit lands roughly 50 years off, so set the unit explicitly when auto-detection is ambiguous. Output can be formatted as ISO 8601 (2023-11-14T22:13:20Z) for machine exchange or as a localized human format for reading. And remember timestamps are anchored to UTC — the date you see depends on the timezone you select, not on where the number came from.

Frequently Asked Questions

Yes. You can convert unlimited Unix timestamps and dates in both directions at no cost — timezone selection, seconds or milliseconds units, ISO 8601 or local output, and the current-time shortcut are all available without limits, paid tiers, or an account.
Yes. Every conversion is computed in your browser with JavaScript, so the timestamps and dates you enter never leave your device. Even the Current Time button reads your system clock locally — nothing is sent to a server or logged.
No. There is no registration, email, or sign-in. Enter a timestamp or a date, or click Current Time, and the converted result appears immediately with the input format detected for you.
A seconds-based Unix timestamp counts whole seconds since 1970 and is usually 10 digits today (like 1700000000); a milliseconds-based one counts thousandths of a second and is 13 digits (like 1700000000000). Reading a value in the wrong unit shifts the result by decades, so the tool lets you set the unit explicitly and tries to detect it from the digit length.
A Unix timestamp always refers to one absolute instant measured from UTC. When you pick a timezone, the tool only changes how that instant is labeled on a wall clock — the moment itself is identical. That is why 1700000000 reads as 22:13 UTC but 07:13 the next morning in Seoul.
ISO 8601 is a standardized text format for dates and times, such as 2023-11-14T22:13:20Z, where the trailing Z marks UTC. It is the safest choice for exchanging times between systems because it is unambiguous. Pick the local format instead when you just want a readable date in your own region.

Related Tools

🔐

JWT Decoder

Decode any JSON Web Token to inspect its header, payload, and claims, with automatic checks on expiration, issued-at, and not-before times. Decoding happens locally and does not verify the cryptographic signature, so it is built for debugging and inspection rather than validating production tokens.

🆔

UUID Generator

Generate RFC 4122 UUIDs in bulk, choosing version 4 for cryptographically random IDs or version 1 for timestamp-based ones. Produce up to 100 at a time and toggle hyphens and uppercase formatting, with everything generated instantly in your browser.

🔢

Binary/Hex Converter

Convert data between text, binary, hexadecimal, decimal, octal, and Base64, with automatic input-format detection and all six representations shown at once. Customize the separator, hex case, and 0x/0b prefixes, then copy any single result or export everything as JSON.