Symbol Translator

About Symbol Translator

Symbol Translator is a small collection of browser tools for turning ordinary text into another writing system and back again. It covers Morse code, binary, Wingdings, glitch text, Egyptian hieroglyphs and uncontracted Grade 1 braille.

Why these tools exist

Most people meet these codes in a specific place: a Morse message in a film, a binary joke in a chat, a Wingdings puzzle, a name written in hieroglyphs on a souvenir, or a braille label that needs checking. The usual search results are either a bare table or a page that hides the answer behind an app or an upload. This site takes the opposite approach: the converter is the page, and the reference material sits underneath it.

Every tool works in both directions. You can type plain text and read the symbols, or paste symbols and read the letters. The detector chooses the likely direction automatically, and the character map shows which input character produced which output symbol.

How the site is built

The site is a static export built with Next.js, React and Tailwind CSS. There is no account system, database or server-side conversion. The engines are small TypeScript functions that run in the browser, and the audio, SVG and PNG exports are generated on your device.

That design keeps the tools fast, private and cheap to host. It also means a page keeps working once it has loaded, even if the network drops. The share links store a message in the URL fragment rather than on a server, so the text is not sent anywhere when a link is created.

Accuracy and limits

The alphabet tables are checked against published standards and the Unicode character database. The Morse timing follows the PARIS standard, the braille tool uses UEB capital indicators, and the hieroglyph tool is a phonetic transliteration rather than a translation of ancient Egyptian. Each tool page explains those limits next to the converter.

If you find an error in a table, a missing character or a conversion that looks wrong, please send the exact input and the expected result. Corrections are easiest to verify when they include a source.

Get in touch

Questions and corrections are welcome through the contact page.