Convert Milliseconds to Date and Time

Convert milliseconds to a readable date and time by entering the timestamp and choosing the correct time zone. The calculator below treats the value as milliseconds since the Unix epoch, 1 January 1970 at 00:00:00 UTC, and returns the corresponding date and time in UTC.

Formula

A Unix timestamp in milliseconds counts elapsed milliseconds from the Unix epoch. To convert it to seconds, divide by 1,000. To find the whole number of days since the epoch, divide by 86,400,000 and round down.

• ms is the input timestamp in milliseconds.
• Days since Unix epoch = floor(ms ÷ 86,400,000), measured in whole days.
• Unix timestamp in seconds = ms ÷ 1,000, measured in seconds. The result retains three decimal places, so milliseconds are represented as fractions of a second.

The calculator’s second output is not itself a formatted calendar date. Use it with a date converter or a programming language’s date functions to display the year, month, day, and clock time. Calendar formatting depends on the time zone you select; UTC is the unambiguous reference used here.

Worked Example

Using the default value of 0 milliseconds:

1. Convert to seconds: 0 ÷ 1,000 = 0.000 seconds.
2. Convert to whole days: floor(0 ÷ 86,400,000) = 0 days.
3. Interpret the timestamp: zero milliseconds is the Unix epoch, 1 January 1970 at 00:00:00 UTC.

The calculator returns 0 whole days and 0.000 seconds. The corresponding calendar date is 1 January 1970 in UTC.

What You’ll Need

• The timestamp as a number, with its unit confirmed as milliseconds rather than seconds, microseconds, or nanoseconds.
• A date-and-time converter, spreadsheet, or programming environment if you need a formatted calendar date. Choose UTC or the intended local time zone.

Step-by-Step

1. Find the timestamp. Copy the complete numeric value from the source. A millisecond Unix timestamp often has 13 digits for contemporary dates, but digit count is only a clue, not proof. Check the source documentation or field name.
2. Enter the number unchanged. Type it into the Timestamp field. Do not add a date, commas, or a time-zone offset. Use the sign as given: values before the epoch can be negative.
3. Read the calculator outputs. Days since Unix epoch shows the number of complete 24-hour periods from the epoch, rounded down. Unix timestamp in seconds divides your input by 1,000 and keeps three decimal places.
4. Convert the timestamp to a calendar date. Give the original millisecond value to a converter that explicitly supports Unix timestamps in milliseconds, or divide by 1,000 if the tool expects seconds. In a spreadsheet, use a date formula or a timestamp conversion feature and verify whether it expects seconds or milliseconds.
5. Set the time zone. Use UTC to match the epoch definition and compare systems consistently. If you need local clock time, convert the UTC result to the relevant named time zone, including the applicable daylight-saving rules.
6. Check the displayed result. Confirm the date, time, and unit against the original context. If possible, convert the displayed date back to milliseconds and check that it matches the input, allowing for any rounding or omitted subsecond digits.

Common Mistakes

• Confusing milliseconds with seconds. A seconds timestamp entered as milliseconds produces a date near 1970; a milliseconds value treated as seconds may be outside the date tool’s supported range. Divide milliseconds by 1,000 only when the receiving tool expects seconds.
• Mixing up the epoch. Unix time counts from 1 January 1970 UTC. Other systems may count from a different starting date or use a different unit. Check the system’s documentation before converting.
• Ignoring the time zone. The same instant can have different calendar dates and clock times in UTC and local time. A date-only difference does not necessarily mean the timestamp is wrong.
• Dropping negative signs or fractional milliseconds. Negative timestamps represent instants before the epoch. Fractional seconds preserve milliseconds; rounding them away loses precision.
• Assuming all timestamps fit a familiar digit count. The number of digits changes over time and with the unit. Identify the unit rather than relying on length alone.

Tips

• Keep the original value and note its unit and time zone alongside any converted date.
• Prefer UTC when storing, comparing, or sharing timestamps. Convert to local time for display when needed.
• For a result that must preserve milliseconds, display three digits after the seconds field, such as 12:34:56.789.
• Use a named time zone, such as one tied to a city or region, rather than a fixed offset when daylight-saving changes matter.
• Remember that Unix timestamps commonly ignore leap seconds. This is suitable for ordinary date conversion, but exact timekeeping across leap seconds can require a specialized time standard.

Troubleshooting

The date is close to 1970. The input may be in seconds but was interpreted as milliseconds, or the reverse. Check the unit and try the correct conversion: milliseconds ÷ 1,000 gives seconds; seconds × 1,000 gives milliseconds.

The date is hours off. Compare the result in UTC first. If UTC is correct but local time differs, check the selected time zone and daylight-saving date.

The converter rejects the value. Look for a sign, extra characters, a missing digit, or an unsupported date range. Confirm the tool accepts Unix time and the specific unit you supplied.

The result is a day off near midnight. A time-zone conversion can move the calendar date forward or backward. Check the full date and clock time, not just the day.

Milliseconds disappear from the output. The display may round to whole seconds. Use a format with three fractional-second digits or retain the original timestamp for exact millisecond precision.

Frequently Asked Questions

What date is 0 milliseconds?
It is 1 January 1970 at 00:00:00 UTC, the Unix epoch.

How do I convert milliseconds to seconds?
Divide the millisecond value by 1,000. For example, 1,500 milliseconds equals 1.5 seconds.

How do I convert milliseconds into a date in a spreadsheet?
Use a date or timestamp function that matches your spreadsheet’s date system and input unit. Many spreadsheet date values count days from a different origin, so do not simply treat milliseconds as spreadsheet days; check the function’s documentation and time-zone behavior.

Can a millisecond timestamp be negative?
Yes. A negative Unix timestamp represents an instant before 1 January 1970 UTC.

Does a timestamp contain a time zone?
A Unix timestamp identifies an instant relative to the UTC epoch; it does not store a local time zone. Choose a zone separately when formatting it as a calendar date.

Why does a converter show a different date?
It may expect seconds instead of milliseconds, use a different epoch, or display the instant in another time zone. Verify all three before deciding the timestamp is incorrect.

Related

• iQOO Z10 vs Z10R 5G: Key Specs, Prices, Differences
• Logitech G930 Sound Cutting Out: Fixes That Work
• Continuous Authentication Settings That Stay Secure and Invisible

in ms | Timestamp | ms | 0 | 0
out days | Days since Unix epoch | days | floor(ms / 86400000) | 0
out date | Unix timestamp in seconds | s | ms / 1000 | 3