TEXT · SYMBOLS · SCRIPTS
Aurebesh-compatible font preview
Select a compatible font file from your device to preview the Latin text in this browser tab.
This mode does not contain or reproduce an Aurebesh glyph chart. The font stays local, and copied text remains Latin rather than becoming a script transcription.
Preview Latin text with a compatible Aurebesh font you select locally. The font is not uploaded; the underlying text remains Latin and is not converted into Aurebesh glyphs.
Aurebesh text preview
Choose a mode and direction, then enter text.
All transformations run in your browser without remote APIs or CDNs. Historical and fictional scripts are not universal ciphers or translators; each mode’s limits are explained next to its settings.
FEATURES AND ACCURACY
Symbol conversion with clear limitations
- Braille uses uncontracted English patterns in Unicode. It is not embossed output or a complete localized Russian Braille standard.
- Runes and Ogham represent approximate Latin spelling. Multiple modern letters can share a sign, so decoding may not restore the original spelling.
- The hieroglyph and cuneiform tables are illustrative Latin-letter substitutions, not translations into Egyptian, Sumerian, or Akkadian.
- Wingdings-style output uses a limited Unicode symbol set, not the original font or its proprietary chart. Aurebesh is only previewed with a compatible font you provide.
Before publishing or archiving, check how the symbols render on the target device; Unicode font coverage and glyph appearance vary by system.
Frequently asked questions
Which scripts are available?
Seven modes are available: Wingdings-style symbols, English Braille, illustrative Egyptian and cuneiform tables, Elder Futhark runes, Ogham, and an Aurebesh preview using your own font.
Can I use Russian text?
Yes. Alphabet-based modes transliterate Cyrillic to Latin with a fixed table by default. Decoding returns the Latin approximation, not the original Cyrillic spelling.
Is my source text sent to a server?
No. Conversion runs in your browser. Site analytics may record a visit and that a button was used, but the source text and result are not sent.
Which modes can be decoded?
Wingdings-style symbols, English Braille, and the illustrative Egyptian and cuneiform tables have reverse mappings for supported symbols. The Wingdings-style, hieroglyph, and cuneiform tables do not encode letter case; Rune and Ogham values also merge some letters.
Are the hieroglyphs and cuneiform translations?
No. These modes use an arbitrary substitution of Latin letters with Unicode signs for a visual effect. They do not encode words, sounds, or grammar of ancient languages.
Why does the tool report an unsupported character?
The mappings are intentionally limited. The message identifies the character and its position; remove or replace it, or use another mode.
Why might some symbols look blank or different?
Rendering depends on the font, operating system, and application. Some systems do not have a font for certain Unicode blocks.
Does switching modes reload the page?
No. Choose another option in Script or mode; the interface updates without reloading. Each mode also has its own indexable URL.
Is letter case preserved?
Braille marks uppercase Latin letters. Wingdings-style, hieroglyph, and cuneiform tables do not encode case; runes and Ogham also cannot restore the original capitalization.
Is every output an accurate historical rendering?
No. Treat runes and Ogham as approximate renderings of modern words, not scholarly reconstructions. The Egyptian and cuneiform tables are visual substitutions only.
Can I use the original Wingdings font?
No. This mode uses a small original set of Unicode symbols, not the official font or its mapping. Use a properly licensed font separately when exact Wingdings rendering is required.
Why does Aurebesh not convert text into new characters?
This mode does not include a glyph chart. You may select a compatible font from your device; it changes only rendering, and copied text remains Latin.