JavaScript Date setUTCMilliseconds() Method

What You’ll Learn

setUTCMilliseconds() writes the sub-second fraction (0–999) inside the current UTC second. This guide covers syntax, ISO precision, overflow, and comparisons with local setMilliseconds() and getTime().

Introduction

ISO timestamps and server logs often include fractional seconds. After reading the UTC fraction with getUTCMilliseconds(), setUTCMilliseconds() writes it back without touching local timezone offsets.

This is not the same as setting total epoch time—that is setTime() or getTime(). Here you adjust only the millisecond hand inside the current UTC second.

Understanding the setUTCMilliseconds() Method

Date.prototype.setUTCMilliseconds(millisecondsValue) accepts an integer for the UTC sub-second fraction. Values outside 0–999 normalize into adjacent UTC seconds instead of being rejected.

For local sub-second writes, use setMilliseconds(). For a full UTC time including ms in one call, use setUTCHours(h, m, s, ms).

📝 Syntax

dateObj.setUTCMilliseconds(millisecondsValue)

Parameters

• millisecondsValue — Integer for the UTC sub-second fraction (typically 0–999; overflow normalizes).

Return value

• Updated epoch milliseconds after the change.
• NaN if the Date was invalid before the call.

Examples Gallery

Open DevTools Console (F12) or use Try-it links. Examples use Date.UTC() for predictable UTC times.

const date = new Date(Date.UTC(2026, 2, 1, 12, 30, 45, 120));
date.setUTCMilliseconds(500);

console.log(date.getUTCSeconds());         // 45
console.log(date.getUTCMilliseconds());    // 500
console.log(date.toISOString());           // "2026-03-01T12:30:45.500Z"

45
500
2026-03-01T12:30:45.500Z

const date = new Date(Date.UTC(2026, 2, 1, 12, 30, 45, 789));
date.setUTCMilliseconds(0);

console.log(date.getUTCSeconds());         // 45
console.log(date.getUTCMilliseconds());    // 0
console.log(date.toISOString());           // "2026-03-01T12:30:45.000Z"

45
0
2026-03-01T12:30:45.000Z

const date = new Date(Date.UTC(2026, 2, 1, 9, 0, 0, 0));
date.setUTCHours(12, 30, 45, 250);

console.log(date.getUTCHours());           // 12
console.log(date.getUTCMilliseconds());    // 250
console.log(date.toISOString());           // "2026-03-01T12:30:45.250Z"

12
250
2026-03-01T12:30:45.250Z

const original = new Date(Date.UTC(2026, 2, 1, 12, 30, 45, 100));
const adjusted = new Date(original);
adjusted.setUTCMilliseconds(750);

console.log("Original ms:", original.getUTCMilliseconds());  // 100
console.log("Adjusted ms:", adjusted.getUTCMilliseconds());  // 750

Original ms: 100
Adjusted ms: 750

const date = new Date(Date.UTC(2026, 2, 1, 12, 30, 45, 0));
date.setUTCMilliseconds(1500);

console.log(date.getUTCSeconds());         // 46
console.log(date.getUTCMilliseconds());    // 500

46
500

🚀 Common Use Cases

• ISO timestamps — align fractional seconds in toISOString() output.
• UTC second rounding — setUTCMilliseconds(0) before second-level compare.
• Test fixtures — pin exact UTC ms in unit tests with Date.UTC().
• Log alignment — normalize sub-second noise in server log timestamps.
• Animation timing — fine-tune UTC sub-second fields in frame loops.
• Clone + mutate — copy a Date before changing UTC milliseconds.

📝 Notes

• setUTCMilliseconds() adjusts the fraction inside the current UTC second (0–999 typical range).
• Not the same as setTime(epochMs), which replaces the entire instant.
• Mutates the original Date—clone with new Date(date) when needed.
• Returns epoch ms, not the Date—no fluent chaining on the return value.
• Overflow normalizes (1500 → next UTC second + 500 ms).
• Use setMilliseconds for local clocks; setUTCMilliseconds for ISO/server rules.

💡 Best Practices