Military Time Converter

How to use the military time converter

Enter the time in the single field. A time is one instant, so there is no direction to choose: the card returns the military four-digit form, the civil colon form, the 12-hour form and a spoken reading together. The browser time control decides whether you type AM and PM or a plain 24-hour hour.

The minute never changes during this conversion. In 10:45 PM, the final 45 remains 45 while the hour becomes 22, producing 2245 in military writing and 22:45 in civil 24-hour writing. In the reverse direction, 2245 becomes 10:45 PM because an hour above 12 loses 12 and takes the PM label.

The familiar shortcut covers 22 of the 24 whole hours, which is why it feels dependable until noon or midnight appears. Adding 12 works for 1 PM through 11 PM, while leaving the hour alone works for 1 AM through 11 AM. Hour 12 is the exception on both halves of the day.

Military writing uses four digits without a colon. The leading zero is part of that form, so nine in the morning is 0900 rather than 900. The colon belongs to the extended civil 24-hour form, where the same moment is 09:00. Both are clear, but they are different notations and should not be mixed.

The spoken line needs a service label rather than a universal claim. This converter follows the engine’s Army and Marine-style reading, including “hours,” so 0900 appears as “zero nine hundred hours.” The Navy’s current NJROTC manual says Navy parlance omits that final word. Local units and operational procedures remain the authority for speech.

1. 1

   Before 10 in the morning

   Keep both hour positions. The engine writes 9:00 AM as 0900 and reads the leading zero aloud.

2. 2

   From 1 PM through 11 PM

   Add 12 to the displayed hour while leaving the minutes untouched, so 10:00 PM becomes 2200.

3. 3

   At hour 12

   Use the named exception: 12 AM maps to 0000 and 12 PM maps to 1200.

Why midnight needs a date beside it

Midnight is one instant with two useful boundary descriptions. NIST describes 0000 as midnight at the beginning of a stated day and 2400 as the end of a stated day. The digits alone are therefore incomplete around midnight: a date tells the reader which day is opening or which one has just closed.

For example, 0000 on Tuesday starts Tuesday, while 2400 on Monday names the same boundary from Monday’s closing side. Writing only 2400 without a date leaves the intended day uncertain. The converter returns 0000 for 12:00 AM because its input describes the start of the selected day rather than the end of a preceding date.

The current ISO 8601 edition has a related history. ISO 8601-1:2019 originally excluded hour 24, then Amendment 1 in 2022 reintroduced the end-of-day representation. That does not make 2400 interchangeable with an undated 0000 in every document; it gives information systems a defined way to name the closing boundary of a calendar day.

NIST also advises against 12 a.m. and 12 p.m. when clarity matters, because noon is neither before nor after the meridian and midnight raises the additional question of which date owns it. “Noon,” “midnight,” 0000 with a date, or 2400 with the preceding date says more than either ambiguous abbreviation.

A suffix identifies a zone but does not convert it

A military time can carry a letter after the four digits. Z is Zulu and identifies Coordinated Universal Time, so 0935Z is a time stated on the UTC basis. J, spoken Juliett, indicates the observer’s local time rather than a fixed offset. Its clock reading depends on where that observer is located.

L is Lima, a fixed military zone designator associated with UTC plus 11 hours; it is not a generic abbreviation for local time. Treating every trailing L as “local” can change the intended instant by many hours. When local time is meant, the applicable service publication or message format should say how it is marked.

That boundary matters whenever a time is coordinated across locations. Converting 1530 to 3:30 PM answers a notation question only. Converting 1530Z to an observer’s local clock requires a date, a destination zone, and the offset in force on that date. Those inputs belong in a time-zone converter, not in this one.

The formula, worked line by line

A 12-hour clock repeats the numbers 1 through 12 twice, while military time numbers the day from hour 00 through hour 23. Conversion therefore changes only the hour field. Minutes pass through unchanged, and the AM or PM marker is replaced by the hour’s position in the full day.

For AM, hours 1 through 11 stay numerically the same and receive a leading zero when needed. The special case is 12 AM, which becomes hour 00. For PM, hours 1 through 11 gain 12. The special case is 12 PM, which stays hour 12 rather than becoming 24.

In the reverse direction, hour 00 becomes 12 AM, hours 01 through 11 take AM, hour 12 becomes 12 PM, and hours 13 through 23 lose 12 and take PM. That four-branch rule avoids every noon and midnight error without relying on what the words AM and PM seem to suggest.

12 AM -> hour 00; 12 PM -> hour 12
1 AM through 11 AM -> keep the hour and pad to two digits
1 PM through 11 PM -> hour + 12
military form = two-digit hour + two-digit minute
civil 24-hour form = two-digit hour : two-digit minute

Noon demonstrates why the condition must be narrower than “add 12 for PM.” The engine maps 12:00 PM directly to hour 12 and produces 1200. Adding 12 would produce hour 24, which belongs only to an end-of-day boundary notation and is not the ordinary representation of noon.

Midnight demonstrates the matching AM exception. The engine maps 12:00 AM to hour 00 and produces 0000, with 2400 exposed only as the alternative end-of-day boundary. Keeping 12 unchanged would mislabel midnight as noon, an error of half a day rather than a small formatting difference.

Questions people ask