Convert a Unix timestamp to a date, or a date to an epoch value, in any IANA time zone. Reads seconds, milliseconds, microseconds or nanoseconds.
Runs in your browser — your input is processed on this device and never uploaded.
Unix epoch integer or RFC 3339 datetime. Maximum 256 bytes. There is no now default.
Results appear here.
A Unix timestamp, also called epoch time, counts the seconds since 1970-01-01 00:00:00 UTC. Logs, APIs and databases store that integer because it is compact and not tied to any time zone. People still need a date and a clock time, usually in a named zone.
This tool converts both ways in your browser. Paste an epoch value to get a date, or paste a date to get the epoch value. Input can be up to 256 bytes.
The result shows the RFC 3339 datetime with its UTC offset, Unix seconds, Unix milliseconds, the time zone name, the weekday, and the UTC offset in seconds.
A raw epoch in a log suits machines and slows people down. You cannot tell at a glance whether 1700000000 is a date in 2023 or a value in milliseconds, and a spreadsheet that reads it as a date serial will be off by decades.
The same converter answers the reverse question: which number to put in a database query, a log search or an API filter for a given local time.
Converting in the browser also keeps production timestamps off someone else's server, which matters when the numbers come from access logs or order records.
GNU date, PowerShell and Python's datetime do the same work locally when the value is already in a terminal. epochconverter.com is the long-running website for this job.
JWT Decoder on ToolkitBay shows the claims of a token, and its exp and iat values are Unix seconds you can paste here. To create time-ordered IDs, use UUID and GUID Generator with version v7.
Do not use this page as a clock or a scheduler, or to count leap seconds. Unix time ignores leap seconds by definition.
32-bit signed Unix time overflows at 03:14:07 UTC on 19 January 2038, the Year 2038 problem. This tool uses 64-bit values, so 2038 is not a problem here.
1000000000 seconds after the epoch was 9 September 2001 at 01:46:40 UTC, a common test vector.
Conversion runs in your browser. The timestamp is not sent to ToolkitBay's servers.