Epoch & Unix Timestamp Converter

Convert timestamps instantly. Nothing leaves your browser.

100% in your browser. Nothing uploaded.

Now —
Enter a Unix timestamp above.
Enter a date string above.

Batch Log Converter


        

      

      
Paste log lines above and click Convert.

    


    


    

      
Convert Unix timestamps online without upload

      

        This free epoch converter runs entirely in your browser. No data is sent to a server — making it safe to use with sensitive log files, internal timestamps, or production traces. Paste a Unix timestamp and get the equivalent UTC date, local time, ISO 8601, and a relative human description. Or go the other way: type a date and get the Unix timestamp in both seconds and milliseconds.
      


      
How to use the single converter

      
    
        
  1. Paste a Unix timestamp (seconds or milliseconds) into the left pane — the result appears instantly.
    2. 
        
  2. To convert a date to a Unix timestamp, type it in the right pane. ISO 8601, RFC 2822, and plain YYYY-MM-DD all work.
    3. 
        
  3. Click Now in either pane to pre-fill with the current time.
    4. 
        
  4. Copy any row value with its inline Copy button.
    5. 
      


      
How to use the batch converter

      
    
        
  1. Paste lines of log output into the Input pane (or click Sample to load an example).
    2. 
        
  2. Click Convert. Every 10- or 13-digit timestamp in the text is annotated with its ISO date in square brackets.
    3. 
        
  3. Click Copy output to paste the annotated log wherever you need it.
    4. 
      


      
Seconds vs milliseconds

      

        Unix time is officially defined in seconds. But most modern APIs and databases (JavaScript, Java, Python's time.time_ns, Redis, MongoDB) expose time in milliseconds or nanoseconds. This converter auto-detects the unit: numbers with 13 or more digits are treated as milliseconds; shorter numbers are treated as seconds. The batch converter applies the same heuristic to every number it finds in your log lines.
      


      
When to use it

      
    


    
    
    

      
FAQ

      

        What is a Unix timestamp / epoch time?
        
A Unix timestamp is the number of seconds (or milliseconds) that have elapsed since 00:00:00 UTC on 1 January 1970, known as the Unix epoch. It is the most common way to represent a point in time in software: a single integer that is timezone-independent, compact, and easy to compare and store. The epoch is the reference point — time zero. Timestamps before 1970 are negative.

      

      

        Is it safe to paste private log data here?
        
Yes. All conversion runs in JavaScript inside this browser tab. Nothing you paste is sent to any server, stored, or logged. You can use this tool offline once the page has loaded, which makes it suitable for air-gapped environments or when working with sensitive production traces.

      

      

        Does it support milliseconds automatically?
        
Yes. If the number you enter has 13 or more digits, it is treated as milliseconds. Shorter numbers are treated as seconds. The same heuristic applies during batch conversion: every number in your log lines is checked against this threshold before it is annotated. This covers the overwhelming majority of real-world logs, which use either 10-digit (seconds) or 13-digit (milliseconds) timestamps.

      

      

        How does the batch converter find timestamps in log lines?
        
It scans each line with a regular expression that matches standalone 10–13-digit integers (not embedded in longer numbers). Each match is checked: if the resulting date falls between 1970 and 2100, it is annotated with its ISO 8601 equivalent in square brackets. Matches that fall outside that range are left untouched so things like error codes or counters are not mistakenly converted.

      

      

        What date formats does the date-to-timestamp converter accept?
        
Anything that the browser's built-in Date constructor can parse: ISO 8601 (e.g. 2024-06-02T00:00:00Z), bare date strings (2024-06-02, treated as UTC midnight), and RFC 2822 strings. Ambiguous formats without a timezone are interpreted according to the browser's local timezone, so prefer ISO 8601 with an explicit Z or offset for predictable results.

      

      

        Does it work offline?
        
Yes, once the page has loaded. There are no runtime API calls, so the converter keeps working on a plane, behind a firewall, or after you disconnect from Wi-Fi.