Unix Timestamp Converter

A Unix timestamp (or epoch time) is the number of seconds that have elapsed since 00:00:00 UTC on 1 January 1970, not counting leap seconds. For example, 2026-01-01 00:00:00 UTC is timestamp 1767225600. It is the universal time format used by Unix, Linux, databases, and most server-side APIs.

It depends on the API. JavaScript's Date.now() returns milliseconds — divide by 1000 to get seconds. Most server languages (PHP, Python, Ruby) and databases use seconds. Some Java systems and game engines use milliseconds. Check the API docs; getting this wrong shifts your date by decades.

You are likely comparing a UTC timestamp with a local-time string. Unix timestamps are always UTC. If you see 2026-01-01 05:00:00 when the timestamp is 1767225600, that's just your local timezone (WIB in this case). The tool always shows the ISO string and your local time so the relationship is clear.

Yes. The Date → Epoch card lets you set the timezone offset from UTC (default is your browser's local offset, so it matches your wall clock). The Epoch → Date card always shows both UTC (ISO) and your local time. You never have to guess whether a value is in UTC or local time.

Yes. Everything runs locally — the live counter, the conversions, the timezone math. No network calls. Refresh the page and the current time keeps ticking because the clock is recomputed from your device time on every render.