JavaScript Date setUTCFullYear() Method

What You’ll Learn

setUTCFullYear() writes the four-digit year on a Date in UTC, with optional month and day overload. This guide covers syntax, UTC year increments, leap-day normalization, and comparisons with local setFullYear().

Introduction

Global contracts, ISO reporting, and server-side schedules often anchor dates in UTC. After reading the UTC year with getUTCFullYear(), setUTCFullYear() writes it back without using local timezone rules.

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

Understanding the setUTCFullYear() Method

Date.prototype.setUTCFullYear(year [, monthIndex [, day]]) accepts a four-digit UTC year and optional zero-based month and day. When you pass only the year, UTC month and day stay the same unless normalization is required (for example UTC Feb 29 in a non-leap year).

The method returns epoch milliseconds, not the Date object. Call each setter on the same Date variable when you need multiple changes—do not chain on the numeric return value.

📝 Syntax

dateObj.setUTCFullYear(year)
dateObj.setUTCFullYear(year, monthIndex)
dateObj.setUTCFullYear(year, monthIndex, day)

Parameters

• year — Four-digit integer (e.g. 2027).
• monthIndex (optional) — Zero-based UTC month 0–11 (January = 0).
• day (optional) — UTC day-of-month 1–31; requires monthIndex when provided.

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 calendar values.

const date = new Date(Date.UTC(2026, 1, 26));
date.setUTCFullYear(2027);

console.log(date.getUTCFullYear());  // 2027
console.log(date.getUTCMonth());     // 1 (February)
console.log(date.getUTCDate());      // 26

2027
1
26

const date = new Date(Date.UTC(2026, 1, 26));
date.setUTCFullYear(2027, 6, 15); // July 15, 2027 UTC

console.log(date.getUTCFullYear());  // 2027
console.log(date.getUTCMonth());     // 6 (July)
console.log(date.getUTCDate());      // 15

2027
6
15

const renewal = new Date(Date.UTC(2026, 2, 15)); // March 15, 2026 UTC
renewal.setUTCFullYear(renewal.getUTCFullYear() + 1);

console.log(renewal.getUTCFullYear());  // 2027
console.log(renewal.getUTCMonth());     // 2 (March)
console.log(renewal.getUTCDate());      // 15

2027
2
15

const date = new Date(Date.UTC(2026, 1, 26));
const ms = date.setUTCFullYear(2027);

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

// Correct multi-step updates on the same Date:
date.setUTCFullYear(2028);
date.setUTCMonth(11);
date.setUTCDate(31);

Type: number
Matches getTime(): true

const date = new Date(Date.UTC(2024, 1, 29)); // Feb 29, 2024 UTC
date.setUTCFullYear(2025);

console.log(date.getUTCFullYear());  // 2025
console.log(date.getUTCMonth());     // 2 (March)
console.log(date.getUTCDate());      // 1

2025
2
1

🚀 Common Use Cases

• ISO contract renewals — bump UTC expiry by one year.
• Global reporting — align fiscal UTC anchors across regions.
• Server-side forms — apply UTC year/month/day from API payloads.
• Historical UTC dates — set years on parsed ISO timestamps.
• Leap-day policies — handle Feb 29 UTC birthdays and anniversaries.
• Clone + mutate — copy before changing UTC year for comparisons.

📝 Notes

• setUTCFullYear() changes the UTC calendar year—not the local one from getFullYear().
• Month index is zero-based: January = 0, December = 11.
• Omitting month/day keeps current UTC month and day unless normalization applies.
• Mutates the original Date—clone with new Date(date) when needed.
• Returns epoch ms, not the Date—no fluent chaining on the return value.
• Verify with getUTCFullYear(), getUTCMonth(), and toISOString().

💡 Best Practices