Developer & data utilities
Epoch time converter
Convert Unix timestamps to readable dates and back.
Run Epoch time converter online
In-browserDocument processing runs on your device. External resources may still load.
Enable JavaScript to use the interactive tool. Read the instructions, limitations and FAQs below before starting.
Unix epoch time (also called Unix timestamp) is the number of seconds that have elapsed since January 1, 1970, 00:00:00 UTC. It is the standard time representation in computing — used in databases, APIs, log files, programming languages, and system clocks. Converting between epoch time and human-readable date/time is a frequent developer task.
This tool converts epoch timestamps (in seconds or milliseconds) to human-readable date and time in any timezone, and converts human-readable dates back to epoch timestamps. It also displays the current epoch time in real time for reference.
Developers encounter epoch timestamps in API responses, database records, JWT token expiry fields (exp), server logs, and file metadata. Converting timestamps helps with debugging, reading log files, verifying token validity, and correlating events across systems with different time representations.
How to use this utility
- Use the controls below—paste text, pick files, or adjust options as described on the tool.
- Click the main action button. Processing runs in your browser on this device.
- Download or copy the output. Check the processing note for any external services used by this operation.
Common use cases
- Converting a JWT token's 'exp' (expiry) claim from epoch to human-readable date to check if it's expired.
- Converting a Unix timestamp from a server log to a human-readable date for incident analysis.
- Getting the epoch timestamp for a specific date to use in an API query with a date range filter.
- Converting a database timestamp column value to local time for debugging.
- Verifying that a file's modification time (stored as epoch) matches the expected update date.
Tips for best results
- 1Be aware of the difference between second-precision (10-digit) and millisecond-precision (13-digit) epoch timestamps — using the wrong precision produces incorrect conversion results (off by 1000x).
- 2Always specify the timezone when converting epoch to human-readable time — the same epoch value maps to different local times in different timezones.
- 3For JWT tokens, the 'iat' (issued at) and 'exp' (expiry) fields are standard epoch seconds — paste the value here to get a readable date.
- 4Remember that epoch time is timezone-independent (always UTC) — the conversion to a specific timezone happens in the display, not in the epoch value itself.
- 5For events around Daylight Saving Time transitions, verify the converted time is correct for the specific transition date and location.
Frequently asked questions
- Is Konnect2Tools free?
- Yes. These in-browser tools are completely free to use with no account required for core functionality.
- Do my files leave my device?
- Browser document operations run locally, except where the operation uses an external service, such as AI summarisation. Read the processing note before using sensitive inputs.
- Is the Epoch time converter tool safe to use?
- Local operations process document content on your device. External-service operations may send inputs as described in the processing note. Keep originals and inspect the output.
- What is the Unix epoch?
- The Unix epoch is the point in time represented by timestamp 0: January 1, 1970, 00:00:00 UTC. All Unix timestamps represent the number of seconds (or milliseconds, in some systems) elapsed since this moment.
- How do I know if my timestamp is in seconds or milliseconds?
- Timestamps in seconds are typically 10 digits (e.g., 1700000000 for 2023). Millisecond timestamps are 13 digits (e.g., 1700000000000). JavaScript's Date.now() returns milliseconds; Python's time.time() returns seconds (as a float).
- What is the maximum date representable as a Unix timestamp?
- With 32-bit signed integers, the maximum is January 19, 2038 (the 'Year 2038 problem'). With 64-bit integers (used by modern systems), Unix time can represent dates billions of years into the future.
- How is epoch time different from ISO 8601 date format?
- Epoch time is a single integer representing seconds since 1970, without timezone ambiguity (always UTC). ISO 8601 is a human-readable format (e.g., 2024-01-15T10:30:00Z) that includes date, time, and optional timezone. Both representations describe the same moment; epoch is more compact and machine-friendly.
Related tools
Continue with another utility in developer & data utilities.