⏱️

Epoch Converter

Compare an epoch with a human date using two directions, named presets and a ten-entry in-memory history. Read the UTC/ISO rows for an unambiguous instant and the local calendar components for your device’s zone.

Advertisement

Compare an epoch with a human date using two directions, named presets and a ten-entry in-memory history. Read the UTC/ISO rows for an unambiguous instant and the local calendar components for your device’s zone.

Current Unix seconds

Auto reads |value| > 9,999,999,999 as milliseconds, otherwise seconds. The sign does not change the rule; choose the unit explicitly for ambiguous values.

Presets (seconds)

The date picker uses your browser’s local time zone, shown here:

Result

History

The latest 10 successful conversions remain in this page’s memory. Clear removes them; reloading the page starts a new history.

Epoch input is limited to ±8,640,000,000,000,000 ms; local calendar input accepts years 0001–9999. Invalid dates and skipped daylight-saving times are rejected. At a repeated local time the browser chooses the earlier instant; choose a numeric epoch to remove ambiguity.

Method and limits

Unix time counts seconds from 1970-01-01 00:00:00 UTC. The browser’s Date and Intl functions produce UTC, local, ISO and approximate relative output; no leap-second table is applied.

Auto reads |value| > 9,999,999,999 as milliseconds, otherwise seconds. The sign does not change the rule; choose the unit explicitly for ambiguous values.

Epoch input is limited to ±8,640,000,000,000,000 ms; local calendar input accepts years 0001–9999. Invalid dates and skipped daylight-saving times are rejected. At a repeated local time the browser chooses the earlier instant; choose a numeric epoch to remove ambiguity.

Sub-millisecond input is truncated toward zero by Date; integer seconds use floor, so −1 ms is −1 second. Months and years in relative output approximate 30 and 365 days. Calendar details use local dates; week 1 contains January 1 and starts on Sunday, not ISO week numbering.

Conversion uses browser Date/Intl without a server conversion request. Copy asks the browser clipboard only after your action. The rest of the site’s services have their own data handling.

Copied

Copy failed. Select the result and copy it manually.

Embed this tool on your website

Use whole pixel dimensions from 1 to 4096.

× px (1–4096)

                        

💡 Integration Tip

Copy the embed code and paste it into your website HTML. The responsive version adapts to all screen sizes automatically.

3.3
3 ratings
✓

About Epoch Converter

Convert a Unix timestamp into a readable date, or go the other way from a date-and-time picker. Paste a value and Auto interprets seconds or milliseconds by a magnitude convention, then shows local time, UTC, ISO 8601, the weekday and a relative reading such as "3 days ago", each with its own copy button. A live counter of the current epoch runs at the top, and presets jump to landmarks like Unix zero and the 2,147,483,647 32-bit rollover. The conversion happens in your browser. Auto reads |value| > 9,999,999,999 as milliseconds, otherwise seconds. The sign does not change the rule; choose the unit explicitly for ambiguous values.

Compare an epoch with a human date using two directions, named presets and a ten-entry in-memory history. Read the UTC/ISO rows for an unambiguous instant and the local calendar components for your device’s zone.

Unix 0 produces timestamp 0 and timestampMs 0. −1000000000000 milliseconds (or Auto) produces 1938-04-24T22:13:20.000Z; the negative sign denotes an instant before 1970.

Conversion uses browser Date/Intl without a server conversion request. Copy asks the browser clipboard only after your action. The rest of the site’s services have their own data handling.

Use Cases

Inspect API timestamps and log events without changing the source data.
Compare database time values using explicit units.
Use ISO output when sharing an instant across time zones.
Technical writers preparing code samples, configuration examples, or documentation assets.
Check negative epochs and the signed 32-bit boundary.
Check UTC versus your browser’s local display.

How to use

1

Choose Epoch → date and enter a number, or select a seconds-based preset such as Unix 0. Auto reads |value| > 9,999,999,999 as milliseconds, otherwise seconds. The sign does not change the rule; choose the unit explicitly for ambiguous values.

2

Or press Use Current to insert the live counter shown under Current Epoch, which ticks once a second at the top of the page.

3

Try a preset button such as Y2K, iPhone (2007), Unix 0, Max 32-bit or 2030 to jump to a well-known moment.

