Full rune descriptions in your pocket whenever you need them. In one app.
A rune translator transliterates runic characters back into Latin letters, recovering the sounds a carver wrote rather than the meaning of the words. Runes are an alphabet, not a language, so what comes back is a reading of an inscription, not a translation of it.
Paste runes into the box below, or tap them out on the on-screen rune keyboard. All six historical alphabets are read at once, and any rune shared between more than one of them resolves by a fixed priority order, Elder Futhark first.
This tool reads runes back into Latin letters one character at a time. It does not recognise words, names, or grammar; it only knows which historical alphabets a given rune shape belongs to and which sound that shape stood for. That makes it a transliteration tool, the mirror image of the rune converter, rather than a genuine translation service.
Using the translator takes four steps.
Reading a runic inscription properly happens in three stages, and everyday usage collapses all three into the word translation. This tool does the first stage only, which is worth knowing before you rely on what it hands back.
| Stage | What it produces | Example, from ᚦᛟᚱ | In this tool |
|---|---|---|---|
| Transliteration | Each rune replaced by its Latin letter, one for one, conventionally set in lower-case bold | þor | Yes, and it needs nothing but the rune tables |
| Transcription | The same text rewritten in the normalised spelling of the language it was carved in, conventionally set in italics | Þórr | No, this one needs Old Norse |
| Translation | The normalised text rendered into a modern language | Thor, the name of the god | No, this one needs Old Norse |
Each chart below lists every rune in one historical alphabet next to the English letters it can stand for. Use them to check what an unfamiliar glyph means, to see which alphabets share a given shape before you paste it, or simply to read an alphabet directly without typing anything into the translator.
This is the one behaviour that surprises people. A rune shape is not unique to a single historical alphabet; several of the six alphabets reused the same shapes for their own, sometimes different, sounds. Every character pasted or typed into this tool is checked against the six alphabets in a fixed order: Elder Futhark first, then Younger Futhark, Short-Twig, Staveless, Medieval, and Anglo-Saxon Futhorc last. The first alphabet in that order that contains the rune wins, and its own first listed letter is what gets shown, even when a later alphabet in the list uses the same glyph for a different sound.
Take the rune ᚦ. Elder Futhark, Younger Futhark, Short-Twig, and Anglo-Saxon Futhorc all use this shape for the same th/eth sound, and the Medieval Runerow adds a third spelling to that same rune's letter list. Because Elder Futhark comes first in the priority order, pasting ᚦ on its own always reads back as the Elder Futhark spelling, regardless of which of the other alphabets you actually meant.
Now take the rune ᚴ. Elder Futhark has no rune of this shape at all, so the translator skips past it and checks Younger Futhark next, where ᚴ does exist, covering the sounds G, K, C, and Q. Because Younger Futhark is the first alphabet in the priority list to actually contain that glyph, pasting ᚴ reads back as G, even though Short-Twig and the Medieval Runerow also use the same shape.
One consequence worth knowing: the alphabet tab open on the on-screen keyboard changes only which glyphs are shown to tap, never how a pasted or typed rune gets read back. There is no way to tell the translator to read a rune as one specific alphabet; the priority order is fixed for every character, every time.
If you know roughly where or when the runes you are reading came from, this table can help confirm which of the six alphabets they most likely belong to, before you rely on the translator's own priority order to settle any shared glyphs.
| Alphabet | Period | Region | Runes | Best for |
|---|---|---|---|---|
| Elder Futhark | c. 150-800 CE | Proto-Norse, Germanic | 24 | The default guess for an unlabelled inscription; checked first, so it wins most ties |
| Younger Futhark | c. 800-1100 CE | Viking Age, long-branch | 16 | Viking Age runestones and formal monumental inscriptions |
| Short-Twig | c. 800-1100 CE | Swedish-Norwegian runes | 16 | Everyday Viking Age writing, such as wood or bone with simplified strokes |
| Staveless | c. 1000-1100 CE | Hälsinge runes | 16 | Regional Swedish finds with no vertical stave; rare and approximated on screen |
| Medieval | c. 1100-1500 CE | Latin-influenced, full alphabet | 25 | Later finds mixed with Latin script, or with sounds the older futharks lack |
| Anglo-Saxon Futhorc | c. 400-1100 CE | Old English, Frisian | 28 | English and Frisian finds, the largest rune set of the six |
The conventions this tool follows, the limits it works inside, and somewhere to check each one.
Analysing a runic inscription is conventionally done in three stages: transliteration of the runes into Latin letters, transcription into a normalised spelling of the language of the inscription, and translation into a modern language. What this tool produces is the first stage.
Runologists keep those stages visually distinct on the page: transliterations are printed in lower-case bold, transcriptions in italics. Lower-case bold letters quoted for an inscription are therefore a sign you are reading a transliteration rather than a translation.
The Younger Futhark cut the row from 24 runes to 16 at the same time as sound changes were giving Old Norse a larger number of distinct phonemes, so a single rune had to cover several sounds. Reading those runes back into letters is lossy by the design of the writing system, not by a fault in the tool.
Source: Younger Futhark, Wikipedia
The Rök stone in Östergötland, Sweden, raised in the ninth century, carries the longest known runic inscription, more than 700 runes across five of its sides.
Runes have been part of Unicode since version 3.0 in 1999, which encoded 81 runic characters. Eight more followed in Unicode 7.0 in 2014, giving 89 characters in the block at U+16A0 to U+16FF. Anything outside that block, bindrunes and the Staveless row included, has no code point of its own, which is why this tool cannot read it.
Source: Runic (Unicode block), Wikipedia
The output is a letter-by-letter transliteration, not a translation into modern English meaning. Runes recorded sounds the way the Latin alphabet does, so translating ᚱᚨᚷᚾᚨᚱ returns the sounds ragnar, a name, not an English sentence with a meaning of its own. A genuine Old Norse or Old English inscription still needs someone who knows that language to read it as a sentence.
Several runes in the underlying tables list more than one letter they can stand for, because a single historical shape covered more than one related sound. The translator always shows the first listed letter, so any rune with alternate readings settles on one answer even where the original carver could have meant either.
Real runestones often mark the space between words with a raised dot, a cross, or a colon-like symbol rather than a blank space. Pasting that mark, shown here as ×, reads back as an apostrophe, the closest plain Latin character to a historical word divider. Plain spaces are preserved as spaces, exactly as typed.
Anything that is not a genuine Unicode runic character, such as a similar-looking Latin letter, a stray symbol, or a digit, is shown highlighted in red rather than guessed at or silently dropped. None of the six alphabets had runes for numbers or most punctuation, so a red mark there is historically accurate rather than a fault in the tool.
A bindrune fuses two or more runes into a single carved shape and generally has no Unicode code point of its own, so this translator cannot separate one back into its parts. Worn, damaged, or ambiguous carvings on a real find need the judgement of someone trained to read runestones, not a character-by-character tool like this one.
Four short strings run through the translator, so you can see exactly what the tool outputs before pasting your own.
Paste ᚱᚨᚷᚾᚨᚱ and the translator reads back ragnar. Every glyph maps one to one onto a single Latin letter in Elder Futhark here, so nothing is lost and nothing needs the red unmapped highlight.
Paste ᚦᛟᚱ and the translator reads back þor, not thor. The rune converter replaces the English digraph TH with the single letter þ before matching a rune, so reading that same rune back only ever returns þ; it has no way to know the original spelling used two letters, not one.
Paste ᚴ on its own and the translator reads back g. Elder Futhark has no rune of this shape, so the translator moves on to the next alphabet in its priority order, Younger Futhark, where ᚴ exists and its own first listed letter is g.
Paste any character that is not a genuine Unicode rune, an @ symbol for instance, and the translator does not guess. It is shown highlighted in red and passed through unchanged, the same treatment an unmapped letter gets in the rune converter.
Paste runes into the box, or tap them out with the on-screen rune keyboard, and the Latin transliteration appears beneath as you go. There is no button to press and no alphabet to choose first; the translator checks all six historical alphabets automatically. Read the result directly, or copy it for later.
You can paste runes as text, but not a photo. If the runes came from an image, type or tap in each character yourself first, using the on-screen rune keyboard if you are unsure which key matches which shape. The translator only reads Unicode text; it cannot read pictures.
It lets you enter runes even though a standard keyboard has no runic keys. Tap the alphabet tab matching the runes you are copying, then tap each glyph in order; the letters a key stands for are shown as its tooltip. Switching tabs changes only which glyphs are shown, not how typed runes are read.
The usual cause is that the pasted character is not actually a Unicode runic character, for example a similar-looking Latin or Cyrillic letter, or a symbol copied from an image rather than text. Anything the translator cannot match against its six alphabets is shown highlighted in red rather than silently dropped.
Several historical alphabets assigned one rune shape to more than one related sound; Elder Futhark's Thurisaz rune, for instance, stands for both þ and ð, the two related th sounds in Old Norse and Old English. The translator always returns the first listed letter for a match, settling on one reading even where the original carving could plausibly mean either.
No. Every rune is read the same way regardless of which keyboard tab happens to be open, by working through a fixed alphabet priority order rather than by detecting a source alphabet. Knowing which alphabet your text came from only helps you type it with the matching keyboard tab; it does not change how the reading resolves.
Each futhark was built for a different stage of the Norse or Old English sound system, so a glyph shape carried over from an earlier alphabet into a later one was sometimes reassigned. The rune stands for G, K, C and Q in Younger Futhark, for example, but only K and Q in the Medieval Runerow.
No. Runes are an alphabet, not a language, so the translator only turns rune characters into their nearest Latin letters; it has no knowledge of Old Norse or Old English grammar or vocabulary. Reading an actual Old Norse sentence, rather than a single name or word, requires knowing that language separately.
No. Several historical alphabets used fewer runes than English has letters, so more than one Latin letter can collapse onto a single rune shape, and only one of them comes back out. Treat the result as a close phonetic reading, not a guaranteed reconstruction of the original spelling.
A standard keyboard has no runic keys, so use the on-screen rune keyboard built into this tool instead: pick the matching alphabet tab, then tap each glyph. Some operating systems also support typing Unicode characters by code point, but that method is slower and easy to get wrong.
Yes, for five of the six alphabets, which use standard Unicode runic characters that display correctly almost anywhere. The Staveless alphabet is the exception: it uses approximated symbol characters rather than true Unicode runes, since Staveless script was never added to the Unicode standard.
That happens when the device or app displaying the text has no font installed that covers the Unicode runic block. The character itself pasted correctly; it is a missing font, not a translation error, and switching to a device or browser with a runic font installed usually fixes it.
It is the word divider used on many real runestones, carved as a raised dot, a cross, or a colon-like mark rather than a blank space. The translator reads × back as an apostrophe, the closest single Latin character to what that historical mark represented.
Type or paste the runes you can identify into this translator for a rough phonetic reading, then treat that as a starting point rather than a finished answer. Genuine runestone inscriptions often mix damaged letters, bindrunes, and regional spelling this tool does not attempt to resolve; published academic transcriptions exist for most known stones.
No. A bindrune fuses two or more runes into a single carved shape, but the translator matches one Unicode character at a time against its six alphabet tables. A bindrune typically has no Unicode code point of its own, so it will either show as unmapped or be read as whichever single rune it happens to resemble.
The converter goes one direction, English into runes, for writing a name or word out in a historical alphabet. This translator goes the other way, runes back into English, for reading text you already have in runic form. They are separate tools, linked to each other for exactly that reason.
No, the round trip is lossy. Several Latin letters collapse onto a single rune when converting to runes, so K, C and Q all become the same Elder Futhark rune, and translating that rune back only ever returns K, never C or Q. Running text through both tools in sequence will not reliably reproduce the original spelling.
This site's individual rune-meaning pages cover all 24 Elder Futhark runes, with the history, sound, and traditional associations behind each one. The translator itself only handles reading rune characters back into letters; it does not explain what any single rune has historically meant.
It means replacing each character of one script with its counterpart in another, letter for letter, without touching the language. Transliterating the runes for ragnar returns ragnar: the same word, in a different alphabet. Translation would turn Old Norse into English, which needs knowledge of Old Norse that no character-mapping tool has.
No. Google Translate works between languages, and runes are an alphabet rather than a language, so there is nothing there for it to translate from. What the job needs is a transliteration tool like this one, which maps rune characters back to Latin letters and leaves the language alone.
About 6,000 runic inscriptions are known from Scandinavia, of which roughly 3,000 are runestones. Most were raised between 950 and 1100 CE, and the Swedish district of Uppland alone accounts for 1,196 inscriptions in stone, the highest concentration found anywhere.
The Rök stone in Östergötland, Sweden, raised in the ninth century, with more than 700 runes carved across five of its sides. It is also among the hardest to read, mixing rune rows and encrypted passages in a way that is far beyond what any character-by-character tool can resolve.
Published academic transcriptions exist for most known stones. The standard reference is the Scandinavian Runic-text Database, Samnordisk runtextdatabas, maintained at Uppsala University, which catalogues inscriptions by a signum such as U 1034 for an Uppland stone. This tool reads characters and holds no catalogue of finds.
Which rune are you?
Seven questions, about a minute, and you get one of the 24 Elder Futhark runes. The scoring is shown as you answer. Free, no signup.
All six futharks offline. Save your favourites.