How this instrument works
The 24-hour clock, called military time in the US and used as the default civil clock across most of the rest of the world, labels each moment from 00 at midnight through 23 at eleven at night, with no AM or PM marker needed since every point in the day has its own unique number. Converting from the familiar 12-hour clock means combining the 1-through-12 reading with whether it's AM or PM into a single 0-through-23 value — a step that looks like simple addition but has two exceptions that trip up a naive rule.
The common shortcut of 'add 12 for PM, leave AM alone' works for every case except 12 itself. 12 AM, meaning midnight, is not 12 in 24-hour time at all — it's 00, the very start of the day — while 12 PM, meaning noon, stays exactly 12 rather than becoming 24, which doesn't exist as a valid label. Both mistakes are common because '12' looks like it should map straight across, when in fact noon and midnight are the two moments where the 12-hour clock's own labelling is arguably backwards: 12 AM comes right before 1 AM, not after 11 PM, even though its number suggests otherwise.
This conversion matters wherever a schedule or timestamp has to move between the two notations, which is more often than the two systems' relative obscurity to each other suggests: international flight itineraries, hospital charting, computer logs, transportation timetables, and military and emergency-services communication all default to the 24-hour clock specifically because it removes the AM/PM ambiguity that has caused real missed appointments and miscommunicated deadlines.
- Set the Hour (1-12) field to the hour shown on a 12-hour clock, from 1 to 12.
- Set the Minute field to the minutes past that hour, from 0 to 59.
- Choose AM or PM in the segmented control to match the time of day.
- Read the 24-hour clock hour field for the converted hour, from 0 (midnight) to 23 (eleven at night).
- Combine the 24-hour result with your original Minute value to write the full military time, such as 15:45.
Worked example — 3:45 PM to 24-hour time
A US-issued boarding pass lists a departure time of 3:45 PM, and the connecting European itinerary needs it written in 24-hour time. Setting Hour (1-12) to 3, Minute to 45, and PM to on, the calculator checks whether the reading is 12: it isn't, so the PM branch adds 12, giving hour24 = 3 + 12 = 15.
Combined with the unchanged minute, the departure reads 15:45 in 24-hour notation — written on the European ticket simply as 15:45, with no AM/PM marker needed since 15 is unambiguous. If the original time had instead been 12:45 PM (just after noon), the same plus-12 rule would wrongly give 24:45; the noon exception catches this and correctly keeps it at 12, giving 12:45.
Questions
Why doesn't 12 AM just become 12 in 24-hour time?
Because 12 AM means midnight, the very first moment of the day, and the 24-hour clock labels that instant 00, not 12 or 24. The '12' in '12 AM' is a quirk of the 12-hour clock's own labelling, not a hint about the 24-hour equivalent — midnight is 00, and the next tick of the clock, 1 AM, becomes 01, continuing normally from there.
Why does 12 PM stay as 12 instead of becoming 24?
Because noon is already the twelfth unit of the day counting from midnight, and 24-hour time never uses 24 as a label — the day runs from 00 through 23, then rolls over to 00 again for the next day. Adding 12 to noon's '12' would give 24, which isn't a valid 24-hour clock reading, so noon is the one PM case where the usual plus-12 shortcut has to be skipped.
Is there a single rule that avoids checking for AM and PM separately?
Yes, though it requires a small trick: take the raw 1-to-12 value modulo 12 (which turns 12 into 0 and leaves 1 through 11 unchanged), then add 12 only if the time is PM. That correctly handles all four cases — 12 AM becomes 0 mod 12 = 0, plus nothing since it's AM; 12 PM becomes 0 mod 12 = 0, plus 12 since it's PM, giving 12 — without an explicit if-12 check, though most people find the direct noon/midnight rule easier to remember.
Why is 24-hour time called 'military time' in the US specifically?
Because the US armed forces standardized on the 24-hour clock for operational communication, where an unambiguous single number per moment matters more than familiarity, while most everyday US civilian life still runs on the 12-hour AM/PM clock. Outside the US, the 24-hour clock is simply the default civil clock on schedules, transit timetables and official documents, with no particular military association attached to the name.
How is the minute handled in this conversion?
It isn't changed at all — only the 1-to-12 reading needs converting between the two clock systems, since minutes count the same way (0 to 59) in both. A time like 3:45 PM keeps its 45 minutes exactly, becoming 15:45; only the leading figure, 3 with a PM flag, becomes the single 24-hour value 15.
Do 12-hour and 24-hour clocks ever disagree on when a new day starts?
No, both agree that a new day begins at midnight — 12 AM and 00:00 refer to the identical instant. What differs is only the label: the 12-hour clock calls that moment '12', which reads confusingly like the end of a cycle, while the 24-hour clock calls it '00', which reads unambiguously as the start of one.