Unix Timestamp to Date Converter Online

Copy the bare number, without quotation marks, commas or the field name around it, paste it into the seconds field and press convert. The tool reads the value as seconds since the epoch and prints the matching date and time. Stray characters around the digits will break the parse, so tidy the fragment up before pasting it.

Almost certainly a time zone difference. Servers usually log in UTC, while this converter renders the result according to your operating system's settings. The gap is exactly your offset. To compare directly, either switch your machine to UTC temporarily or subtract your own offset from what you see here.

Your value is in milliseconds — the unit JavaScript, MongoDB and several logging stacks use. This field expects seconds, so the number is a thousand times too large and the date shoots off into the fifty-somethingth millennium. Delete the final three digits and convert again; those digits are only fractions of a second.

Zero is the epoch itself, midnight UTC on 1 January 1970. In real data it almost never represents a genuine date; it usually marks an uninitialised field — a default value, a failed string parse or an empty response. If an export is full of 1 January 1970, look for a data-loading bug rather than a fifty-year-old event.

Yes. Negative values point to moments before 1970 and decode normally: minus 86400 gives 31 December 1969. Numbers like these turn up in historical archives and when dates of birth are stored as epoch values. If the field resists a typed minus sign, paste the whole value in from the clipboard instead.

The digits after the decimal point are fractions of a second and barely affect the date shown. The tool is built for whole seconds, so it is safer to round the value or simply strip everything after the point before entering it. One-second precision is already more than log reading and event correlation usually need.

Nowhere beyond your own tab. A script inside the page does the arithmetic, no network request is made during conversion, and no history of what you entered is kept. That makes it reasonable to decode timestamps from internal systems and customer exports without clearing it with your security team first.