About UTCTime
A clock built for the person who has to put the time into a program. Every value on this site is one click from your clipboard, every page renders before you can blink, and the JSON API behind it is free and needs no key.
Why it exists
The sites that rank for "utc now" were built around 2010 and never moved. They show you an ISO 8601 timestamp and leave you to select it with a mouse. They have no dark mode, no code snippets, and no API. Meanwhile worldtimeapi.org — the free time API that thousands of ESP32, CircuitPython and reporting projects hard-coded — has spent long stretches unreachable, with no status page and no explanation.
Both gaps have the same shape: the time is trivially computable, so serving it well should be cheap and reliable. This site is what that looks like when someone actually tries.
What is here
- UTC now — a live clock with every common format, a copy button on each, per-language snippets, and a check on whether your own device clock is drifting.
- Zone converters — with the daylight-saving state spelled out, because "EST" in July usually means EDT, and that one-hour lie is the single most common scheduling bug there is.
- Unix timestamps — both directions, with the unit detected from the digit count, and a permanent shareable page for any instant.
- Timezone abbreviations — including the ambiguous ones nobody else disambiguates: IST is India, Ireland and Israel; CST is US Central, China and Cuba.
- A free JSON API — keyless, CORS-open, with published limits and worldtimeapi.org-compatible URL shapes.
How we try not to be wrong
Correctness is the entire value of a time site, so: every offset, every daylight-saving date and every abbreviation on this site is computed at request time from the IANA tz database, never from a stored table or a hard-coded offset. When a government changes its clock rules, the pages change with the next tzdata release rather than quietly serving last year's answer. Nothing is precomputed into text, which is also why an hour permalink like /utc-to-est/14-00 carries the full converter rather than a generated paragraph.
The host is NTP-synchronised, and the homepage tells you how far your own device is off — measured against this server, corrected for half the round-trip. If we are making claims about the correct time, we should be willing to be measured.
What we deliberately do not do
- No accounts. Nothing here needs one, and your preferences live in your own browser.
- No tracking pixels, no third-party fonts, no CDN scripts. Every asset is served from this domain.
- No consumer city pages ("time in London") — that is a different site's job. This one is for developers.
- No AI-written filler. If a page has a FAQ, someone wrote those answers and the numbers in them were computed for that page.
Contact
Bug reports about a wrong offset or a missing zone are the most welcome kind of mail we get — send one. If you are building on the API and expect real volume, say hello first and we will make sure nothing surprises you.