JavaScript Date setUTCMinutes() Method

What You’ll Learn

setUTCMinutes() writes the minute (0–59) on a Date in UTC, with optional seconds and milliseconds. This guide covers syntax, hour snaps, relative minutes, overflow, and comparisons with local setMinutes().

Introduction

Cron jobs, server logs, and ISO timestamps often schedule by UTC clock time. After reading the UTC minute with getUTCMinutes(), setUTCMinutes() writes it back without local timezone offsets.

Like setMinutes(), it mutates the Date and returns epoch milliseconds. Use UTC getters and setters together—do not mix local setMinutes with UTC getUTCMinutes in one step.

Understanding the setUTCMinutes() Method

Date.prototype.setUTCMinutes(minute [, second [, millisecond]]) accepts a UTC minute and up to two optional sub-minute fields. When you pass only the minute, UTC seconds and milliseconds stay the same unless overflow normalization rolls the UTC clock.

Verify results with toISOString() or UTC getters. For a full UTC time including ms in one call, use setUTCHours(h, m, s, ms).

📝 Syntax

dateObj.setUTCMinutes(minute)
dateObj.setUTCMinutes(minute, second)
dateObj.setUTCMinutes(minute, second, millisecond)

Parameters

• minute — Integer 0–59 in UTC time (overflow normalizes).
• second (optional) — 0–59 UTC.
• millisecond (optional) — 0–999 UTC.

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, 15, 45));
date.setUTCMinutes(30);

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

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

const date = new Date(Date.UTC(2026, 2, 1, 14, 37, 22, 800));
date.setUTCMinutes(0, 0, 0);

console.log(date.getUTCHours());           // 14
console.log(date.getUTCMinutes());         // 0
console.log(date.getUTCSeconds());         // 0
console.log(date.getUTCMilliseconds());    // 0
console.log(date.toISOString());           // "2026-03-01T14:00:00.000Z"

14
0
0
0
2026-03-01T14:00:00.000Z

const date = new Date(Date.UTC(2026, 2, 1, 12, 50, 30));
date.setUTCMinutes(date.getUTCMinutes() + 15);

console.log(date.getUTCHours());    // 13
console.log(date.getUTCMinutes());  // 5
console.log(date.getUTCSeconds());  // 30

13
5
30

const date = new Date(Date.UTC(2026, 2, 1, 9, 0, 0, 0));
date.setUTCMinutes(45, 30, 500);

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

45
30
500
2026-03-01T09:45:30.500Z

const date = new Date(Date.UTC(2026, 2, 1, 12, 30, 45));
date.setUTCMinutes(75);

console.log(date.getUTCHours());    // 13
console.log(date.getUTCMinutes());  // 15
console.log(date.getUTCSeconds());  // 45

13
15
45

🚀 Common Use Cases

• UTC cron alignment — snap to setUTCMinutes(0, 0, 0) for hourly jobs.
• ISO scheduling — set exact UTC :MM:SS.ms on parsed timestamps.
• Relative UTC shifts — postpone with getUTCMinutes() + N.
• Log bucketing — group entries by UTC minute for global dashboards.
• API deadlines — align server-side cutoff times in UTC.
• Clone + mutate — copy a Date before changing UTC minutes.

📝 Notes

• setUTCMinutes() adjusts the minute hand in UTC (0–59 typical range).
• 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 (minute 75 → next UTC hour + 15 minutes).
• Omitting optional args does not reset seconds/ms to zero—only pass them when you intend to change them.
• Use setMinutes for local clocks; setUTCMinutes for ISO/server rules.

💡 Best Practices