JavaScript Date setMinutes() Method

What You’ll Learn

setMinutes() writes the minute (0–59) on a Date in local time, with optional seconds and milliseconds. This guide covers syntax, scheduling patterns, overflow, and comparisons with UTC setters.

Introduction

“Start in 15 minutes,” “round to the top of the hour,” and time-picker forms all need to change the minute hand on a Date. After reading minutes with getMinutes(), setMinutes() writes them back in local time.

Like other setters, it mutates the original object and returns epoch milliseconds—not the Date for chaining.

Understanding the setMinutes() Method

Date.prototype.setMinutes(minute [, second [, millisecond]]) accepts a local minute and up to two optional sub-minute fields. When you pass only the minute, the hour stays the same unless overflow normalization rolls into the next hour.

Values outside normal ranges roll forward or backward— setMinutes(75) on 12:30 becomes 13:15. For UTC minute writes, use setUTCMinutes().

📝 Syntax

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

Parameters

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

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 the Date constructor for predictable local times.

const date = new Date(2026, 2, 1, 12, 15, 45);
date.setMinutes(30);

console.log(date.getHours());    // 12
console.log(date.getMinutes());  // 30
console.log(date.getSeconds());  // 45

12
30
45

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

console.log(date.getHours());         // 14
console.log(date.getMinutes());       // 0
console.log(date.getSeconds());       // 0
console.log(date.getMilliseconds());  // 0

14
0
0
0

const date = new Date(2026, 2, 1, 12, 50, 30);
date.setMinutes(date.getMinutes() + 15);

console.log(date.getHours());    // 13
console.log(date.getMinutes());  // 5
console.log(date.getSeconds());  // 30

13
5
30

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

console.log(date.getMinutes());       // 45
console.log(date.getSeconds());       // 30
console.log(date.getMilliseconds());  // 500

45
30
500

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

console.log(date.getHours());    // 13
console.log(date.getMinutes());  // 15
console.log(date.getSeconds());  // 45

13
15
45

🚀 Common Use Cases

• Meeting delays — push start time with getMinutes() + N.
• Hourly buckets — setMinutes(0, 0, 0) for report windows.
• Time pickers — apply user-selected minutes to a Date.
• Cron-style snaps — align to :00 or :30 marks.
• Test fixtures — pin exact minute/second/ms in unit tests.
• Clone + mutate — copy a Date before changing minutes for comparisons.

📝 Notes

• setMinutes() uses local time minutes 0–59 (overflow normalizes).
• Mutates the original Date—clone with new Date(date) when needed.
• Returns epoch ms, not the Date—no fluent chaining on the return value.
• Optional second and millisecond args default to 0 when omitted after minute.
• For adding duration across hours, getMinutes() + N is simpler than manual hour math.
• Use setUTCMinutes when rules follow UTC, not local wall clock.

💡 Best Practices