4

Switch to the Date to Epoch tab and choose a moment in the date and time picker to convert in the opposite direction.

5

Read the Result rows for Local Time, UTC, ISO 8601, Relative, Day of Week and the timestamp in seconds and milliseconds.

6

Click the clipboard icon on any row to copy that single value; recent conversions stay under History until you press Clear.

7

Choose Epoch → date and enter a number, or select a seconds-based preset such as Unix 0.

8

Choose its unit explicitly when seconds and milliseconds could be confused.

9

Read the local, UTC, ISO and calendar rows; UTC/ISO fix the instant independently of your local zone.

10

Switch to Date → timestamp and select a valid local date; check the displayed device zone.

11

Copy the required value and review the last ten successful conversions; Clear removes that history.

Pro Tips

  • Auto reads |value| > 9,999,999,999 as milliseconds, otherwise seconds. The sign does not change the rule; choose the unit explicitly for ambiguous values.
  • Use keyboard shortcuts (Ctrl/Cmd+A to select all, Ctrl/Cmd+C to copy) to speed up your workflow inside the Epoch Converter.
  • Epoch input is limited to ±8,640,000,000,000,000 ms; local calendar input accepts years 0001–9999. Invalid dates and skipped daylight-saving times are rejected. At a repeated local time the browser chooses the earlier instant; choose a numeric epoch to remove ambiguity. Sub-millisecond input is truncated toward zero by Date; integer seconds use floor, so −1 ms is −1 second. Months and years in relative output approximate 30 and 365 days. Calendar details use local dates; week 1 contains January 1 and starts on Sunday, not ISO week numbering.
  • The latest 10 successful conversions remain in this page’s memory. Clear removes them; reloading the page starts a new history. If you need history, copy important outputs to a local file or note app.
  • Inspect API timestamps and log events without changing the source data.
  • The latest 10 successful conversions remain in this page’s memory. Clear removes them; reloading the page starts a new history.
  • Sub-millisecond input is truncated toward zero by Date; integer seconds use floor, so −1 ms is −1 second. Months and years in relative output approximate 30 and 365 days. Calendar details use local dates; week 1 contains January 1 and starts on Sunday, not ISO week numbering.

Troubleshooting

Problem:

The date is near 1970 or unexpectedly far away.

Solution:

Check seconds versus milliseconds. Auto is a magnitude convention; select the unit from your source.

Problem:

A local date is rejected or ambiguous.

Solution:

Check the real calendar date and local daylight-saving transition. Use a numeric epoch to specify an overlapping hour precisely.

Frequently Asked Questions

The local tool code uses no provider API key. Site access, account, advertising and consent conditions and browser resource limits remain separate. The date picker uses your browser’s local time zone.

Unix time counts seconds from 1970-01-01 00:00:00 UTC. The browser’s Date and Intl functions produce UTC, local, ISO and approximate relative output; no leap-second table is applied. The latest 10 successful conversions remain in this page’s memory. Clear removes them; reloading the page starts a new history. The date picker uses your browser’s local time zone.

Epoch input is limited to ±8,640,000,000,000,000 ms; local calendar input accepts years 0001–9999. Invalid dates and skipped daylight-saving times are rejected. At a repeated local time the browser chooses the earlier instant; choose a numeric epoch to remove ambiguity.

The tool lets you copy results for use in a project. It does not determine the rights or policies that apply to your input or project.

Local calculations require the page's JavaScript to have loaded. This does not guarantee an offline reload; browser capabilities still apply.

The local tool code uses no provider API key. Site access, account, advertising and consent conditions and browser resource limits remain separate. The date picker uses your browser’s local time zone.

No. It uses absolute magnitude, not context: values above 9,999,999,999 are milliseconds. Old millisecond values and far-future seconds can be ambiguous; select the intended unit.

The browser applies its local time-zone and daylight-saving rules. A skipped hour is rejected; an overlapping hour chooses the earlier instant. A numeric epoch avoids this local ambiguity.

The live counter changes every second; it never changes an existing result. Only a successful conversion adds a history entry, up to ten in this page’s memory.

Popular Tools

No more tools to show
Explore All Tools
FreeWebTools AI