Unix Time Converter

About this tool

Unix Time Converter on UtilityKit converts between Unix epoch timestamps and human-readable dates in both directions: enter a timestamp in seconds and see the ISO 8601 UTC date plus your local time, or pick a date and time in your local timezone and get the epoch seconds ready for code, APIs or database queries. Unix time — seconds elapsed since 00:00:00 UTC on 1 January 1970 — is the universal format across backend systems, logs, cloud APIs and JWT claims. The timestamp field always reads seconds, so divide a 13-digit millisecond value by 1000 before converting. Use current time fills in the current second and converts it at once. The reverse direction uses a date-and-time picker and outputs the floor-second integer, which also appears in the timestamp field, ready to paste into a curl command, SQL WHERE clause or JWT exp field.

Why use it

• Seconds In, Dates Out: The timestamp field takes standard Unix seconds — the format used by most servers, JWT claims and cloud APIs — and returns a readable date with no arithmetic.

• Simultaneous UTC and Local Time Output: The result always shows both the ISO 8601 UTC string and your browser's locale-formatted local time, so you never have to mentally subtract your UTC offset.

• Current Time in One Click: Use current time fills in the current second as a Unix timestamp and converts it immediately — useful for generating test values or checking the current epoch without arithmetic.

• Bidirectional — Date to Timestamp Too: Pick any calendar date and time and get the exact Unix timestamp back in seconds, ready to paste into a curl parameter, SQL WHERE clause, or JWT exp field.

• Debug Logs and JWT Claims Quickly: Server logs and JWT payloads surface epoch integers that are unreadable at a glance. Paste them here to confirm whether a token is expired or a log event occurred in the right time window.

• Browser-Only — Works Offline and Without Sign-Up: Date arithmetic runs entirely in the browser using the native JavaScript Date API. No server, no account, and no Internet connection required once the page has loaded.

How to use

1. To convert a timestamp to a date, type the Unix timestamp in seconds into the 'Unix timestamp · seconds' field.
2. Click 'Timestamp → date' — the result shows the ISO 8601 UTC time and your local time, and the date picker is set to match.
3. To convert a date to a timestamp, choose a date and time in the 'Date & time · your local timezone' picker.
4. Click 'Date → timestamp' — the result shows the Unix timestamp in seconds and fills the timestamp field.
5. Click 'Use current time' to fill in the current second and convert it immediately.
6. Click 'Copy result' to copy the converted text.

When it helps

• When a server log or database record shows a large integer and you need to know what date and time it represents in human terms.
• When a JWT token's exp or iat claim is an epoch integer and you need to verify whether the token is still valid or has already expired.
• When writing a curl command or SQL query with a date filter and you need the exact Unix timestamp for a specific calendar date and time.
• When a cloud API (AWS, GCP, Stripe, GitHub) returns an event timestamp as epoch seconds and you need to correlate it with a local event timeline.
• When debugging a time-based bug where two systems disagree on event ordering and you need to verify whether each system's timestamp resolves to the same instant.
• When generating test data that requires realistic past or future Unix timestamps and you need to pick a date and get the integer value quickly.

Examples

1746057600 (browser set to UTC, en-US locale)

2025-05-01T00:00:00.000Z (local: 5/1/2025, 12:00:00 AM)

1715000000000 ÷ 1000 = 1715000000 (browser set to UTC, en-US locale)

2024-05-06T12:53:20.000Z (local: 5/6/2024, 12:53:20 PM)

2025-01-15 09:00:00 picked in the date picker (browser set to UTC)

1736931600 seconds

Tips

• When working with JWT tokens, paste the exp claim integer directly — if the resulting date is in the past, the token has expired. The ISO 8601 output makes it immediately obvious.
• Use current time is handy for capturing a reference timestamp at the moment a deployment starts or a config change is applied — no terminal needed.
• If a timestamp from a JavaScript application has 13 digits, it is in milliseconds — divide by 1000 before entering it, because the tool reads seconds.
• To find the Unix timestamp exactly 30 days from now, click Use current time, then add 2,592,000 (30 × 86400) to the value.
• ISO 8601 output (e.g. 2024-05-06T12:53:20.000Z) can be pasted directly into most database timestamp fields, REST API bodies, and documentation — it is universally parseable.

Frequently Asked Questions

Glossary

Unix epoch

The reference point for Unix timestamps: 00:00:00 UTC on Thursday, 1 January 1970. All Unix timestamps are the number of seconds (or milliseconds) elapsed since this moment.

Unix timestamp

An integer representing a point in time as the number of seconds elapsed since the Unix epoch. A 10-digit integer represents a date in the range 2001–2286.

ISO 8601

An international standard for representing dates and times (e.g. 2024-05-06T20:13:20.000Z). The trailing Z indicates UTC. Universally parseable by databases, APIs, and programming languages.

Millisecond timestamp

A 13-digit Unix-style timestamp counting milliseconds since the epoch. Used by JavaScript's Date.now(), Java System.currentTimeMillis(), and many cloud APIs. Divide by 1000 to get seconds.

UTC (Coordinated Universal Time)

The primary time standard against which the world's clocks are regulated. Unix timestamps always count from the UTC epoch regardless of the local timezone of the system producing them.

JWT exp claim

A field in a JSON Web Token payload that specifies the expiration time as a Unix timestamp in seconds. If exp is in the past relative to the current time, the token is expired and must be rejected.