In short: To convert a timestamp to UTC, take away its offset: CST is UTC−6, so add 6 hours. 2026-11-18 04:13:42.130241 CST is 2026-11-18 10:13:42.130241 UTC, written 2026-11-18T10:13:42.130241Z in ISO 8601, and 1794996822.130241 in Unix time.
How to use the timestamp to UTC converter
- Paste the timestamps. One a line, or whole log lines as they came out of the system: the converter finds every timestamp in each line, so there is no need to cut them out first.
- Say where unlabelled times come from. A timestamp that carries its zone (CST, Z, −06:00, America/Chicago) is read with it. One without a zone is read in the zone you choose, with that zone's daylight saving time on that date. The menu starts on your device's time zone, shows each zone's offset from UTC today, and lists every other time zone your browser knows after the common ones.
- Choose what to convert to. UTC by default; choose US Central or any other zone to go the other way, from UTC to CST. Swap zones flips the two menus in one click.
- Check the notes and copy. Each timestamp gets its converted time, ISO 8601 and Unix time, and a note when something about it needs a second look. Copy the converted times, the lines with their timestamps rewritten, or everything as CSV for a spreadsheet.
Nothing you paste leaves your browser, which matters when the log lines carry customer data or internal addresses.
CST to UTC, EST to UTC and the other US time zones
To get UTC from a US time, add the zone's hours behind UTC. CST to UTC is plus 6 hours, so 2026-11-18 04:13:42.130241 CST is 2026-11-18 10:13:42.130241 UTC. EST to UTC is plus 5 and PST to UTC plus 8: 04:13:42 PST is 2026-11-18 12:13:42 UTC. In summer most of the US moves its clocks an hour ahead for daylight saving time, so Central becomes CDT and the gap shrinks to 5 hours. Under 15 U.S.C. 260a, the law that sets daylight saving time, it runs from 2 a.m. on the second Sunday of March to 2 a.m. on the first Sunday of November: in 2026, Mar 8, 2026 to Nov 1, 2026. Arizona rejects daylight saving time by state law and Hawaii does not use it either.
| Zone | Winter | Add for UTC | Summer | Add for UTC |
|---|---|---|---|---|
| US Eastern (New York) | EST, UTC−5 | 5 hours | EDT, UTC−4 | 4 hours |
| US Central (Chicago) | CST, UTC−6 | 6 hours | CDT, UTC−5 | 5 hours |
| US Mountain (Denver) | MST, UTC−7 | 7 hours | MDT, UTC−6 | 6 hours |
| Arizona (Phoenix) | MST, UTC−7 | 7 hours | No change | 7 hours |
| US Pacific (Los Angeles) | PST, UTC−8 | 8 hours | PDT, UTC−7 | 7 hours |
| Alaska (Anchorage) | AKST, UTC−9 | 9 hours | AKDT, UTC−8 | 8 hours |
| Hawaii (Honolulu) | HST, UTC−10 | 10 hours | No change | 10 hours |
For UTC to CST, go the other way and take the hours off: 10:13:42 UTC is 04:13:42 CST in winter and 05:13:42 CDT in summer. The converter does this for any date when you choose US Central under Convert to.
When a stamp says CST in summer
Central clocks show CST only in winter. A log line stamped 2026-07-15 09:30:00 CST therefore means one of two things. Either the clock that wrote it really was on UTC−6, because it ignores daylight saving time or is not a US clock, and the time is 2026-07-15 15:30:00 UTC. Or the label is fixed and the clock was on CDT, and the time is 2026-07-15 14:30:00 UTC, an hour earlier. The converter reads the stamp as written, which is the only reading it can know is literal, and adds a note with the other answer so you can pick the one that fits the system. The same happens with EST in summer (2026-07-15 09:30:00 EST is 2026-07-15 14:30:00 UTC as written) and with CDT or EDT in winter.
CST has a second meaning: China Standard Time, UTC+8. Read that way, 2026-11-18 04:13:42.130241 CST is 2026-11-17 20:13:42.130241 UTC, 14 hours earlier than the US reading. When the logs come from a server in China, press Use China Standard Time on a CST stamp's line, and every CST stamp is read that way. Other abbreviations are read the way a US reader expects: AST is Atlantic Standard Time, IST is India Standard Time and BST is British Summer Time.
Times that happened twice, or never
When clocks go back in November, an hour repeats. In US Central on Nov 1, 2026, 1:30 a.m. happened once in CDT and again an hour later in CST, so a log time of 2026-11-01 01:30:00 with no zone is ambiguous: it is 2026-11-01 06:30:00 UTC or 2026-11-01 07:30:00 UTC. The converter reads it as the first and shows the second in a note. When clocks go forward in March, an hour is skipped: 2:30 a.m. never happened in US Central on Mar 8, 2026. A stamp of 2026-03-08 02:30:00 is read as 2026-03-08 03:30:00 CDT, which is 2026-03-08 08:30:00 UTC, and flagged, because it usually means the clock or the log is wrong.
A timestamp that carries its offset, such as 2026-11-01T01:30:00-05:00, is never ambiguous, which is why RFC 3339, the internet timestamp standard, always writes one: the letter Z for UTC, or a numeric offset.
Log timestamp formats it reads
Each line is searched for timestamps, so the text around them can be anything. The converter reads:
- ISO 8601 and SQL:
2026-11-18T10:13:42.130241Z,2026-11-18 04:13:42-06(PostgreSQL),2026-11-18 04:13:42,130(with a comma before the milliseconds, as some Java loggers write it). ISO 8601 allows a comma before any fraction; the converter reads one when three, six or nine digits follow it (milliseconds, microseconds or nanoseconds, as Java loggers can write them), or when a zone comes right after it or after one space (Z, an offset with its minutes such as −06:00, an abbreviation or a zone name:10:13:42,130241Z), and otherwise takes the comma as a separator, as between the fields of a CSV line. - US dates with AM or PM:
11/18/2026 4:13:42 AM. A date that works both ways, like03/04/2026, is read month first and gets a Read day first button on its line; a date that only works one way, like18/11/2026, is read that way and noted. - Month names:
Nov 18, 2026 4:13 PM EST,18 Nov 2026 10:13:42 +0000(email headers),18-Nov-2026 04:13:42, and JavaScript'sWed Nov 18 2026 04:13:42 GMT-0600. - Server logs: the Unix date command's
Wed Nov 18 04:13:42 CST 2026, Apache and nginx access logs'18/Nov/2026:04:13:42 -0600, and syslog'sNov 18 04:13:42, which has no year, so the current year is used and noted. - Zones written as abbreviations (CST, CDT, EST, PST, GMT, CET, JST and more), offsets (Z, −06:00, −0600, UTC−6, GMT+5:30) or zone names from the tz database (America/Chicago).
- Unix time in seconds, milliseconds, microseconds or nanoseconds, on a line of its own or after a key that names it, as in
"ts": 1794996822.130241.
A weekday that does not match the date (Thu with a date that falls on a Wednesday) gets a note, since one of the two must be wrong.
Unix time, ISO 8601 and milliseconds
Unix time counts seconds from the start of 1970 in UTC, which makes it the same number everywhere in the world. It ignores leap seconds, as the POSIX standard defines it:
As represented in seconds since the Epoch, each and every day shall be accounted for by exactly 86400 seconds.
Many systems count in milliseconds instead, which adds three digits: 1794996822130 is the same moment as 1794996822.130 seconds. The converter gives Unix time in seconds in its table and in milliseconds in the CSV, keeping the fraction you pasted digit for digit, up to nine digits. ISO 8601 output uses the RFC 3339 form: a T between date and time and Z for UTC, or the offset when you convert to another zone. Daylight saving rules come from the tz database (IANA Time Zone Database) that your browser ships with, so a date years back is converted with the rules in force then.
For a time difference between cities rather than a single timestamp, the time zone meeting planner shows the working hours two to four cities share, and the military time converter turns 24-hour times into 12-hour ones.
Este convertidor también está en español: convertir hora a UTC, con las mismas zonas y avisos.
Questions people ask
Is UTC 5 or 6 hours ahead of CST?
6 hours. CST, US Central Standard Time, is UTC−6, so 04:13 CST is 10:13 UTC. During daylight saving time Central clocks show CDT, which is UTC−5, and UTC is 5 hours ahead; in 2026 that runs from Mar 8, 2026 to Nov 1, 2026. A stamp that says CST is read as UTC−6 whatever the date, and the converter adds a note when Central clocks were on CDT that day.
Is UTC−6 the same as CST?
For a single time, yes: CST means UTC−6. But US Central Time is not UTC−6 all year, because it moves to CDT, UTC−5, for daylight saving time. Mexico City stays on UTC−6 all year in 2026, so in summer a time at UTC−6 can be Mexico City's clock while Chicago's is at UTC−5. To convert a time with no label, choose the zone the clock is in, and the converter works out the offset for that date.
How do I convert a Unix timestamp to UTC?
Paste it. The converter tells the unit from the number of digits: 10 digits are seconds, 13 milliseconds, 16 microseconds and 19 nanoseconds. 1794996822130 has 13 digits, so it is milliseconds: 2026-11-18 10:13:42.130 UTC. Unix time is always counted from 1970-01-01 00:00:00 UTC, so the zone menus do not change how it is read, only how it is shown.
Does it keep microseconds and nanoseconds?
Yes. The digits after the seconds are carried through as written, up to nine of them, so 2026-11-18 04:13:42.130241 CST becomes 2026-11-18 10:13:42.130241 UTC, 2026-11-18T10:13:42.130241Z in ISO 8601 and 1794996822.130241 in Unix seconds. Time zones only ever shift whole minutes, so the fraction never changes.
How do I convert UTC to CST?
Choose US Central under Convert to and paste the UTC time. 2026-11-18 10:13:42.130241 UTC becomes 2026-11-18 04:13:42.130241 CST, and the ISO 8601 column gives 2026-11-18T04:13:42.130241-06:00. In summer the same choice gives CDT, because the converter uses Central's real offset on each date. US Eastern gives 2026-11-18 05:13:42.130241 EST.
What happens to a timestamp with no time zone?
It is read in the zone you choose under Timestamps with no time zone are in, with that zone's daylight saving rules for its date. That menu starts on your device's own time zone, so check it when the logs come from a server somewhere else. If the time happened twice that day, because the clocks went back, it is read as the first and the note gives the second. If it never happened, because the clocks jumped forward, the note says so and gives the time it was read as.
Is anything I paste sent anywhere?
No. The converter runs in your browser, so log lines never leave your computer. Copy share link puts your settings, and the text if it is short, in the part of the address after the #, which browsers never send to a server.