Unix Timestamp Converter Logo
Developer Tools Embed Tool

Unix Timestamp Converter

Convert Unix timestamps between seconds, milliseconds, UTC, and local dates, and convert date-time values back to timestamps.

0
Uses
—
Verified
Open
Access
Nov 2026
Added
Back to Directory

Unix Timestamp Converter

Convert Unix timestamps in seconds, milliseconds, microseconds or nanoseconds to dates in any time zone, and turn dates back into timestamps.

Live clock100% private
Current Unix time (seconds)
0
0 ms  · 
Saved on this device 0

    Found a Bug or Missing a Feature?

    Report any problems or suggest new features you want. You can write in English, Urdu, Hindi, or any language! Our AI will analyze your feedback and upgrade the tool.

    About This Tool

    Convert Unix timestamps between seconds, milliseconds, UTC, and local dates, and convert date-time values back to timestamps.


    Unix Timestamp Converter: Seconds, Milliseconds and the Bug That Puts You in 1970

    A Unix timestamp is a single number: how many seconds have passed since midnight UTC on 1 January 1970. Computers love it because it has no time zone, no daylight saving and no date format to argue about. People hate it for the same reason, since 1700000000 means nothing at a glance. The converter above translates in both directions, shows the result in any time zone you choose, and keeps a live clock at the top so you can copy the current value.

    Reading a timestamp by counting digits

    Most of the confusion comes from units. Today's timestamp in seconds has 10 digits. In milliseconds, which is what JavaScript's Date.now() returns, it has 13. Microseconds have 16 and nanoseconds 19. The converter uses that rule on Auto-detect and tells you what it assumed, so you can override it if your number is unusual.

    Worked example: 1700000000 is 14 November 2023, 22:13:20 UTC. In Karachi (UTC+05:00) the same instant is 15 November, 03:13:20. In New York (UTC-05:00) it is still 14 November, 17:13:20. Same number, three wall-clock readings; that is exactly why servers store the number and convert only for display.

    The 1000x bug

    If you feed milliseconds to something that expects seconds, you land tens of thousands of years in the future. If you do the opposite and treat 1700000000 as milliseconds, you end up on 20 January 1970, about 20 days after the epoch. When a date in an API response looks like early 1970, suspect a unit mix-up before anything else.

    2038 and other big numbers

    Systems that keep time in a signed 32-bit integer run out at 2,147,483,647, which is 19 January 2038, 03:14:07 UTC. Paste that value in, and add one, to see the warning the tool shows. Most modern software uses 64-bit values and will not care, but old embedded devices and some databases still do.

    Four modes, one page

    Timestamp to date

    Besides the ISO 8601 string you get a readable date, an SQL-style datetime, the RFC 2822 form used in HTTP headers, how long ago or from now it is, the weekday, the day of the year and the ISO week number. Every row has its own copy button.

    Date to timestamp

    Fill in year, month, day, hour, minute and second. The fields are read in the time zone you picked, so 09:00 in Dubai gives a different timestamp from 09:00 in London. The tool also catches impossible dates, such as 31 February, and local times that do not exist because clocks jumped forward for daylight saving.

    Batch

    Paste a column of timestamps from a log or database export, one per line, and convert them all at once. Copy the result as CSV or download it with a byte-order mark so a spreadsheet opens it cleanly. Invalid lines are marked rather than silently dropped.

    Difference

    Enter two timestamps or two dates and see the gap as years, months, days and hours, plus total seconds, minutes, hours, days and weeks. For plain calendar gaps there is also the Age in Days page.

    Time zones, honestly

    Store and compare timestamps in UTC; convert at the edges, when a person needs to read them. Unix time also ignores leap seconds: every day is treated as exactly 86,400 seconds. If you need to plan a meeting across zones rather than decode a number, the Time Zone Converter is the better fit.

    Finding timestamps in the first place

    Long log files often hide epoch values inside text. A pattern like \b1[0-9]{9}\b will pull ten-digit seconds out of a line; try it in the Regex Tester and paste the matches into the batch box here.

    Frequently asked questions

    What is the Unix epoch?

    The starting point of Unix time: 1 January 1970, 00:00:00 UTC. A timestamp counts the seconds elapsed since then.

    How do I tell seconds from milliseconds?

    Count the digits. Current timestamps have 10 digits in seconds and 13 in milliseconds. Auto-detect applies this rule for you.

    Can a timestamp be negative?

    Yes. Negative values are moments before 1 January 1970. For example, -1 is 23:59:59 UTC on 31 December 1969.

    What is the year 2038 problem?

    A signed 32-bit counter cannot hold a value above 2,147,483,647, which is 19 January 2038 at 03:14:07 UTC. Software that still uses 32-bit time will overflow at that moment.

    Does the converter send my data anywhere?

    No. Conversion uses your browser and its time zone data. Nothing is uploaded.