Jak Konwertować Unix Timestamps na Czytelne Daty (Krok po Kroku)
Quick Answer
Aby skonwertować timestamp do daty: wklej Unix timestamp do Timestamp Converter i czytelna data w UTC i lokalnej timezone pojawia się natychmiast. Aby skonwertować datę do timestampa: wprowadź datę. Całe przetwarzanie odbywa się lokalnie.
Introduction
Unix timestamp (nazywany też epoch time lub POSIX time) to liczba sekund, które upłynęły od 1 stycznia 1970, 00:00:00 UTC (Unix epoch). Timestampy są szeroko używane w bazach danych, logach i API ponieważ są timezone-independent i łatwe do porównania. Jednak ludzie nie mogą ich bezpośrednio odczytać —1693526400 jest bez sensu bez konwersji.
Step by Step
-
Open the Timestamp Converter tool
Go to the Timestamp Converter tool page. The tool supports bidirectional conversion: timestamp to date, and date to timestamp.
-
Enter your Unix timestamp
Paste the timestamp into the input field. The tool auto-detects whether the value is in seconds (10 digits) or milliseconds (13 digits). For example, 1693526400 is seconds, 1693526400000 is milliseconds.
-
Read the human-readable date
The tool converts the timestamp to a date and displays it in both UTC and your local timezone. For example, 1693526400 becomes 2023-09-01 00:00:00 UTC. The result appears instantly.
-
Convert a date to a timestamp (reverse)
To convert a date to a Unix timestamp, enter the date in the date input field. The tool computes the epoch value in both seconds and milliseconds. This is useful for API calls that require timestamps.
-
Copy the result
Click Copy to copy the converted date or timestamp to your clipboard for use in your application, log analysis, or API request.
Examples
Timestamp (seconds) to date
Input: 1693526400
Output: 2023-09-01 00:00:00 UTC
Timestamp (milliseconds) to date
Input: 1693526400000
Output: 2023-09-01 00:00:00 UTC
Date to Unix timestamp
Input: 2023-09-01 00:00:00 UTC
Output: 1693526400 (seconds) / 1693526400000 (milliseconds)
Current Unix epoch
Input: now
Output: Approximately 1725235200 (as of 2024-09-02)
Common Problems
- Confusing seconds and milliseconds —JavaScript uses milliseconds (13 digits), Unix and most APIs use seconds (10 digits). Mixing them gives dates in 1970 or the year 50000+.
- Timezone confusion —Unix timestamps are always UTC. When displaying, convert to the user's local timezone or specify UTC explicitly.
- The Year 2038 problem —32-bit signed integers overflow on 2038-01-19 03:14:07 UTC. Use 64-bit integers or JavaScript numbers (which are 64-bit floats) to avoid this.
- Negative timestamps —dates before 1970-01-01 have negative timestamps. Some systems do not support them.
Tips
- Always check whether an API expects seconds or milliseconds —this is the most common timestamp bug.
- Use ISO 8601 strings (e.g., "2023-09-01T00:00:00Z") for human-readable timestamps in APIs; use Unix epoch for storage and computation.
- JavaScript Date.now() returns milliseconds; divide by 1000 and floor to get seconds.
- Use our Timestamp Converter for instant, private conversion —no data leaves your browser.