Skip to content
TryDevSnip

Epoch & Unix Timestamp Converter

Live epoch clock plus bidirectional conversion — entirely in your browser.

Runs 100% in your browser. No upload.

Live current epoch

Seconds

—

Milliseconds

—

Epoch → human date

Local (selected TZ)
—
UTC
—
ISO 8601
—
Relative
—

Date → epoch

Epoch (seconds)
—
Epoch (milliseconds)
—

Unix time without the timezone traps

Unix timestamps count seconds (or milliseconds) since 1970-01-01 UTC. They are unambiguous on the wire and confusing on screens. This converter shows local (with a timezone you pick), UTC, ISO, and relative phrasing so you can confirm what an API field actually meant — without posting the number to a remote converter.

Off-by-1000 errors are classic: treating Date.now() milliseconds as seconds yields dates in the far future. Digit-count detection reduces that footgun. When in doubt, compare against the live clock above.

Frequently asked questions

Seconds or milliseconds — how do you detect which?

By digit length: 13+ digit values are treated as milliseconds; shorter values as seconds. Most modern APIs use seconds; JavaScript Date.now() is milliseconds.

Does this call a time API?

No. Conversion uses your browser clock and dayjs with UTC/timezone plugins, all bundled locally.

Why is my timestamp “wrong” by a few hours?

Usually a timezone interpretation issue. Check local vs UTC outputs and the timezone dropdown. The live epoch uses your device clock.

What is ISO 8601 here?

The ISO line uses JavaScript’s toISOString() — always UTC with a trailing Z. Handy for logs and APIs.

Can I convert a date back to epoch?

Yes. Use the date/time picker; outputs update for both seconds and milliseconds.

Is my input stored?

No. Values stay in the page until you close the tab.