JavaScript Date toUTCString() Method

What You’ll Learn

toUTCString() formats a Date as a readable UTC string in RFC 1123 style—weekday, day, month, year, time, and GMT. It is useful for HTTP headers and logs; for JSON APIs, prefer toISOString().

Introduction

When you need a human-readable timestamp in Coordinated Universal Time, toUTCString() converts any valid Date instant into a standardized GMT string. Unlike toString(), which uses local time, this method always expresses the instant in UTC.

For machine-readable JSON and databases, use toISOString() instead. For locale-aware display, use toLocaleString(). toUTCString() shines in HTTP Date headers and server logs where RFC 1123 text is expected.

Understanding the toUTCString() Method

Date.prototype.toUTCString() returns a string like:

• ddd, dd mmm yyyy HH:MM:SS GMT
• Example: Sun, 15 Mar 2026 09:00:00 GMT
• ddd — abbreviated weekday (Sun, Mon, …)
• mmm — abbreviated English month (Jan, Feb, …)
• Clock fields use 24-hour UTC time with zero-padded seconds.

📝 Syntax

dateObj.toUTCString()

Parameters

• None.

Return value

• An RFC 1123 UTC string with a trailing GMT suffix.
• "Invalid Date" if the Date is invalid.

Examples Gallery

Open DevTools Console (F12) or use Try-it links. Examples use Date.UTC() so UTC output is predictable.

const date = new Date(Date.UTC(2026, 2, 15, 9, 0, 0));
const utcText = date.toUTCString();

console.log(utcText);
// "Sun, 15 Mar 2026 09:00:00 GMT"

Sun, 15 Mar 2026 09:00:00 GMT

const date = new Date(Date.UTC(2026, 2, 15, 9, 0, 0));

console.log(date.toUTCString());  // RFC 1123 UTC
console.log(date.toISOString());  // ISO 8601 UTC
console.log(date.toString());     // local default

Sun, 15 Mar 2026 09:00:00 GMT
2026-03-15T09:00:00.000Z
Sun Mar 15 2026 14:30:00 GMT+0530 (India Standard Time)

// Local: Mar 16 2026 01:00 (example in UTC+5:30)
const lateLocal = new Date(2026, 2, 16, 1, 0, 0);

console.log(lateLocal.toString());
console.log(lateLocal.toUTCString());

Mon Mar 16 2026 01:00:00 GMT+0530 (India Standard Time)
Sun, 15 Mar 2026 19:30:00 GMT

const now = new Date(Date.UTC(2026, 2, 15, 9, 0, 0));
const httpDate = now.toUTCString();

const headerLine = `Date: ${httpDate}`;
console.log(headerLine);
// Date: Sun, 15 Mar 2026 09:00:00 GMT

Date: Sun, 15 Mar 2026 09:00:00 GMT

const bad = new Date('not-a-date');

console.log(bad.toUTCString()); // "Invalid Date"

if (Number.isNaN(bad.getTime())) {
  console.log('Cannot format UTC string');
}

Invalid Date
Cannot format UTC string

🚀 Common Use Cases

• HTTP response headers — Date, Last-Modified, Expires.
• Server logs — human-readable UTC timestamps in text logs.
• Email date headers — RFC 1123-style message timestamps.
• Debugging UTC view — compare against local toString() output.
• Legacy integrations — systems expecting GMT text instead of ISO.
• Teaching — show how UTC differs from local string formatters.

📝 Notes

• Always UTC with a GMT suffix—never local offset text.
• Read-only: does not mutate the Date.
• RFC 1123 format differs from ISO 8601—do not confuse the two in APIs.
• toGMTString() is deprecated but returns the same string.
• Invalid dates return "Invalid Date"—unlike toISOString() which throws.
• For JSON payloads, prefer toISOString() over toUTCString().

💡 Best Practices