JavaScript Date setUTCHours() Method

What You’ll Learn

setUTCHours() writes the hour (0–23) on a Date in UTC, with optional minutes, seconds, and milliseconds. This guide covers syntax, ISO scheduling, overflow, and comparisons with local setHours().

Introduction

Global events, cron jobs, and ISO timestamps often schedule by UTC clock time. After reading the UTC hour with getUTCHours(), setUTCHours() writes it back without local timezone offsets.

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

Understanding the setUTCHours() Method

Date.prototype.setUTCHours(hour [, minute [, second [, millisecond]]]) accepts a 24-hour UTC hour and up to three optional sub-hour fields. When you pass only the hour, UTC minutes and seconds stay the same unless overflow normalization rolls the UTC calendar day.

Verify results with toISOString() or UTC getters. Hour 15 is 3:00 PM UTC in 24-hour time.

📝 Syntax

dateObj.setUTCHours(hour)
dateObj.setUTCHours(hour, minute)
dateObj.setUTCHours(hour, minute, second)
dateObj.setUTCHours(hour, minute, second, millisecond)

Parameters

• hour — Integer 0–23 in UTC 24-hour time (overflow normalizes).
• minute (optional) — 0–59 UTC.
• 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, 30, 45));
date.setUTCHours(10);

console.log(date.getUTCHours());     // 10
console.log(date.getUTCMinutes());   // 30
console.log(date.toISOString());    // "2026-03-01T10:30:45.000Z"

10
30
2026-03-01T10:30:45.000Z

const meeting = new Date(Date.UTC(2026, 2, 1, 9, 45, 30, 500));
meeting.setUTCHours(15, 0, 0, 0);

console.log(meeting.getUTCHours());         // 15
console.log(meeting.getUTCMinutes());       // 0
console.log(meeting.toISOString());         // "2026-03-01T15:00:00.000Z"

15
0
2026-03-01T15:00:00.000Z

const date = new Date(Date.UTC(2026, 2, 1, 22, 30, 0));
date.setUTCHours(date.getUTCHours() + 2);

console.log(date.getUTCHours());   // 0
console.log(date.getUTCDate());    // 2

0
2

const date = new Date(Date.UTC(2026, 2, 1, 12, 30, 45));
const ms = date.setUTCHours(10);

console.log("Type:", typeof ms);                    // "number"
console.log("Matches getTime():", ms === date.getTime()); // true

Type: number
Matches getTime(): true

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

console.log(date.getUTCHours());   // 1
console.log(date.getUTCDate());    // 2

1
2

🚀 Common Use Cases

• Global events — snap to setUTCHours(15, 0, 0, 0) for 3 PM UTC.
• Server cron — schedule jobs on UTC wall clock, not local server TZ.
• ISO APIs — align parsed timestamps to UTC hour boundaries.
• Relative UTC shifts — postpone with getUTCHours() + N.
• Log bucketing — group entries by UTC hour for global dashboards.
• Clone + mutate — copy a Date before changing UTC hours.

📝 Notes

• setUTCHours() uses 24-hour UTC time (0 = midnight UTC, 12 = noon UTC).
• 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 (hour 25 → next UTC day hour 1).
• For real timezone conversion, use Intl or libraries—not naive offset math on getters.
• Use setHours for local user-facing clocks; setUTCHours for ISO/server rules.

💡 Best Practices