We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Instantly convert between human-readable dates and UNIX timestamps (seconds/milliseconds). Perfect for development, debugging, and data processing.
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
A Unix timestamp counts time from the Epoch: January 1, 1970 at 00:00:00 UTC. The timestamp represents a moment; the date and clock display is a way to view that moment in a time zone. This converter formats the date using the local time zone of the device running the page, so the same timestamp can appear as different clock readings on devices in different zones.
Choose the timestamp unit explicitly. Seconds and milliseconds describe the same timeline at different scales:
milliseconds = seconds × 1,000
seconds = floor(milliseconds ÷ 1,000)
The date field displays through whole seconds. The timestamp field preserves the chosen unit, including milliseconds.
The tool does not infer the unit from the number of digits. A value intended as seconds must be read as seconds; a millisecond value read as seconds points to a much later date. Selecting a different unit while a timestamp is entered rescales the entered number by 1,000. Switching from milliseconds to seconds discards any sub-second remainder by rounding down.
The date field accepts a date-time entry such as 2026-09-28 09:30:00. It is interpreted in the device’s local time zone and converted to the selected timestamp unit. The date display does not show a zone label, so record the zone separately when sharing a local date-time with someone elsewhere.
Choose seconds or milliseconds to match the source value or the format required by the receiving system.
Enter an integer timestamp to see its local date and time, or enter a date and time to calculate the timestamp. The paired field updates from the entered value.
Check the unit and compare the displayed local clock time with the expected time zone. Copy the timestamp or date using the adjacent copy control.
The hour, day, week, month, and year shortcuts calculate from the device’s current time when selected. They fill both conversion fields using the currently selected unit. These shortcuts are useful for making a quick reference value, but they do not add a duration to a timestamp already in the input box.
The live “now” area shows a seconds timestamp and a local date-time. Its pause control freezes that clock display; it does not pause a conversion already entered in the main fields.
When a log contains a numeric time, select the unit specified by that log’s documentation before reading its local date.
When supplying a date to an API, confirm whether its field expects seconds or milliseconds, then copy the value in that unit.
Use the timestamp as the shared moment, and include a named time zone alongside any copied local date and time.
The date field uses the device’s local time zone and does not label the zone. The timestamp itself is independent of local display; compare or share it with an explicit time-zone reference when needed.
No. Choose the unit manually. The same digits interpreted in the wrong unit produce a different moment.
The date field is formatted only to whole seconds. The timestamp field can still contain milliseconds, so copy that field when the sub-second value matters.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Match the unit expected by your log, API, or timestamp source. Do not rely on digit count alone.
Enter the timestamp in its selected unit, or type a local date-time in the date field. The other field updates to show the corresponding value.
Copy the result and note its unit. If you share the date field, include the time zone used by your device.
Use cases
See how the tool fits into real work and everyday tasks.
Convert an event value after checking the logging system’s unit, then compare the local date with the incident timeline.
Convert a local date-time and use the unit specified by the API contract before pasting the result.
Send the timestamp or pair the displayed local time with its time zone so a colleague can interpret it consistently.
Notes
Review scope, result limitations, and important precautions before use.
Related
Discover related tools, collections, and available API capabilities.