Date & Time/Timestamp Converter
Unix Timestamp Converter
Convert Unix timestamps (epoch seconds or milliseconds) to human-readable dates and back. See ISO 8601, UTC, RFC 2822, and locale formats side by side. Nothing leaves your browser.
🔒All conversions happen locally in your browser. Nothing leaves your device.
Or paste any date string (ISO 8601, RFC 2822, etc.) in the timestamp field.
What is a Unix timestamp?
A Unix timestamp (also called an epoch timestamp) is the number of seconds that have elapsed since 1 January 1970 00:00:00 UTC — the Unix epoch. It is the most common way to represent a point in time in databases, APIs, and log files because it is a single integer with no ambiguity about timezone or calendar system.
Many modern systems use milliseconds instead of seconds for higher precision. JavaScript's Date.now() and most mobile SDKs return milliseconds; Unix command-line tools and most POSIX APIs use seconds. The tool lets you pick the right unit with one click.
FAQ
Is my data sent to a server?
No. All conversions use the browser's built-in Date and Intl APIs. Nothing is transmitted anywhere.
What is the Year 2038 problem?
Systems that store Unix timestamps in a 32-bit signed integer will overflow on 19 January 2038 at 03:14:07 UTC. Modern 64-bit systems and this tool are not affected — JavaScript handles dates up to ±8,640,000,000,000,000 milliseconds from the epoch (roughly ±275,760 years).
How do I get the current timestamp?
Click the Now button next to the timestamp input to fill in the current Unix time. On the command line: date +%s on macOS/Linux, or [DateTimeOffset]::UtcNow.ToUnixTimeSeconds() in PowerShell.
Does the tool account for leap seconds?
No — and neither does the Unix timestamp specification. Leap seconds are not counted in Unix time; UTC and Unix time diverge by the number of historical leap seconds (27 as of 2024), but the difference is rarely significant in practice.
Working with JWTs that contain timestamps? Try the JWT Decoder →