Everything runs in your browser using your device’s clock and time zone data. Nothing is sent to Flipper File.
Unix Timestamp Converter
Convert a Unix timestamp to a readable date, or a date to a Unix timestamp, as you type. The converter detects whether a timestamp is in seconds, milliseconds, microseconds, or nanoseconds, shows the result in UTC and any time zone you pick, and breaks the date into its parts. You can paste a whole list, with one timestamp or date per line.
How to use it
- Paste a timestamp like
1791989520or a date like2026-10-14 14:52:00. Each line converts in the direction it needs. - Pick a time zone to see the local date and offset alongside UTC.
- Click any value in the results to copy it, or use Copy and Download for the whole list.
- Click Use next to the live clock to start from the current Unix time.
What is a Unix timestamp?
A Unix timestamp, also called epoch time or POSIX time, is the number of seconds that have passed since 00:00:00 UTC on January 1, 1970, which is known as the Unix epoch. It's a single number that means the same moment everywhere, so it's widely used in databases, APIs, log files, and programming languages. Negative timestamps are dates before 1970. Unix time ignores leap seconds, so every day counts as exactly 86,400 seconds.
Seconds, milliseconds, microseconds, and nanoseconds
| Unit | Digits (current dates) | Example | Common in |
|---|---|---|---|
| Seconds | 10 | 1791989520 | Unix, PHP, Python time.time(), most databases |
| Milliseconds | 13 | 1791989520000 | JavaScript Date.now(), Java |
| Microseconds | 16 | 1791989520000000 | PostgreSQL internals, some logging tools |
| Nanoseconds | 19 | 1791989520000000000 | Go time.UnixNano(), high-resolution tracing |
Auto-detect uses the number of digits to pick the unit. If you're working with very old or far-future dates, where the digit count can be misleading, choose the unit yourself.
Dates without a time zone
A date like 2026-10-14 09:30 doesn't say which time zone it's in, so it could mean several different moments. By default the converter reads these as UTC. Switch Dates with no zone to read them in the time zone you've selected instead. Dates that end in Z, UTC, or an offset like -04:00 are always read exactly as written. Dates in the 10/14/2026 format are read as month/day/year.
The Year 2038 problem
Systems that store Unix time as a signed 32-bit integer can only count up to 2,147,483,647 seconds, which is 03:14:07 UTC on January 19, 2038. One second later, the number overflows and wraps to a date in December 1901. Most modern systems use 64-bit time, but older software and embedded devices may still be affected. The converter flags timestamps past this limit.
Frequently asked questions
How do I get the current Unix timestamp?
The live clock at the top of the tool shows it, updating every second. In code, use Math.floor(Date.now() / 1000) in JavaScript, int(time.time()) in Python, or date +%s in a Linux or macOS terminal.
Is a Unix timestamp the same in every time zone?
Yes. A timestamp counts seconds from a fixed moment in UTC, so it's the same number everywhere. Only the way it's displayed as a local date changes.
Why is my converted date off by several hours?
Usually the date was read in the wrong time zone, or a millisecond timestamp was treated as seconds. Check the detected unit in the result, and add a zone like Z or -05:00 to your date to make it exact.
Can I convert dates before 1970?
Yes. Dates before the epoch give negative timestamps, and negative timestamps convert back to dates before 1970.
Is my data sent anywhere?
No. Everything is converted in your browser, using your device's clock and time zone data.