Unix Timestamp Converter
Convert Unix timestamps to human-readable dates and vice versa. Live current timestamp.
Seconds or milliseconds
Any parseable date format
Convert between Unix timestamps (seconds/milliseconds) and human-readable date formats. Shows current timestamp live and supports various date formats.
A Unix timestamp is the number of seconds (or milliseconds) elapsed since January 1, 1970 UTC — the "epoch." Almost every programming language and database uses some flavor of it internally because it's a single integer with no timezone ambiguity, no month-length edge cases, and no localization. The catch is that 1713787200 is not something a human can read at a glance — you need a conversion step whenever a timestamp shows up in a log file, an API response, or a database export.
This converter handles both directions and both common units. From timestamp to date, paste a number and the tool shows the equivalent UTC time, your local time, ISO 8601, RFC 2822, and a relative format ("3 hours ago"). It auto-detects whether your input is seconds (10 digits, through 2286) or milliseconds (13 digits — the JavaScript default). From date to timestamp, pick or type a date and time and get the integer in both units. A live clock displays the current timestamp so you can grab "now" without calculating.
Typical uses include decoding expiration fields in JWT tokens (which are Unix seconds), debugging timezone issues in API responses, converting database TIMESTAMP or DATETIME columns for a bug report, cross-checking scheduled job runs, and converting user-supplied dates into the numeric form your API expects.
- 1
Pick a direction
Choose timestamp-to-date or date-to-timestamp. Either mode accepts input instantly and shows the conversion with no button press needed.
- 2
Enter your value
Paste a timestamp (seconds or milliseconds are auto-detected) or pick a date from the picker. The current timestamp is shown live for quick reference.
- 3
Read multiple formats
Output appears in UTC, your local timezone, ISO 8601, RFC 2822, and a relative description. Copy whichever format matches your target system.
JWT token debugging
Decode the exp, iat, and nbf fields in a JWT — all Unix seconds — to check why a token is expired or not yet valid.
API response inspection
Convert Unix timestamps returned by Stripe, GitHub, or AWS APIs into a readable date when debugging a webhook or audit log.
Scheduled job verification
Confirm that a cron job ran at the expected UTC time by converting its logged timestamp to your local timezone.
Database timestamp conversion
Translate a BIGINT Unix timestamp stored in a database into a human-readable date for a bug report or support ticket.
How do I know if my timestamp is seconds or milliseconds?
Seconds-based timestamps for recent dates are 10 digits long (around 1.7 billion for 2024). Millisecond timestamps are 13 digits (around 1.7 trillion). The tool auto-detects by length, but you can override it if your value is ambiguous.
Does it handle timezones correctly?
Yes. Timestamps are always UTC by definition, and the tool converts to your local timezone using your browser's settings. It also shows UTC explicitly so you can share unambiguous values with teammates in other zones.
What's the Year 2038 problem?
Signed 32-bit timestamps overflow on January 19, 2038, because 2^31 seconds from 1970 lands there. Most modern systems use 64-bit integers and won't hit this for hundreds of billions of years, but legacy C code and some databases still have 32-bit columns that will wrap.
Is my data sent anywhere?
No. Conversion uses the browser's Date API locally. Timestamps and dates stay on your device.
Does it support ISO 8601 input?
Yes. In date-to-timestamp mode you can paste an ISO string like 2024-05-01T12:00:00Z and get the corresponding Unix timestamp in both seconds and milliseconds.