What is 24-hour time?

What does a 24-hour clock time look like?

A 24-hour clock time is two digits for the hour, then a colon, then two digits for the minute, optionally followed by a colon and two digits for the second: 00:00 at the moment a calendar day begins, 09:00 nine hours into it, 14:30 at half past two in the afternoon, 23:59 a minute before the day ends.¹ The hour runs from 00 to 23 and the minute from 00 to 59. There is no AM, PM, "in the morning", or "at night" suffix; the hour itself disambiguates which half of the day the moment falls in.²

The international standard that pins this convention down — ISO 8601, the standard for date and time strings — was first published in 1988 and is now in its 2019 edition.¹ The standard's grammar uses 24-hour notation throughout: a wall-clock time is hour-then-minute-then-second from largest unit to smallest, with hours two digits in the range 00 to 24 and a fixed colon separator in the format used by humans. The compact form without separators — 1430 instead of 14:30 — is also defined and used in narrow technical contexts, but the colon-separated form is what every web specification, database, and operating system uses by default.¹³

The defining property of the format is that there is no shared name between two different times of day. In the 12-hour clock, "9:00" can mean either of the two times nine hours after midnight or nine hours after noon, and a reader has to either know which from context or trust a separate AM/PM marker that is occasionally missing or wrong.² In the 24-hour clock, every minute of the day has exactly one written form, and that form sorts naturally — 09:00 is alphabetically and numerically before 21:00, which is exactly the order they occur in. This is the same property that makes ISO 8601 dates sort chronologically by string comparison.

Where is 24-hour time the everyday civil convention?

Most of the world. Continental Europe, most of Latin America, most of Africa, most of Asia, and most former British and French colonies use the 24-hour clock as the default in transport timetables, broadcast schedules, written communication, and increasingly in spoken communication.⁵ The international standard, the major internet protocols, and almost every digital interface that has to be intelligible across borders default to the same convention.¹³

The exceptions cluster in the English-speaking world. The United States is the largest of them: the 12-hour clock with AM and PM is the everyday convention, and the major US style guides — the AP Stylebook for journalism, the Government Publishing Office Style Manual for federal documents — assume 12-hour notation as the default for civil writing.⁶² The 24-hour clock appears only in technical contexts: military operations, aviation, hospitals, scientific writing, and computer interfaces.

The same pattern holds, in softer form, in Britain, Ireland, Canada, Australia, and New Zealand. The 12-hour clock is the everyday norm in conversation and in informal writing, but the 24-hour clock is the default in transport timetables (where ambiguity over the half of the day matters), in technical documentation, and in government data. The UK Government's open-standards guidance, for example, explicitly mandates 24-hour notation with a colon separator for date-and-time fields in public-sector data, even though the same government's press releases use 12-hour times.⁵

The everyday/technical split is therefore not a sharp line: the same speaker may say "let's meet at half past two" in the office and write 14:30 in a calendar invite. What differs between countries is which side of that split the everyday convention sits on.

Why do aviation, the military, and hospitals use 24-hour time?

To eliminate the half-day ambiguity built into the 12-hour clock. The cost of that ambiguity is small in everyday life — missed dinner reservations, a late meeting — and large in the operational settings where a misread time can cost lives or aircraft. Each of these settings adopted the 24-hour clock for the same reason, and none has reverted.

Aviation. The U.S. operational rules for air-traffic control require the 24-hour clock for time-of-day expressions, with the hour given by the first two figures and the minute by the last two: "A reference may be made to local daylight or standard time utilizing the 24-hour clock system. The hour is indicated by the first two figures and the minutes by the last two figures."⁴ Time is normally given in Coordinated Universal Time — known by aviation tradition as Zulu time, after the radio-alphabet word for the letter Z that ends a UTC-tagged timestamp — so that pilots and controllers crossing time zones share a single clock with no zone arithmetic.⁴ The same conventions are used by every other major civil-aviation regulator and by the International Civil Aviation Organization's standards for air-ground communication.

The military. The 24-hour clock has been the default in military communications for the same reason and longer. Times appear in messages, orders, and schedules as four-digit numbers — 0600, 1430, 2200 — followed by a single-letter time-zone designator: Z for UTC, L for the local zone, or one of the letters A through Y for a specific zone offset. The full timestamp form most often seen, the date-time group, packages the day-of-month, the four-digit time, the zone letter, the three-letter month, and the two-digit year into a single token like 091430Z MAY 26.

Hospitals and emergency services. Medical safety bodies have argued for 24-hour notation in medication-administration records and clinical communication for decades on the grounds that the AM/PM convention has been a recurring source of medication-time errors — drugs given twelve hours late, or twelve hours early, when the AM/PM marker on a written order was misread or missing. The U.S. National Institute of Standards and Technology gives the same rationale in plainer terms: "12 a.m. and 12 p.m. are ambiguous and should not be used", with the recommended alternatives being either to write out "noon" and "midnight" or to switch to 24-hour notation, where there is no 12:00 AM or 12:00 PM at all.² Many hospitals adopt 24-hour notation across the board for that reason; emergency services, dispatch, and hospital pharmacy systems do the same.

What is "military time" and how does it differ from 24-hour time?

