Transliteration is not translation
Writing your name in runes gives you your name, spelled with runes. It does not give you an Old Norse name. Almost every tool online quietly conflates the two.
Transliteration swaps the letters. Translation swaps the language. These are completely different operations, and the distinction is the single most useful thing to understand before putting runes on anything permanent.
| Transliteration | Translation | |
|---|---|---|
| What changes | The script | The language |
| Input | love | love |
| Output | ᛚᛟᚠᛖ, the English word in runes | ást, the Old Norse word, which you could then write in runes as ᛅᛋᛏ |
| Needs | A character mapping | A dictionary, a grammar, and knowledge of the target language |
| What our tool does | This | Not this |
Why this trips people up
Because "translator" is what people search for, and so it is what tools call themselves. A site offering a "Viking rune translator" that outputs ᛚᛟᚠᛖ for "love" is transliterating, and the result is not Old Norse, not Viking, and not what most users think they are getting.
That is not necessarily a problem. If you want your name written in runes, transliteration is exactly the right operation: there is no Old Norse translation of "Jessica" to be had. It becomes a problem when someone believes a transliterated English sentence is something a Viking would have understood.
What a Viking would have seen
A tenth-century Scandinavian shown ᛚᛟᚠᛖ would face two problems. First, ᛟ and ᛖ had not been part of the alphabet for two hundred years. Second, the sequence spells nothing in Old Norse. It would read as gibberish written in obsolete characters.
Transliterating into Younger Futhark fixes the first problem (the characters would at least be current) but not the second. The word is still English.
The third layer nobody mentions
There is a step between the two that gets skipped. Runic spelling is phonetic, not orthographic: carvers wrote what they heard, not a standardised spelling. A properly done transliteration should arguably work from how a word sounds rather than how it is spelled, so "Chloe" would be handled as /kloi/ rather than as c-h-l-o-e.
Our transliterator takes a middle path: it handles digraphs like th, ng, ch and qu phonetically, and otherwise follows the written letters. Every decision it makes is shown, so you can override it by respelling your input phonetically if you want a closer result.
If it is going on your skin
Sanity checks
- Does the alphabet match the era you want? Elder Futhark is pre-Viking. Younger Futhark is Viking. Futhorc is English.
- Does the tool explain its choices? If it silently produces a d-rune in Younger Futhark, it is wrong: there is no d-rune.
- Are you expecting meaning, or spelling? If meaning, you need a translation first, from someone who knows Old Norse.
- Have you checked the individual runes? Some carry modern associations you may not want.
Questions this guide answers
- Can you translate English into runes?
- Not directly, because runes are not a language. You can transliterate English into runic characters, or translate English into Old Norse and then write that in runes. Those give very different results.
- Is a rune translator accurate?
- It can be accurate as a transliterator. What it cannot be is a translator, and most tools do not draw the line clearly. Ours shows every substitution it makes so you can judge for yourself.
- How do I get an Old Norse phrase in runes?
- Get the Old Norse right first, from a dictionary, a grammar, or someone who reads the language, then transliterate that into the runic alphabet appropriate to the period you want.
Sources
Full references on the sources page. Our methodology explains the evidence labels used throughout.