Welcome to the official Contact page for Morse Signal Lab, the home of our browser-based Morse Code Translator, Audio Translator, and Morse Code Trainer. We built these tools for students, radio hobbyists, puzzle solvers, and anyone curious about encoded communication, and we want that experience to be accurate, fast, and genuinely useful. This page explains how to reach us, what kind of feedback helps us most, and what happens after you send a message.
Morse code rewards precision: a single dropped dot or an uneven dash can change a whole message. Because of that, we take reports about translation accuracy, timing, and playback behavior seriously, and we rely on users like you to help us catch edge cases our own testing misses.
How to reach us
The fastest and most reliable way to reach the Morse Signal Lab team is by email. This is our single official contact channel, and every message is read and triaged by a real person, not an automated bot:
We do not currently offer live chat or phone support. Email lets us investigate technical issues properly, including checking browser versions, audio hardware quirks, and specific Morse timing edge cases, before we reply with an answer we're confident in.
What to include in your message
For bug reports, please tell us which tool you were using (Translator, Audio Translator, or Trainer), your browser and operating system, and the exact text or audio input that caused the problem. If the issue is about timing or playback, mention the WPM setting you were using. This lets us reproduce the issue instead of guessing at it.
For content corrections, such as a mistake in a Morse code reference table or a blog post, quote the specific text and explain what you believe is wrong. For feature requests, a short description of the use case you have in mind is enough for us to evaluate it. For licensing, press, or partnership questions, let us know your organization and what you'd like to discuss.
Why people contact us
Common reasons users write in include reporting inconsistent or incorrect translations, requesting support for additional characters or symbols, flagging audio decoding accuracy in noisy recordings, suggesting improvements to the trainer's difficulty levels, and pointing out browser or device compatibility issues. We also welcome accessibility feedback, since we want the site to work well with screen readers, keyboard navigation, and reduced-motion settings.
Every message we receive, whether it's a one-line bug report or a detailed feature proposal, feeds into how we prioritize future updates to the translator, audio decoder, and trainer.
What happens after you write to us
When your email arrives, it's read and categorized based on topic, whether that's a bug, a content question, or a business inquiry. Technical reports are checked against the relevant tool to confirm the behavior before we respond, so you get an answer grounded in an actual test, not a guess.
Morse Signal Lab is maintained by a small, independent team, so replies typically take a few business days rather than a few hours. We don't use canned auto-replies for substantive questions; if your issue needs more investigation, we'll say so and follow up once we know more.
Privacy when you contact us
We only use the information you send us to respond to your request. We don't add your email address to a marketing list, and we don't share your message with third parties except where necessary to resolve a technical issue. For details on how the translator itself handles your text, Morse code, and audio input, see our Privacy Policy.
Frequently asked questions
Do you offer a support phone line?
No. Email is our only official support channel. It lets us properly investigate technical reports, including checking specific browsers, operating systems, and audio hardware, before we get back to you with an accurate answer.
Can I request a new feature for the translator or trainer?
Yes. We regularly review feature requests, including ideas for playback timing controls, additional character support, new trainer difficulty modes, and improvements to the audio decoder's sensitivity to background noise.
I found an error in a Morse code reference table or blog post. What should I do?
Please email us with the page, the specific text you believe is incorrect, and, if possible, a source we can check against. Morse code accuracy matters to us, since a single mismapped character can throw off an entire message.
Can I use the translator's output commercially?
Generally yes, output you generate through our tools (translated text, Morse sequences, or exported audio) is yours to use. See our Terms of Servicefor the full details on what is and isn't restricted.
Do you respond to every message?
We aim to. Some inquiries take longer than others depending on complexity, but every message is read, and we try to send at least a short acknowledgment even when a fuller answer needs more investigation.