The same moment shows up in two costumes. A train board says 18:30. An email says "call at 6:30 PM." A hospital wristband says 0800. A support ticket timestamp is 13:05 in 24-hour style and the U.S. teammate reads it as 1:05 AM by reflex. The form above takes one time entry and prints the format you chose; the detail line underneath keeps both versions visible so you can copy the one your audience expects.
The time field is always 24-hour internally—that is how browsers handle time inputs. Pick "12-hour format" in the output dropdown when you need AM/PM prose. Pick "24-hour format" when you need zero-padded hours for a roster or API field. You are not calculating a duration or sliding a clock forward; add-time and time-span pages do that work.
Afternoon commutes are the everyday check. 18:30 as 12-hour time should read 6:30 PM, the sort of conversion people still second-guess after lunch. Midday labels are where AM/PM bites: 13:05 in 12-hour wording is 1:05 PM, not 1:05 in the morning.
Midnight and noon are not interchangeable
Twelve-hour clocks use 12 as a pivot, not zero. 00:30 shown as 12-hour lands on 12:30 AM—thirty minutes after midnight, easy to mis-say as "half past twelve" without the AM. Noon and midnight are the usual trip points; running the edge once beats arguing from memory in a thread.
When you need how long a span is—not how to write it—switch tools. 10:00 PM to 6:30 AM with end on the next day is an overnight length question on the time difference page. Stacking hours onto a start clock is still the add-time habit, not a format swap.
Before you paste into a form field
Copy the line that matches the destination system. Some portals want 24-hour with a colon; others want AM/PM in prose. The detail under the result shows both so you do not email the wrong one. If the source material mixes date and time, normalize the calendar piece separately—the May 9, 2026 in ISO date form page is the sibling for dates, not hours.
- Output dropdown chooses display; input stays 24-hour under the hood.
- Seconds are not on this form—rough schedules only.
- Timezone offsets are out of scope; this is label conversion on one clock.
Audit and log threads often pair friendly "2 days ago" labels with precise timestamps; the audit trail time note is useful when display copy has to match exported values.
Ordinary reference formatting, not legal or scheduling advice. When the wording matters, keep both styles beside the value you paste.