Epoch Converter

Convert Unix timestamps in seconds or milliseconds into readable local and UTC dates, or generate a timestamp from the current time.

Unix timestampPrecision

Result

Local date: 6/15/2026, 1:50:01 PM

UTC date: 2026-06-15T10:50:01.000Z

Current Unix seconds: 1781520601

Current Unix milliseconds: 1781520601872

How to use this tool

Enter the required values in the labeled fields. Results update in your browser and are announced for assistive technologies. Use realistic measurements and verify important outcomes before acting on them.

Formula or logic

Unix time counts elapsed time since 1970-01-01T00:00:00Z. Seconds and milliseconds are supported.

Example calculation

Example: 1700000000 seconds converts to a readable date in your local timezone and UTC.

Practical use and limits

This page is built for small developer workflow checks that should not require an account, API call or pasted data upload. The calculation is intentionally visible and described above so you can sanity-check the result instead of treating it as a black box.

Limit: the output is a helper for inspection and formatting, not a security audit or production validation guarantee. For important decisions, use this result as a planning aid and verify it against the relevant source of truth.

Last reviewed: May 29, 2026.

Epoch Converter: practical guide

Epoch time is practical because systems can compare one number without arguing about date formats. It is also easy to misread when seconds, milliseconds and time zones get mixed together.

Use this converter when checking logs, API payloads, database exports, analytics events or webhook timestamps before assuming an event happened at the wrong time.

Real examples

API timestamp

Input: 1717243200

Result: convert as seconds since Unix epoch, not milliseconds

JavaScript timestamp

Input: 1717243200000

Result: usually milliseconds, so divide by 1000 for many APIs

Practical notes

Unix epoch is counted from 1970-01-01 00:00:00 UTC.
Many backend APIs use seconds; JavaScript Date uses milliseconds.
Always confirm whether the displayed time is UTC or local time.

Common mistakes

Reading a millisecond timestamp as seconds and getting a far-future date.
Debugging local time while the server logs are UTC.
Dropping timezone context when copying dates into tickets or reports.

Frequently asked questions

What is Unix time?

Unix time is a numeric timestamp measured from 1 January 1970 UTC.

Do I need seconds or milliseconds?

Many APIs use seconds, while JavaScript Date timestamps use milliseconds.

Does timezone matter?

The timestamp is absolute; display can be shown in local time and UTC.

Related tools

Converters