"Military time" is colloquial English for the 24-hour convention as it appears in U.S. military and aviation use: hours from 00 to 23, written as four digits with no colon between hour and minute. Half past two in the afternoon is 1430; ten in the morning is 1000; half past midnight is 0030. The day begins at 0000 and ends at 2359.⁴ Pronounced aloud, the digits are spoken individually — 0920 is "zero niner two zero", not "nine twenty" — to avoid mishearings on radio.⁴ A round hour with no minute component is sometimes pronounced "fourteen hundred" rather than "fourteen zero zero".

The convention is identical to 24-hour civil time on the underlying clock. Every 1430 in a military schedule is the same instant as every 14:30 in a European train timetable; the only difference is the absence of the colon and a small set of pronunciation rules. The two are sometimes treated as separate things in style guides — the Chicago Manual of Style, for example, explicitly distinguishes the four-digit no-colon form ("twenty-four-hour system") from the colon-separated form — but that distinction is typographic, not temporal.

Outside U.S. military and aviation contexts, "military time" is rarely the term of art. The European, Asian, and Latin American civil-time convention is just "the 24-hour clock", and almost universally written with the colon. Calling a French train timetable "military time" would surprise the French.

How does 24-hour time handle midnight and noon?

Noon is unambiguous in 24-hour notation: 12:00. There is no AM/PM choice to get wrong, and no special rule needed. Midnight, on the other hand, is the only edge case in the format — and the only one that has caused enough trouble in practice to be repeatedly clarified by the standards.

The international standard permits two notations for midnight, with subtly different meanings.¹⁷ 00:00 on a given calendar date is the moment that date begins. 24:00 on the previous calendar date is the same instant on the time line, written from the point of view of the day that is ending. The 2019 edition of ISO 8601 had quietly removed the 24:00 form; a 2022 amendment to that edition reinstated it, on the grounds that some industries — transport schedules, broadcasting, contracts that run until end-of-day — genuinely need the "end of day" form because 00:00 of the following day fails to express the intent.⁷ The standard now defines both, with 00:00 recommended where a single representation is required.¹⁷

The U.S. National Institute of Standards and Technology gives the same guidance for civil writing in plainer language: midnight can be written 0000 at the beginning of a date or 2400 at the end of the previous date, but the meaning depends on the context, so contracts and operational documents should pick one convention and state it.² The same body recommends against writing midnight as 12:00 AM at all, on the grounds that the AM/PM convention is genuinely ambiguous at the boundary — 12:00 AM has been read as both midnight and noon by careful readers — and the unambiguous alternatives ("midnight", "noon", or 24-hour notation) are always available.²

The internet profile of ISO 8601 — RFC 3339 — sidesteps the choice by forbidding the 24:00 form entirely. Its grammar restricts the hour field to the range 00 through 23, with the explicit rationale that "this profile of ISO 8601 only allows values between '00' and '23' for the hour in order to reduce confusion."³ An end-of-day midnight in an RFC-3339 timestamp is therefore always written as 00:00:00 on the following day. Most software that handles internet timestamps follows the RFC's restriction even when the surrounding standard is described as ISO 8601, because mixed parsers cannot agree on the meaning of 24:00.³

How do you convert between 12-hour and 24-hour time?

The conversion is mechanical. There are six cases, distinguished by the hour:

• 12:00 AM (midnight) → 00:00. The 12-hour clock numbers midnight as the twelfth hour of the previous half-day; the 24-hour clock numbers it as the zeroth hour of the new half-day.
• 1:00 AM through 11:59 AM → 01:00 through 11:59. The hour is the same; only the AM marker is dropped.
• 12:00 PM (noon) → 12:00. The two clocks agree at noon.
• 12:01 PM through 12:59 PM → 12:01 through 12:59. The hour stays at 12; only the PM marker is dropped.
• 1:00 PM through 11:59 PM → 13:00 through 23:59. Add 12 to the hour and drop the PM marker.
• Going the other way, hours 00:00 through 11:59 become AM (with 00 rewritten as 12), and hours 12:00 through 23:59 become PM (with hours 13 to 23 reduced by 12).

The only routinely-mishandled cases are the two flips at midnight and noon. 12:30 AM is half past midnight, which is the early hours of the day, so it converts to 00:30 — not 12:30. 12:30 PM is half past noon, so it converts to 12:30 — the same number — not 00:30. Software that mishandles AM/PM nearly always mishandles one or both of these. The corresponding conversion tool on this site includes a full reference chart for all 24 hours so neither case has to be reasoned out from scratch.

Where else does 24-hour notation appear on the internet?

Almost everywhere. Wherever a timestamp is written for a machine to parse, the 24-hour form is the default — usually as part of an ISO 8601 or RFC 3339 timestamp, with the hour written as two digits in the range 00–23.¹³ HTTP date headers in their modern form, JSON Schema's format: "date-time", OAuth 2.0 token expiries, structured logs, database TIMESTAMP columns, and the HTML <time datetime="…"> attribute all consume 24-hour notation as a strict subset of their accepted input. The 12-hour clock has no representation in the data layer of the modern web at all; it is exclusively a presentation-layer convention, applied at render time by software that knows the reader's locale.

The same convention extends to time-zone offsets, which use the 24-hour convention for the offset hour: +10:00 means ten hours ahead of UTC, -08:00 means eight hours behind. There is no AM/PM ambiguity to introduce in offsets — they are signed differences, not times of day — but the format-wide commitment to 00–23 hours is what allows a single regular-expression-shaped grammar to validate the whole timestamp.³

Frequently asked questions