Timestamp converter

A log shows 1729516800, a JavaScript value ends in three extra zeros, and nobody agrees which local time the event represents. This is the usual timestamp problem. The converter on this page can turn the number into a readable date, but only after you identify its unit and timezone.

This guide covers Unix timestamps, seconds, milliseconds, UTC, decimal hours, and practical checks with Clockbeam.

Quick Answer

A Unix timestamp counts elapsed time from 1970-01-01 00:00:00 UTC. Check whether the value uses seconds or milliseconds, enter it in the converter on this page, then confirm the displayed timezone. For example, 1729516800 is 2024-10-21 13:20:00 UTC. The same instant has a different clock reading in New York or Tokyo.

What is a timestamp?

A timestamp records an instant as a number or a date-time string. A Unix timestamp counts seconds since the Unix epoch, which began at midnight UTC on January 1, 1970. Unix time ignores leap seconds, as documented by MDN’s Unix time glossary.

Seconds and milliseconds are the two units you will see most often. A server log might store 1729516800 seconds. A browser API might store 1729516800000 milliseconds for the same instant, 2024-10-21 13:20:00 UTC. Divide the millisecond value by 1,000 before using a seconds-based converter. The converter on this page can also read milliseconds directly.

UTC provides the reference point. A local display then applies a timezone offset. The number remains the same while the visible clock changes. A timestamp converter should therefore show the result with UTC or an explicit offset, not only a bare date.

A Unix timestamp identifies an instant; a timezone determines how that instant appears on a clock.

How to use a timestamp converter

Use a fixed sequence so a unit error does not become a timezone argument.

1. Identify the unit. Values around ten digits commonly represent seconds, while values around thirteen digits commonly represent milliseconds. Treat digit length as a clue, not proof.
2. Enter the value. Paste the number into the converter on this page, without commas or extra characters.
3. Select the timezone. Start with UTC when checking a server event. Choose a local timezone when planning a meeting or reviewing a user report.
4. Compare the result. Check the date, time, offset, and seconds against the source record.

For example, convert 1729516800 as seconds. The converter returns 2024-10-21 13:20:00 UTC. If you enter 1729516800000 into a seconds field, the result will land far outside the expected date range. Read as milliseconds, 1729516800000 is the same instant.

To reverse the process, enter a date such as 2024-10-21 00:00:00 UTC and request Unix seconds. That instant is 1729468800 seconds and 1729468800000 milliseconds. Keep the timezone visible in your notes. A developer handing a marketer a value without its unit has created a second problem.

Use the current Unix timestamp on this page to compare the current device time with a converted result. Clockbeam follows the visitor’s device clock, so it can check the clock shown by that browser without adding another synchronization service.

Common timestamp conversion mistakes

Most incorrect results come from three details: unit, timezone, or daylight-saving rules.

• Seconds versus milliseconds. The values 1700000000 and 1700000000000 are the same instant when the first is seconds and the second is milliseconds: 2023-11-14 22:13:20 UTC. Selecting milliseconds for the first value can produce a date near 1970. Selecting seconds for the second can produce an implausibly distant date.
• UTC versus local time. A database may record an event in UTC while your laptop displays it in UTC-5 or UTC+1. Neither clock is necessarily wrong. They are showing different representations of one instant.
• Daylight-saving changes. A local offset can change during the year. An appointment saved with a city timezone can display a different UTC offset after a seasonal clock change.

For a practical check, record the original value, its unit, the source timezone, and the converted output. Also check the device clock used for comparison. Clockbeam reads the visitor’s device clock and does not claim atomic-clock accuracy.

When not to use a timestamp converter

A converter is the wrong tool when the source value is incomplete or the event needs legal or operational verification. Do not rely on a browser conversion alone when:

• the source system has lost its timezone or unit metadata;
• you need an audit record from the original application;
• the device clock may be manually wrong;
• the laptop can sleep or close before a live timer or alarm must run.

Always preserve the original timestamp, unit, timezone, and converted display together.

Decimal to time chart

Decimal hours express part of an hour as a fraction. Multiply the decimal portion by 60 to get minutes. The minutes to hours converter does that conversion, and the reverse, for any length you enter.

A spreadsheet or time report may show 1.75 hours, while a timer needs 1:45:00. Microsoft documents the same general conversion approach for spreadsheet time values: divide or multiply units and apply a time format where needed.

Timestamp formats and examples

Readable date-time strings help people inspect an event. Numeric Unix values help software sort and compare events. Store the format that matches the system, but label it clearly for people.

The Z suffix conventionally marks UTC in ISO-style timestamps. An explicit offset, such as -04:00, tells the reader how the local clock relates to UTC. RFC 9557 describes extensions to Internet date and time formats, including timezone information.

A timestamp becomes easier to debug when its unit and timezone appear beside the value.

How Clockbeam helps you check the current time

Clockbeam gives you a visible browser clock when you need to compare a converted value with the time on your device. It shows the current date and seconds without an account or signup.

You can choose a minimal digital display, flip clock, analog clock, scenic display, or fullscreen view. The fullscreen option suits presentations, classroom work, and an OBS setup where a clock needs to remain visible.

Clockbeam reads the visitor’s device clock. It adds no second synchronization service. City offsets also come from the browser’s timezone data, so a wrong device date, time, or timezone can produce a wrong comparison.

A browser tab cannot keep working after a laptop closes or a device sleeps. Sound also cannot continue in the background after the device has stopped running the page. For those limits, keep the tab open on an awake device and test the page before a live session. The Clockbeam About page explains these device-clock limits.

Timestamp converter questions

What is the difference between a timestamp and a date?

A timestamp identifies an instant relative to the Unix epoch. A date-time display applies a timezone so people can read that instant as a calendar date and clock time.

Are Unix timestamps always in UTC?

Unix timestamps use the Unix epoch at 1970-01-01 00:00:00 UTC as their reference. The number itself has no local timezone, but software can display the result in UTC or a selected local timezone.

Why does the converted time look wrong?

Check the unit first, then check the selected timezone and daylight-saving rules. If the result differs from a browser clock, check the device clock as well, since Clockbeam follows that device clock.

For a reliable handoff, write the value as “1729516800 seconds, UTC” rather than sending the number alone. That label is 2024-10-21 13:20:00 UTC, and it prevents the next timestamp conversion from starting with a guess.

References

• Unix time, MDN Web Docs
• RFC 9557: Date and Time on the Internet, Internet Engineering Task Force
• DateTimeOffset.FromUnixTimeSeconds, Microsoft Learn
• Convert times, Microsoft Support