Micro Tool Yard logo
Tools
Current (seconds)1784460006
Current (milliseconds)1784460006547
Detected: seconds
Local timeSunday, July 19, 2026 at 11:20:06 AM UTC
UTCSun, 19 Jul 2026 11:20:06 GMT
ISO 86012026-07-19T11:20:06.000Z
Relative1 second ago
Ad Slot

How it works

  1. Pick a direction

    Convert a timestamp to a date, or a date to a timestamp.

  2. Enter a value

    Type an epoch number or a date/time string — either field accepts free-form text.

  3. Read the result instantly

    Local time, UTC, ISO 8601, and relative phrasing all update live.

Unix Timestamp Converter translates between epoch timestamps — the number of seconds or milliseconds since January 1, 1970 UTC — and human-readable dates, in both directions. A live current-timestamp display at the top updates every second in both units, which is handy for spot-checking API responses or log entries against "right now."

The Timestamp → Date panel accepts a raw epoch number and auto-detects whether it's in seconds or milliseconds based on its magnitude, though that guess can be overridden manually. It also accepts a date/time string directly — pasting an ISO timestamp into the field, for instance, is recognized as a date rather than mis-parsed as a tiny epoch value. Results are shown as local time, UTC, ISO 8601, and a relative phrasing (like "3 days ago") produced by the browser's built-in Intl.RelativeTimeFormat.

The Date → Timestamp panel does the reverse: type a date and time in whatever format is convenient — ISO 8601, RFC 2822, or a plain-English format like "July 19, 2026 2:30 PM" — and get back both the seconds and milliseconds epoch values, ready to paste into code, a database query, or an API call. There's no fixed picker format to match; anything the browser's native date parser accepts works.

FAQ

What is a Unix epoch timestamp?
It's the number of seconds (or milliseconds) elapsed since midnight UTC on January 1, 1970 — a compact, timezone-free way to represent a single point in time.
How does the tool know if my timestamp is in seconds or milliseconds?
With auto-detect on, values below 100,000,000,000 are treated as seconds (this covers every date until the year 5138) and larger values are treated as milliseconds. You can turn off auto-detect and pick the unit manually if you already know it.
Can I paste a date string into the Timestamp → Date field instead of a raw number?
Yes. If what you enter isn't a plain integer, it's parsed as a date/time string instead (ISO 8601, RFC 2822, and most common formats all work) rather than being mis-parsed as a very small epoch value.
What date formats does the Date → Timestamp field accept?
Any format the browser's native date parser understands — ISO 8601 ("2026-07-19T14:30:00"), RFC 2822, or everyday formats like "July 19, 2026 2:30 PM" or "07/19/2026". There's no fixed picker format to match.
Does the converter account for my timezone?
Yes. "Local time" reflects your browser's system timezone, while "UTC" and the epoch value itself are timezone-independent. A date/time string typed without an explicit timezone or "Z" suffix is interpreted in your local timezone.
Is my timestamp data sent anywhere?
No. All conversion runs locally in your browser using native JavaScript Date and Intl APIs.