Unix Timestamp & Epoch Converter
Convert Unix timestamps in seconds or milliseconds to human-readable dates, and dates back to epoch time. Shows local time and UTC. Free online epoch converter.
The Current Unix Epoch
1792044814
Pro Tip
A 10-digit timestamp is in seconds. A 13-digit timestamp is in milliseconds. Our tool detects both automatically for seamless conversion.
Common Date Formats
You can paste ISO strings, GMT dates, or even simple strings like "Jan 1, 2026" into the human date field to get the Unix epoch.
About this tool
Convert Unix timestamps into human-readable dates and back, in seconds or milliseconds, adjusted to your local time zone. Every developer who's stared at 1753430400 in a log file knows the ritual — this tool ends it in one paste.
How to Convert Timestamps
- 1
Paste an epoch timestamp to see its date, or pick a date and time to get its epoch value — conversion works in both directions.
- 2
The tool auto-recognizes seconds versus milliseconds by magnitude, so both 10-digit and 13-digit values convert correctly without you specifying.
- 3
Read the result in local time, and copy whichever representation your code, query, or bug report needs.
Why Convert Time with Wrklyst
- Computed Client-Side
- Conversion is a date calculation your browser performs alone — timestamps from production logs never leave your machine.
- Second-and-Millisecond Aware
- The classic off-by-1000x confusion between JavaScript and Unix conventions is detected and handled, not left as your problem.
- Always at Hand
- Quicker than spinning up a REPL or remembering date's flag syntax, with nothing to install or sign into.
Timestamp Sanity Tips
- A date of Jan 1 1970 means a zero or null timestamp got formatted — the bug is upstream.
- Dates in 1970 from real data usually mean milliseconds parsed as seconds; year ~57,000 means the reverse.
- Compare log timestamps in UTC when correlating across servers; local rendering hides offsets.
- 0, 86400, and negative values are great test cases — epoch, one day, pre-1970.
Frequently asked questions
What is Unix time, exactly?
A single number counting seconds elapsed since January 1, 1970, 00:00 UTC — the "epoch". Its genius is unambiguity: no time zones, formats, or locales, just monotonic arithmetic, which is why databases, APIs, and logs standardize on it and humans need converters to read it.
How do I tell seconds from milliseconds?
Digit count: current times are 10 digits in seconds (about 1.75 billion) and 13 in milliseconds. Mixing them up produces dates in 1970 or year 57,000 — the two classic symptoms. Unix tools and most APIs use seconds; JavaScript's Date.now() and Java use milliseconds.
Does the converted date account for my time zone?
Yes — the timestamp itself is timezone-free by definition, and the tool renders it in your device's local zone, which is almost always the answer you want when reading logs. Remember teammates in other zones see a different wall-clock time for the identical timestamp; the epoch number is the shared truth.
What is the year 2038 problem?
Systems storing Unix time in signed 32-bit integers overflow on January 19, 2038, wrapping to 1901. Modern 64-bit systems are safe for billions of years, but embedded devices and legacy databases still carry the risk — one reason timestamp handling remains an interview favorite and an auditing concern.