· − · − · · − Get in Touch

Contact OnlineMorseCode

Questions, corrections, feedback, or partnerships — we read every message and aim to respond within 2 business days.

We welcome all feedback, corrections, partnership enquiries, and general questions. Our team reads every message and aims to respond within 2 business days.

Email Us

General Enquiries & Feedback

Questions about the tools, content corrections, feature requests, or anything else.

hello@onlinemorsecode.com

Content Corrections

Found a Morse code error? We take accuracy seriously — please let us know and we'll fix it immediately.

corrections@onlinemorsecode.com

What to Include in Your Message

To help us respond as quickly and usefully as possible:

Response Times

General feedback

We aim to respond within 2 business days. High-volume periods may take slightly longer.

Content corrections

Corrections are reviewed and fixed as a priority — typically within 24 hours of a verified report.

Partnership enquiries

We review all partnership proposals. Educational, ham radio, and language learning partnerships are of particular interest.

Press enquiries

We're happy to provide background on Morse code, the site, and our tools for journalism and educational content.

Frequently Asked Questions

Can I use your Morse code audio in my project?

Yes — audio generated by our translator is produced in real time by your browser using the Web Audio API. It is free to use for personal and commercial projects.

Can I embed your translator on my website?

Please contact us to discuss embedding options. We may be able to provide an embeddable widget for educational or ham radio club websites.

Do you offer advertising or sponsored content?

OnlineMorseCode does not accept sponsored content or paid editorial placements. If we mention a tool or resource it is because we genuinely think it is useful, not because we were paid to.

I found a bug — how do I report it?

Email us at hello@onlinemorsecode.com with a description of the bug, which browser you're using, and the page where it occurred. Screenshots are very helpful.