Semaphore or Signal Flags? Choosing Between Two Maritime Systems

Semaphore and the International Code of Signals both use flags, both predate reliable maritime radio, and a ship's crew historically trained in both rather than choosing one over the other. They are not competing solutions to the same problem — they solve two genuinely different problems, and the difference becomes concrete the moment you compare how each one would actually send the same message.

Two different mechanisms

Our guide to flag semaphore and our guide to the International Code of Signals each cover their own system in full; the short version, side by side: semaphore encodes a letter as a live, held position of two hand flags, one letter at a time, read continuously as a signaller moves through a message. The International Code of Signals encodes a letter (or, more often, a whole pre-agreed message) as a specific flag or combination of flags hoisted on a halyard and left flying, visible to anyone in sight for as long as the message needs to stand. One needs a person actively signalling for the message's entire duration; the other needs a person only for the moment of hoisting it.

Worked example: spelling “SOS” in semaphore

Running “SOS” through our own Semaphore Flag Translator produces three held positions in sequence: S is left arm at the low diagonal, right arm out to the side; O is left arm swung across to the high diagonal, right arm out; then S again, back to the first position. A signaller has to hold each position long enough to be read clearly, then move cleanly to the next — three distinct, sequential positions, requiring a person actively signalling for as long as the message needs repeating.

The same idea, sent the ICS way

The International Code of Signals could spell the same three letters by hoisting the S, O, and S letter flags together on one halyard — but in practice, a real emergency doesn’t reach for the spelled-out version at all, because the code already has a dedicated, pre-agreed signal for exactly this situation. Hoisting the two-flag combination November Charlie is the code's actual general distress signal, meaning “I am in distress and require immediate assistance” — a complete emergency message compressed into two flags, raised once, and left flying for anyone in sight to see, with no live signaller required to hold or repeat anything.

What the comparison actually shows

Line the two up and the design difference is exactly what each system optimises for. Semaphore is built for open-ended, live, two-way exchange: it can spell literally anything, letter by letter, at the cost of needing an active signaller for the full duration and a reader watching in real time. The International Code of Signals is built for broadcasting a small, urgent set of pre-agreed situations as efficiently as possible: a two-flag hoist says more, faster, and keeps saying it hands-free once it's raised, but only for the specific situations the code book has already anticipated and assigned a group to. Spelling out an unanticipated message letter by letter is something the code’s full alphabet can technically still do, but it is the fallback, not the design centre — exactly reversed from semaphore, where spelling things out letter by letter is the whole system.

A second worked example, for a longer message

Running “HELP” through the same Semaphore Flag Translator shows how the system scales with message length: H is left arm across to the low diagonal, right arm out; E is left arm high, right arm down; L is left arm high, right arm low; P is left arm up, right arm out. Four letters means four held positions, each one taking roughly as long to signal and read as the last — the time cost scales directly with how much needs saying, letter by letter, with no shortcut for a longer word. A hoisted code-flag signal has the opposite property: whether the underlying message is one word or a full sentence’s worth of meaning, a pre-agreed code group condenses it to the same one or two flags, provided a group for that specific meaning already exists in the published code.

The catch: a code group needs a shared code book

That compression comes with a real dependency semaphore doesn’t share. A single letter flag’s stand-alone meaning (Oscar for man overboard, Whiskey for medical assistance) is common knowledge across any trained crew, requiring no reference material to send or read. A longer, multi-flag code group representing a specific prearranged situation, by contrast, only means anything if both the sending and receiving vessel own the same published edition of the code book — the flags themselves carry no information about which code book they belong to. Semaphore has no equivalent dependency: its 26-letter alphabet is the entire system, memorised once and never revised out from under anyone by a new edition, which is part of why it remains a useful skill to teach in full even to people who will never actually need to send a real maritime message with it, since there's nothing about it that a later revision could quietly render obsolete.

Why ships carried both rather than picking one

Neither system makes the other redundant, which is exactly why navies trained sailors in both rather than standardising on a single one. A hoisted code-flag signal works unattended and is visible to every ship in sight simultaneously, which suits a status that needs to stay posted (dangerous cargo, a distress call) far better than something one person has to keep signalling by hand. Semaphore, in turn, suits a private, real-time, back-and-forth exchange between two specific vessels that already know roughly what to expect from each other — a negotiation, a course confirmation, a message too specific for any pre-agreed code group to cover. Reach for a hoist when a message needs to keep broadcasting itself with no ongoing effort; reach for semaphore when the content is genuinely open-ended and a live, back-and-forth conversation is what the moment calls for.

Day and night are a third axis entirely

Neither system, in its classic form, works after dark, which is where a signal lamp (flashing Morse code by light rather than flag position) fills a gap neither one covers. A lighted-wand version of semaphore extends its same positional alphabet into darkness, and the International Code of Signals has its own light-based equivalents for several of its most urgent single-flag meanings, but the plain daylight forms of both systems described above assume a clear sightline in good light. Choosing between semaphore and flag hoists is really a choice within daylight signalling specifically; after dark, the practical choice shifts toward whichever light-based method a crew is trained on instead. It is a useful reminder that no single signalling method, however well designed, covers every condition on its own — a well-trained crew historically carried several complementary systems rather than betting everything on one, precisely because each system's weaknesses were covered by one of the others rather than left as a genuine gap in coverage.

Both systems reached their modern form on separate timelines

It is worth being clear that neither system is a variant of the other, despite both predating radio and both surviving into the present as backups. Semaphore’s hand-flag alphabet is generally dated to 1866, adapted from earlier land-based mechanical semaphore telegraphs. The International Code of Signals traces back further as an idea — numeric flag-hoist codebooks were already in naval use in the early nineteenth century — and reached its current nine-language, standardised form only in 1969. The two systems evolved on separate tracks, for separate purposes, and simply ended up sharing the same basic raw material: flags, held or hoisted, read by eye.

A quick decision guide

• Message fits a known category (distress, dangerous cargo, a course heading)? Reach for the International Code of Signals — a compact hoist says it faster and keeps saying it without anyone tending the halyard.
• Message is open-ended, specific, or conversational? Reach for semaphore — it can spell exactly what needs saying, at the cost of needing a live signaller and reader for the duration.
• No one is watching continuously? A hoisted signal wins by default — semaphore only works while someone is actively reading it.
• Multiple recipients in different directions need the same message at once? A hoisted flag or set of flags broadcasts omnidirectionally; a semaphore signaller effectively faces one reader (or a small group) at a time.

Both systems, in the end, rest on the same underlying strength: no batteries, no electronics, and nothing that can lose signal at the worst possible moment — which is exactly why both survived long past the point where radio made them technically unnecessary for routine use. A modern vessel reaches for radio first for almost everything, but the flag locker stays aboard precisely because the two purely visual systems it holds cover two different failure modes: one for when a message is too specific or too personal for any code book, the other for when a message needs to keep broadcasting itself long after whoever raised it has moved on to something else.