Unix Timestamp Converter
Convert Unix time to a date and back
🔒 100% бесплатно · без регистрации · файлы не покидают ваше устройство
Computers prefer to store a moment in time as one plain number: the count of seconds since 1 January 1970 UTC, known as Unix time or epoch time. It has no time zone, no daylight-saving rules and no ambiguous formats, which makes it perfect inside databases and logs — and unreadable to humans. The moment you need to answer 'when did this actually happen', that number has to be translated back into a date.
This Unix timestamp converter goes both ways. Paste a value in seconds or milliseconds and it detects the unit for you, then shows the same instant as local time with your time zone, as UTC, as an ISO 8601 string, and as a plain-English relative time such as 'three days ago'. Go the other direction by picking a date and reading back both epoch seconds and milliseconds, choosing whether your input means local wall time or UTC. A live clock at the top ticks with the current timestamp so you can copy the exact value you need for a query, a token or a test fixture.
Зачем нужен Unix Timestamp Converter
Reading timestamps in server logs
Logs and JSON APIs often store created_at as epoch numbers, so converting one instantly tells you whether an incident happened before or after a deploy.
Writing database queries by hand
Grab the current epoch value from the live clock, subtract an interval, and drop it straight into a WHERE clause without leaving the browser.
Checking token and cache expiry
JWT exp values, cookie max-age and cache headers are all epoch seconds — converting them shows exactly when a session or cache entry dies.
Building test fixtures with fixed dates
Pick a date, copy its millisecond timestamp, and use it to freeze time in a unit test so results stay reproducible on any machine.
Полезные советы
- Count the digits when a date looks wrong: 10 digits are seconds, 13 are milliseconds. A date in 1970 usually means milliseconds were read as seconds.
- JavaScript's Date.now() returns milliseconds, but most backends and JWT claims use seconds — divide by 1000 before sending values between them.
- Use the Local / UTC switch on the date side deliberately: the same wall-clock time gives different timestamps depending on which one you pick.
- Unix time has no daylight-saving jumps, so if a converted local time is an hour off from your logs, the offset almost always comes from a server time zone setting, not from the timestamp.
- The ISO 8601 output always ends in Z, which is the safest format to paste into APIs, spreadsheets and issue trackers because it carries its own offset.
Как пользоваться: Unix Timestamp Converter
- 1Copy the live current timestamp, or paste your own
- 2Let the tool detect seconds or milliseconds automatically
- 3Read the local, UTC and ISO 8601 versions of that moment
- 4Or pick a date to get the matching Unix timestamp back
Часто задаваемые вопросы
How do I know if a timestamp is in seconds or milliseconds?▾
Modern second timestamps have 10 digits and millisecond ones have 13. The converter detects this automatically, and you can override it if the guess is wrong.
What is a Unix timestamp exactly?▾
It is the number of seconds elapsed since 1 January 1970 at 00:00:00 UTC, ignoring leap seconds — a single number that means the same instant everywhere.
Which time zone are the results in?▾
You get both: the local line uses your device's time zone, while the UTC and ISO 8601 lines are always zero-offset.