Skip to content

Arabic Morse Code Translator

How Arabic Morse Code Works

This translator uses the published non-Latin Arabic Morse mapping adopted by this site for the 28 base letters of the modern Arabic alphabet. It also treats standalone Hamza as a separate extension, ء = .. The Arabic letter assignments are not presented as an ITU Arabic alphabet.

Arabic source text is read from right to left, but every Morse group is still a time-ordered sequence of dots and dashes. A space separates letters and / separates words. See the complete Arabic Morse code alphabet for the adopted character table.

Convert Arabic Text To Morse

Enter modern Arabic text in the text field. The translator normalizes supported letter variants, then writes one Morse token for each resulting canonical character:

  • سلام becomes ... .-.. .- --.
  • أهلاً normalizes to اهلا, then becomes .- ..-.. .-.. .-.
  • مسؤول expands the seated Hamza ؤ to وء, then becomes -- ... .-- . .-- .-...

The last two conversions are deliberately lossy: the transmitted characters do not preserve the original Alef form, Hamza seat, or omitted vowel marks.

Decode Arabic Morse

Enter a space between Morse tokens and / between words. Decoding returns the canonical character assigned to each token; it does not infer spelling or rebuild a seated Hamza. For example, .-- . decodes to وء, and .. . decodes to يء, not to ؤ or ئ.

This fixed translator always interprets Morse with the Arabic mapping. Copy the sequence with its spaces intact.

Hamza And Letter Normalization

The translator applies these input rules before encoding:

InputEncoded as
أ, إ, آ, ٱا
ؤوء
ئيء
ىي
ةه

Tatweel and common harakat are omitted. Compatible Arabic presentation forms are reduced to their underlying Unicode characters where possible. These conveniences do not create new Morse letters, and decoding always returns the canonical forms rather than the original aliases.

Arabic Numbers And Punctuation

Decoded digits use the canonical Arabic-Indic forms ٠-٩. You may enter either those digits or ASCII 0-9; both encode to the digit signals listed in ITU-R M.1677-1.

The canonical comma, question mark, and semicolon are ،, ؟, and ؛. ASCII ,, ?, and ; are accepted aliases for them. The other supported punctuation and symbols are . ' ! / ( ) & : = + - _ " $ @. Entries explicitly listed in ITU-R M.1677-1 use those published values; the remaining common symbols are additional mappings retained by this site. Unsupported marks are reported instead of being silently converted.

RTL Text And Morse Order

The Arabic text field uses right-to-left direction. The Morse field stays left to right because its tokens represent transmission order. For سلام, the first token is always ... for س, followed by .-.. for ل, .- for ا, and -- for م. Do not reverse the tokens when copying a sequence between Arabic and left-to-right interfaces.

Play And Create Cards

The shared player can send the generated sequence through Audio, Screen Flash, Vibration, and a supported device's Camera Light (hardware torch). Availability of Vibration and Camera Light depends on the browser and hardware.

The shared Morse code card tool also supports Arabic text. You can download the card as a PNG. On supported devices, Share opens the system share menu with the PNG and current card URL, along with localized invitation text.

Frequently Asked Questions

Is this an ITU Arabic Morse alphabet?

No. The 28 Arabic letter assignments and separate Hamza extension come from the published non-Latin Arabic table adopted by this site. ITU-R M.1677-1 is used for digits, timing and operating conventions, and only the punctuation it explicitly lists. Other common symbols supported here are additional site mappings.

Can I type Arabic in Latin letters?

No. Latin transliteration such as salam is unsupported; enter سلام. Persian letters پ, چ, ژ, and گ, Quranic annotation signs, and other characters from the wider Arabic script are also outside this mapping.

Why does decoded text look different from my input?

Normalization discards distinctions that have no separate entry in the adopted table. Alef variants, Hamza seats, ى, ة, tatweel, and common harakat therefore cannot all be reconstructed after decoding.

References

  • Morse code for non-Latin alphabets: Arabic publishes the non-Latin Arabic letter table adopted by this site.
  • ICAO Doc 9303, Part 3 provides SATTS Arabic character correspondences used only as a comparison when documenting character treatment; SATTS is not the site's Morse mapping or output.
  • Unicode Standard, Chapter 9: Middle East-I identifies Arabic characters, digits, shaping behavior, and encoded order; it does not assign Arabic Morse signals.
  • Unicode Arabic Mark Rendering provides background on Arabic mark sequences and rendering. The decision to omit common harakat here is a site normalization rule, not a Unicode Morse standard.
  • ITU-R M.1677-1 is used for digits, timing and operating conventions, and the punctuation it explicitly lists. Other common symbols are additional mappings retained by this site; ITU does not standardize the Arabic letters used here.