Unix Timestamp Конвертер
Конвертируйте Unix timestamps в человекочитаемые даты и наоборот. Поддерживает секунды, миллисекунды, микросекунды и наносекунды.
Введите временную метку
Поддерживает временные метки Unix в секундах, миллисекундах, микросекундах и наносекундах
1772318296
Секунды с 01 янв 1970.
Год
Месяц
День
Час
Минута
Секунда
Часовой пояс
Временная метка
1772318296
GMT
Sat, 28 Feb 2026 22:38:16 GMT
Ваш часовой пояс
Sat Feb 28 2026 22:38:16 GMT+0000 (Coordinated Universal Time)
Как использовать этот Unix Timestamp Конвертер
- Enter a Unix timestamp in the input field, or use the current timestamp.
- The tool automatically detects if the timestamp is in seconds, milliseconds, microseconds, or nanoseconds.
- View the converted date in both GMT and your local timezone.
- Use the date picker to select a date and convert it back to a Unix timestamp.
What is a Unix Timestamp?
A Unix timestamp is a way of tracking time as a single number that represents the number of seconds that have elapsed since the Unix epoch: 00:00:00 UTC on January 1, 1970, minus leap seconds. This system is widely used in computing because it provides a simple, standardized way to represent dates and times across different systems and programming languages.
Tip
Unix timestamps are timezone-independent, making them ideal for storing and exchanging date/time information globally. They're commonly used in databases, APIs, and file systems.
The Year 2038 Problem
The Year 2038 problem (also known as Y2038 or Unix Millennium Bug) is a time computing issue that will occur on January 19, 2038 at 03:14:07 UTC. Many systems store Unix timestamps as a signed 32-bit integer, which has a maximum value of 2,147,483,647. Once this number is exceeded, it will overflow and wrap around to negative values, causing dates to reset to December 13, 1901.
Addressing Y2038
Modern systems are addressing this by migrating to 64-bit integers, which won't overflow for approximately 292 billion years. However, legacy systems and embedded devices may still be affected.
Key Features
- Converts Unix timestamps to human-readable dates and vice versa
- Supports seconds, milliseconds, microseconds, and nanosecond formats
- Displays results in both GMT and your local timezone
- Shows relative time (e.g., '2 hours ago')
- Date picker for reverse conversion to timestamps
- Live current timestamp display
- Entirely client-side with no server dependency
Common Use Cases
- Converting API response timestamps to readable dates
- Debugging time-related issues in database records
- Generating timestamps for cron jobs and scheduled tasks
- Verifying token expiration times in JWTs and sessions
- Converting log file timestamps for incident analysis
- Setting cache expiration times in web applications
Часто задаваемые вопросы (FAQ)
What is the Unix epoch?
The Unix epoch is the reference point for Unix timestamps: January 1, 1970 at 00:00:00 UTC. All Unix timestamps represent the number of seconds elapsed since this moment. Dates before the epoch are represented as negative numbers.
How do I tell if a timestamp is in seconds or milliseconds?
Timestamps in seconds are typically 10 digits long (e.g., 1700000000), while millisecond timestamps are 13 digits (e.g., 1700000000000). This tool automatically detects the format based on the number of digits you enter.
Do Unix timestamps account for leap seconds?
No. Unix timestamps deliberately ignore leap seconds. Each day is treated as exactly 86,400 seconds. When a leap second occurs, the Unix timestamp either repeats a second or skips one, depending on the system implementation. This keeps timestamp arithmetic simple and predictable.