🕑 Unix Timestamp Converter

Convert between Unix timestamps and human-readable dates. View results in ISO 8601, RFC 2822, local, and UTC formats.

Last updated: November 8, 2026 · By the BoltQuickTools team

Current Unix Timestamp

Read the numbers that logs and APIs use for time

Log lines, API responses and database columns often store a moment as a count of seconds or milliseconds since 1 January 1970 UTC. That number means nothing at a glance, so anyone debugging a failed job or an expired token ends up needing it translated, or needing to produce one for a test.

Converting in either direction

Timestamp to Date: type or paste a number into the Unix Timestamp (seconds or milliseconds) field and press Convert or Enter. Pasting converts straight away. Now fills in the current time, and +1 Hour, +1 Day and +1 Week add to whatever is in the field.

Date to Timestamp: switch tabs, then choose a moment in the Date and Time picker. It converts as soon as the value changes. The same four shortcut buttons appear on this tab.

Results appear in rows labelled Unix (s), Unix (ms), ISO 8601, RFC 2822, Local Time and UTC, each with its own Copy button, plus a Relative line such as "2 years ago". The clock above the form shows the current timestamp and ticks every second.

Example: 1700000000

Entering 1700000000 reports "Detected as seconds" and shows:

RowValue
Unix (s)1700000000
Unix (ms)1700000000000
ISO 86012023-11-14T22:13:20.000Z
RFC 2822Tue, 14 Nov 2023 22:13:20 +0000
UTCTue, 14 Nov 2023 22:13:20 GMT

Local Time depends on your browser's time zone and language, so it will differ between machines. Entering 1700000000000 gives identical rows and reports "Detected as milliseconds".

How seconds and milliseconds are told apart

The page counts the characters you typed. Thirteen or more means milliseconds, anything shorter means seconds. That simple rule has edge cases:

Other details

Timestamp questions

Why does the RFC 2822 row always end in +0000?

The page formats that row from UTC values and appends a fixed offset. It is correct, but it will not match a header written with a local offset, even though both describe the same moment.

Does this page adjust for leap seconds?

No. Unix time and JavaScript dates both treat every day as exactly 86,400 seconds, so the page follows the same convention as the systems producing these numbers.

How do I find the gap between two timestamps?

Convert each one, then enter the dates in the date difference calculator. For a schedule rather than a single moment, the cron parser lists upcoming run times.