JavaScript Date setSeconds() Method

What You’ll Learn

setSeconds() writes the second (0–59) on a Date in local time, with an optional milliseconds argument. This guide covers syntax, minute-boundary snaps, overflow, and comparisons with UTC setters.

Introduction

Timestamps from logs, APIs, and cron jobs often need their second component adjusted. After reading seconds with getSeconds(), setSeconds() 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 setSeconds() Method

Date.prototype.setSeconds(second [, millisecond]) accepts a local second and an optional millisecond (0–999). When you pass only the second, minutes and hours stay the same unless overflow normalization rolls the clock forward.

Values outside normal ranges normalize— setSeconds(90) becomes 1 minute and 30 seconds later. For UTC second writes, use setUTCSeconds().

📝 Syntax

dateObj.setSeconds(second)
dateObj.setSeconds(second, millisecond)

Parameters

• second — Integer 0–59 in local time (overflow normalizes).
• 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, 5);
date.setSeconds(30);

console.log(date.getMinutes());  // 15
console.log(date.getSeconds());  // 30

15
30

const date = new Date(2026, 2, 1, 12, 15, 42, 750);
date.setSeconds(0, 0);

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

15
0
0

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

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

45
500

const original = new Date(2026, 2, 1, 12, 15, 10);
const adjusted = new Date(original);
adjusted.setSeconds(55);

console.log("Original s:", original.getSeconds());  // 10
console.log("Adjusted s:", adjusted.getSeconds());  // 55

Original s: 10
Adjusted s: 55

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

console.log(date.getMinutes());  // 31
console.log(date.getSeconds());  // 30

31
30

🚀 Common Use Cases

• Log alignment — setSeconds(0, 0) for minute buckets.
• API timestamps — apply second/ms from parsed ISO strings.
• Test fixtures — pin exact second/ms in unit tests.
• Cron alignment — snap events to :00 at minute boundaries.
• Form time pickers — apply user-selected seconds to a Date.
• Clone + mutate — keep originals when tweaking sub-minute fields.

📝 Notes

• setSeconds() uses local time seconds 0–59 (overflow normalizes).
• For elapsed duration, use end.getTime() - start.getTime()—not clock getters.
• 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 millisecond defaults to 0 when omitted in two-arg calls.
• Use setUTCSeconds when rules follow UTC, not local wall clock.

💡 Best Practices