About the Unix Timestamp Converter
This tool converts Unix epoch numbers to human dates and converts dates to Unix timestamps. You use it to check API data, debug logs, schedule jobs, or share precise time values. It runs entirely in your browser, so nothing is uploaded to a server and no files are sent. The converter accepts seconds or milliseconds, updates results as you type, and applies your chosen IANA time zone so daylight saving rules are correct for the date. It also treats long numbers (1e11 or more) as milliseconds to match JavaScript and Java conventions. You can copy a result or create a share link that reopens the page with your inputs. The tool shows the numeric result, local display for the selected zone, ISO 8601 form, millisecond value, and a plain-language readout.
How to use it
- 1Select Convert direction: Timestamp to date or Date to timestamp.
- 2Enter a Unix timestamp (seconds or milliseconds) or type a date and time.
- 3Choose a time and pick a time zone from the list.
- 4Copy the Result field or click Share to create a reopen link.
Worked example
Input: Timestamp = 1609459200, Time zone = UTC. Result: 2021-01-01 00:00:00. In the chosen time zone: 2021-01-01 00:00:00 (UTC). ISO 8601: 2021-01-01T00:00:00Z. Milliseconds: 1609459200000. Read as: January 1, 2021 at 00:00:00 UTC.
How it works
A Unix timestamp counts the seconds since 00:00:00 UTC on 1 January 1970, not counting leap secondsNumbers of 1e11 or more are read as milliseconds (JavaScript, Java) and smaller ones as seconds (most databases and APIs)Local times use your browser's time zone database, so daylight saving is applied automatically32-bit systems overflow at 2147483647 (19 January 2038)Results update instantly as the visitor types; there is no calculate buttonVisitors can copy the result and share a link that reopens with their numbersSource: POSIX / The Open Group - Seconds Since the EpochIANA Time Zone Database TheoryLinux man page: time (man7.org). Last checked 5 November 2026.
What it is good for
- Runs entirely in your browser; no data uploaded.
- Auto-detects seconds or milliseconds and updates instantly.
- Shows ISO 8601, millisecond value, and a plain-language readout.
- Does not account for leap seconds; follows POSIX semantics.
- 32-bit overflow issues still apply to systems using 32-bit time_t.
Questions people ask
What exactly is a Unix timestamp?
A Unix timestamp is the integer count of seconds since 1970-01-01 00:00:00 UTC. Many systems use seconds, while JavaScript and some APIs use milliseconds.
How do I tell if a number is seconds or milliseconds?
Use digit count as a guide: about 10 digits usually means seconds, 13 digits means milliseconds. This tool treats numbers of 1e11 or more as milliseconds to match common language runtimes.
Do Unix timestamps include leap seconds?
No. POSIX-style Unix time treats each day as exactly 86,400 seconds and does not encode leap seconds. Conversions at leap-second instants can vary by implementation.
Why do I get different local times for the same timestamp?
A timestamp is timezone-independent. The displayed local time depends on the time zone and its daylight saving rules for that date. Pick the correct IANA zone, for example America/New_York or Europe/London, to get the expected local time.
When will the Year 2038 problem happen?
Signed 32-bit Unix time overflows at 2,147,483,647 seconds, which is 2038-01-19 03:14:07 UTC. Modern systems typically use 64-bit time values and are not affected.
Is my date input treated as local or UTC?
The tool applies the time zone you choose. If you pick UTC the converter treats the date as UTC. If you pick a local zone, the converter shows the date in that zone and applies historical DST rules from your browser's time zone database.
Help keep every tool free
FreeToolr stays free because people help it grow. Share a tool you like, tell us what to build next, or support us on Ko-fi.