UTC Time Now
Live Coordinated Universal Time displayed in every common format. Updates every second.
What Is UTC?
UTC (Coordinated Universal Time) is the world's primary time standard. It is maintained by the International Bureau of Weights and Measures (BIPM) using a weighted average of atomic clocks in more than 70 laboratories worldwide. Every other timezone on Earth is defined as a fixed offset from UTC — for example, New York is UTC-5 in winter (EST) and UTC-4 in summer (EDT), while Tokyo is always UTC+9.
Unlike local times, UTC never changes for daylight saving time. It ticks forward at exactly the same rate every second of every day, which is why it is the foundation of global computing infrastructure, aviation, satellite systems, and financial markets.
UTC vs GMT — What's the Difference?
Numerically, UTC and GMT are the same — both show midnight at the same instant. The practical difference is technical: GMT is a historical timezone based on solar observations at the Royal Observatory in Greenwich, London. UTC is a modern atomic time standard that occasionally adds a leap second to stay within 0.9 seconds of solar time.
In casual conversation, "UTC" and "GMT" are used interchangeably. In technical systems, always prefer UTC — it is the authoritative, internationally agreed standard. Many programming libraries treat "GMT" as an alias for UTC, which is functionally correct but imprecise.
Why Store Everything in UTC?
Storing timestamps in UTC is a foundational software engineering best practice. The reasons are practical:
- No DST bugs: Daylight saving transitions create ambiguous local times (the same wall clock hour appears twice during "fall back"). UTC has no such ambiguity.
- Consistent sorting: UTC timestamps sort chronologically. Local times do not, because offsets vary throughout the year.
- Portability: A UTC timestamp means the same thing on a server in Frankfurt, a database in Virginia, and a client device in Tokyo.
- Simple math: Adding and subtracting durations in UTC is exact. Adding hours to a local time can produce incorrect results near DST boundaries.
The correct pattern: store in UTC → convert to local time at the display layer, using the user's timezone preference.
Getting UTC Time in Code
JavaScript: new Date().toISOString() returns the current UTC time as an ISO 8601 string (e.g., 2026-02-25T12:34:56.789Z). For individual components, use getUTCHours(), getUTCMinutes(), etc.
Python: datetime.utcnow() or the timezone-aware datetime.now(timezone.utc) (preferred in modern Python). Format with strftime('%Y-%m-%dT%H:%M:%SZ').
Go: time.Now().UTC() returns the current time in the UTC location.
SQL: NOW() AT TIME ZONE 'UTC' in PostgreSQL, UTC_TIMESTAMP() in MySQL, GETUTCDATE() in SQL Server.
Frequently Asked Questions
What is UTC time?
UTC (Coordinated Universal Time) is the primary world time standard. All other time zones are offsets from UTC. It is maintained by atomic clocks and does not observe daylight saving time — it runs at the same rate every second of every day.
Is UTC the same as GMT?
They show the same time numerically, but GMT is a historical timezone while UTC is a modern atomic time standard. In everyday use they are interchangeable; in technical contexts, UTC is the authoritative reference.
Why do developers use UTC instead of local time?
UTC eliminates bugs from daylight saving time, ensures consistent chronological sorting, and is portable across servers in different regions. Best practice is to store all data in UTC and convert to local time only at the display layer.
How do I get the current UTC time in JavaScript?
new Date().toISOString() returns the current UTC time in ISO 8601 format. Use getUTCHours(), getUTCMinutes(), etc. for individual UTC components.
What is the difference between UTC and my local time?
Your local time equals UTC plus your timezone's current offset. Eastern Standard Time (EST) is UTC-5, so 12:00 UTC = 07:00 EST. The offset changes twice a year in regions that observe daylight saving time.