Timestamp / Epoch Converter
Convert Unix epoch ↔ human dates across every major time zone
How to use
- Pick Epoch → Date or Date → Epoch
- Enter timestamp (s or ms) or a date/time
- See every common format rendered live
- Review the same instant across 13 time zones
Use cases
- API debugging
- Log analysis
- Database inspection
- Cross-timezone debugging
About the Timestamp / Epoch Converter
A Unix timestamp is the number of seconds (or milliseconds) since January 1, 1970 UTC — the dominant way computers encode time. Converting to a human-readable date is a daily task when reading logs, debugging APIs, or correlating database rows across services. This converter does both directions and shows the same instant across every major time zone so you can reason about global events quickly.
Features
- Bidirectional: epoch ↔ date
- Seconds or milliseconds input
- Live current-time reference (updates every second)
- Outputs: Unix seconds, Unix ms, ISO 8601, RFC 2822, local time, relative time
- Renders the same instant in 13 major world time zones
- One-click copy for every format
How it works
- Pick Epoch → Date or Date → Epoch.
- Enter a timestamp (seconds or milliseconds) or pick a date and time.
- See every common format rendered — ISO, RFC, local, relative.
- Scroll down for the same instant in 13 world time zones.
Frequently asked questions
Seconds vs. milliseconds — which does my system use?
+
Unix and most databases use seconds (10 digits). JavaScript Date.now() and most APIs built after 2010 use milliseconds (13 digits). If your timestamp is 10 digits long, use seconds.
Is there a year-2038 problem here?
+
Not for this tool — JavaScript uses 64-bit doubles for Date, so we handle timestamps up to year 275,760. Your backend might still have the 32-bit int overflow problem (Jan 19, 2038).
What does 'relative time' show?
+
Human-friendly age: '3 hours ago', '2 days from now'. Useful for eyeballing whether a token is expired or a scheduled event is near.
Does the time zone panel handle DST correctly?
+
Yes. Each zone's render uses Intl.DateTimeFormat with formatToParts, which computes the correct offset at the target instant — not just the current offset.
Where does the current time come from?
+
Your system clock. If it's wrong, the 'current time' block and 'relative' outputs will be wrong too.