Convert Unix epoch seconds or milliseconds to a readable date — and the other way around — with a live clock in your browser. Useful when debugging logs or APIs; nothing you paste is sent to a server.
🔒Tool processing runs in your browser — your pastes/files are not uploaded to our servers for processing. Ads (if shown) load separately and do not receive your tool inputs.Advertising · Details
Quick answer
TryDevSnip Timestamp Converter turns Unix epoch seconds or milliseconds into local/UTC/ISO dates (and back) using your browser clock — no time API and not uploaded to our servers for processing.
Offline note
After assets load, many browsers (Chrome/Edge/Firefox) can keep the tool usable offline. Some browsers (e.g. Tor) or private modes block service workers — the tool still runs online without uploading your files to our servers for processing.offline-ready ✓
Live current epoch
Seconds
—
Milliseconds
—
Epoch → human date
Recent epochs (saved on this device)
Local (selected TZ)
—
UTC
—
ISO 8601
—
Relative
—
Date → epoch
Epoch (seconds)
—
Epoch (milliseconds)
—
Embed this tool
Paste this iframe on your site. Includes a backlink to Timestamp Converter. Opens chrome-less with ?embed=1.
How to verify: offline after assets load
Load this page once while online (so scripts are cached).
Open your browser’s Network tab (DevTools).
Turn on airplane mode, or disconnect Wi‑Fi / Ethernet (Chrome/Edge/Firefox usually work; Tor/private modes may block service workers).
Use the tool again with a sample or your own input.
Confirm no new upload requests to our servers — and the result still updates when offline is supported.
Whether online or offline, we don’t upload your inputs to our servers for processing.
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.
Rate this tool
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?
Recent epoch numbers you convert can be saved in this browser’s localStorage (digits only) for quick reuse. Not uploaded to our servers for processing. Clear recent anytime.
How do I convert an epoch/Unix timestamp to UTC?
Paste the number into the epoch field — the UTC output updates instantly, alongside your local time and ISO 8601. No separate "to UTC" step needed.
How do I convert a timestamp to a specific timezone (PST, EST, IST, EDT, JST, AEST, etc.)?
Pick the zone from the timezone dropdown near the epoch field — it recalculates using the IANA zone database (dayjs/timezone), so DST is handled automatically. Add ?tz=America/Los_Angeles (or any IANA zone name) to the URL to deep-link a specific zone.
