Rune Translator: Elder Futhark for Tattoos, Games, and Decoding Real Inscriptions

The Elder Futhark is the oldest runic alphabet archaeologists have catalogued. It was carved on weapons, burial stones, and jewelry by Germanic and Norse peoples from roughly the 2nd century to the 8th century CE. Despite being over 1,700 years old, those 24 symbols keep showing up in tattoo studios, video games, tabletop campaigns, and TV title cards. If you need to go from English to those glyphs — or read them back — a rune translator handles the whole mapping for you.

This guide covers exactly how the transliteration works, where it differs from genuine historical spelling, and how to get rune text right whether you're designing a tattoo, building a fantasy world, or just trying to decode a sword inscription from a game.

The 24 Runes and How They Map to Letters

The Elder Futhark contains exactly 24 runes, organized into three groups of eight called ættir. The Unicode runic block (U+16A0–U+16FF) encodes 89 characters in total to cover not only Elder Futhark but also Younger Futhark, Futhorc, and related medieval scripts (Unicode Standard, Chapter 8). For transliteration purposes, only the 24 Elder Futhark runes matter.

Mapping English's 26 letters onto 24 runes means a few letters share a glyph:

| Letter(s) | Rune | Name | |-----------|------|------| | f | ᚠ | Fehu | | c, k | ᚲ | Kaunan | | v, w | ᚹ | Wunjo | | q | ᚲ | (folded to k) |

Numbers have no runic equivalent at all — the Elder Futhark predates positional numeral systems in northern Europe — so digits in your text pass through unchanged.

How Two-Letter Sounds Work (And Why They Matter)

This is the detail that catches most people off guard. Three English letter pairs correspond to a single Elder Futhark rune:

• th → ᚦ (Thurisaz)
• ng → ᛜ (Ingwaz)
• ei → ᛇ (Eihwaz)

A translator handles these by matching the pair before checking individual letters. That means the word thing produces three runes — ᚦᛁᛜ — not four. The word Thor encodes as ᚦᛟᚱ, three glyphs not four, because the th at the start is one rune.

Here's a real input/output pair you can verify yourself:

Input: northern king Output: ᚾᛟᚱᚦᛖᚱᚾ ᚲᛁᛜ

Count the runes: northern has 8 Latin letters but becomes 8 glyphs with th collapsing into ᚦ and the final n staying ᚾ. King has 4 letters but the ng digraph becomes 1 rune, so it encodes to 3 glyphs ᚲᛁᛜ. The space between the words passes through as-is.

Decoding reverses the process: paste ᚦᛟᚱ into the Rune Translator with direction set to decode, and you get thor back in plain letters.

Getting a Rune Tattoo Right

I tested a dozen personal names and short phrases through the translator before writing this, paying attention to the outputs a tattoo artist would actually work with. A few things I noticed:

First, the output is real Unicode from the runic block, not an image or a custom font. That means you can paste it directly into Illustrator, Procreate, or a tattoo design app and it scales to any size without losing crispness. If you see empty boxes in your design software, the font lacks runic glyphs — switch to a font like Noto Sans Runic, which covers the block.

Second, the tool is a transliteration, not historical spelling. A genuine runic inscription would record sounds in Proto-Norse, often drop vowels, and sometimes use bind-runes (two glyphs merged into one) that no automatic converter can reconstruct. What you get from a rune translator is a clean, reversible letter-for-letter mapping — every English letter goes to a specific rune, and the rune decodes back to that letter. For a tattoo or a logo that is meant to read your name or a short phrase, that is exactly what you want.

Third, double-check the transliteration before it becomes permanent. Paste the rune string back into the decode direction and verify the letters match what you intended. This catches mistakes from copy-paste or from splitting a two-letter sound across a line break in your design.

Runes in Games, D&D, and World-Building

The Rune Translator tool has a share-link feature that encodes your input and direction in the URL. For game masters and indie developers, this is practical: run the place names for a map through the converter, grab the share link, and send it to the artist or co-DM. They open the same set of rune spellings you produced, with no screenshots and no transcription errors.

For video game or film prop designers working at scale, the Unicode output has a concrete advantage over rasterized rune fonts: you can store rune text as a plain string in a localization file or asset database, search it, and replace individual glyphs programmatically. An image of rune text cannot do any of that.

If you want to add texture beyond just runic glyphs — say, a cipher layer on top of the transliteration — you might layer this with tools like the Fancy Text Generator to apply additional visual styling for titles or banners.

Decoding Runes You Encounter in the Wild

Video games, especially the Dark Souls series, Elder Scrolls games, and Hellblade: Senua's Sacrifice, scatter runic inscriptions throughout their environments. Museum gift shops sell replica amulets with runes. TV shows use runic title cards. People encounter these and want to know if they actually say something.

A word of caution: not every runic inscription follows Elder Futhark. Younger Futhark, used after the 8th century, has only 16 runes and maps them differently. Anglo-Saxon Futhorc has 28–33 runes. The glyphs look similar but a Younger Futhark text decoded through an Elder Futhark key gives nonsense.

For most modern games and fantasy media, Elder Futhark is the system used — it is the one that looks most like the popular mental image of "Viking runes." Switch the translator to decode mode, type or paste the glyphs, and the tool expands ᚦ back to th, ᛜ back to ng, and you get readable text. If the result is still garbled after decoding, the source may have used a different system, or the inscription may have been decorative with no intended meaning.

For a different kind of symbol-to-meaning lookup — when you encounter a Unicode character you cannot identify — the complement tool Unicode Character Inspector shows the code point, block name, and Unicode category for any character you paste in.

One Practical Workflow

If you are working on something where the rune text will be seen by people who might try to decode it — a game with attentive players, a tattoo on a visible spot — here is a clean verification loop:

1. Type your phrase in the encoder direction and copy the rune output.
2. Open a new tab of the same tool and paste the runes into the decode direction.
3. Compare the decode result to your original phrase.
4. If it matches, the transliteration is internally consistent and a reader with the same mapping will get the right result.

That three-step check takes under a minute and eliminates the most common complaint about runic tattoos: discovering the glyph sequence does not decode to what you thought.

---

Made by Toolora · Updated 2026-06-09