Convert unix timestamp

area69

It would be very convenient to be able to convert unix/epoch timestamps into human readable format. Example query that should trigger this:

Currently I use this website, but it would be a lot faster for me to just get a similar tool in Kagi.

brandtkurowski

The "quick answer" doesn't consistently give me the answer.

When I searched for "unix timestamp 1743495477" then click "Quick Answer", I get

The Unix timestamp 1743495477 represents the number of seconds that have elapsed since January 1, 1970, 00:00:00 Coordinated Universal Time (UTC) 12. Online tools, such as the Unix Timestamp Converter, can convert Unix timestamps into human-readable dates and vice versa 3. These converters support timestamps in seconds, milliseconds, microseconds, and nanoseconds 45.

which isn't particularly helpful, so I started to request this feature. But then I saw this post, so I tried harder. It turns out that searching for "unix timestamp 1743495477?" gives me a more helpful "Quick Answer":

The Unix timestamp 1743495477 corresponds to March 30, 2025, 09:37:57 PM (Pacific Daylight Time).

A Unix timestamp is a way to track time as a running total of seconds since January 1st, 1970 at UTC 12.

I would've expected the same results either way, but even if the question mark shortcut gives me a different answer, I would still suggest the manual invocation of "Quick Answer" could be more helpful in this case.

dix

Hi,

Having the same issue today with Quick Answer and in a way with Assistant.

I'm trying to get a readable format for the "1762937286275" timestamp, which is:

If I ask QA, I basically get NOW(), it just doesn't care about the actual value I give.

And I noticed that I must have hit some sort of cache because no matter how many times I type the same question, I get the exact same answer.
If I change a thing in my question, I get a wrong answer, but with NOW() updated to the time of my new request.

Notice how the time is updated at each new request.

Meanwhile with Assistant (using Code here), I get the right date, but the time used is... not right. It seems like the NOW() of the first request in the thread.
If I ask the same question later in the thread, the time is the same as the first response, but still wrong.