Morse Code Interpreter: from signals to meaning

18 WPM 600 Hz ×1
Audio, flash, and vibration playback WAV download, no signup Full ITU character set Works offline
Beyond letter-for-letter

Interpreting Morse is decoding plus meaning

Decoding turns ... --- ... into letters; interpreting tells you someone is in distress. Real Morse traffic is dense with abbreviations, Q-codes, and procedural signals that translate into letters but not into sense unless you know the conventions. The interpreter above decodes anything you paste instantly, both directions, with playback and live highlighting, and this page adds the layer no character chart covers: what the codes operators actually send really mean, and how to build the by-ear copying skill that turns heard rhythms into understood messages.

The meaning layer

Interpreting Morse abbreviations and Q-codes

A century of operators compressing common phrases produced a shared shorthand: two or three letters that carry a whole sentence. These are the ones you will hear most, with what they actually mean. Click any row to hear it as Morse.

Common Morse abbreviations and Q-codes in amateur use. A Q-code followed by a question mark asks the question; sent plain, it states the answer. Click a row to play it.
CodeMorseInterpretation
CQ-.-. --.-Calling any station: an open invitation for anyone hearing it to reply▶ play
DE-.. .From / this is: precedes the sender's call sign▶ play
K-.-Over: invitation for any station to transmit▶ play
R.-.Received / roger: everything copied correctly▶ play
73--... ...--Best regards: the standard friendly sign-off▶ play
88---.. ---..Love and kisses: the affectionate sign-off▶ play
QTH--.- - ....My location is (or, with a question mark, what is your location?)▶ play
QRZ--.- .-. --..Who is calling me?▶ play
QSL--.- ... .-..I confirm receipt (also the name of the confirmation postcards hams exchange)▶ play
QRS--.- .-. ...Send more slowly: the most useful code a learner can know▶ play
ES. ...And: borrowed from old American Morse▶ play
TU- ..-Thank you: often heard at the end of contest exchanges▶ play

Prosigns such as SOS, AR, and SK are a separate category, sent as single run-together patterns; the prosign table on the main page plays each one correctly.

The human skill

How to interpret Morse by ear

Operators call it copying, and it is the skill this page is built to practise. The workflow that works:

Transcribe what you hear

Listen to the Morse, at reduced speed if you can get it, and write the rhythms as dots and dashes: . for every short tone, - for every long one, a space when a letter ends, a slash at the longer word pauses.

Paste and decode

Paste your transcription into the interpreter above. Correct patterns become text instantly; anything that matches no real character is flagged, which is exactly where your transcription slipped, usually a missed gap or a dah heard as a dit.

Compare against playback

Press Play and follow the live highlighting. Hearing your transcription back, element by element, against your memory of the original is the fastest correction loop there is, and over time the decode step happens in your head before you reach the keyboard.

FAQ

Morse code interpreter questions, answered

What does a Morse code interpreter do?
It converts Morse code into readable text and, in the fuller sense this page takes seriously, into meaning: expanding the abbreviations, Q-codes, and procedural signals that letter-for-letter decoding leaves cryptic. Paste dots and dashes above for instant text, and use the table on this page to interpret what codes like CQ, 73, and QTH are actually saying.
How do I interpret abbreviations like CQ and 73?
CQ is a general call inviting any station to answer, and 73 means best regards, the standard friendly sign-off. They decode to those literal letters and digits; the meaning comes from convention. The table above covers the dozen you will meet most, each with playback, and a Q-code followed by a question mark turns the statement into the question.
Can it interpret Morse code from a sound recording?
Not automatically; it works on typed dots and dashes rather than audio analysis. The by-ear workflow above is the practical route: transcribe what you hear as . and -, paste it, let the flagged tokens show you where you misheard, and compare with the highlighted playback.
Is this different from the Morse code decoder on this site?
Same engine, different focus, honestly stated. The decoder page concentrates on input mechanics: notation, separators, and why pasted Morse sometimes fails to decode. This page concentrates on interpretation: the meaning of the abbreviations and Q-codes, and building the by-ear copying skill.