Skip to content
Lizely

Rune Meanings

Search all 24 Elder Futhark characters by Unicode name, code point, transliteration, or reconstructed literal name gloss.

Privacy: your files never leave your device. All processing happens locally in your browser.

How to use

  1. 1.Search by rune, common name, code point, transliteration, or literal gloss, and optionally select one of the three aett groups.
  2. 2.Choose a matching rune to inspect its Unicode name, transliteration, reconstructed gloss, group position, and uncertainty note.
  3. 3.Use Reset catalogue to restore all 24 entries; search and filters are never stored or sent.

About Rune Meanings

Rune Meanings is a historical-language catalogue for the 24 characters commonly grouped as the Elder Futhark. It supports search by rune character, Unicode code point, standard Unicode name, common reconstructed name, transliteration, or literal name gloss. Users can also filter the catalogue to the first, second, or third aett, each containing eight entries in the displayed conventional sequence.

Unicode provides the authoritative encoded characters, code points, and standard names used here. The table begins with ᚠ at U+16A0 and ends with ᛟ at U+16DF, while selecting the specific Elder Futhark forms from the larger Runic Unicode block. Tests independently transcribe all 24 character, code-point, and Unicode-name triples and verify that each character and code point is unique.

A Unicode character name is an encoding label, not proof of the word used by every ancient runewriter. Elder Futhark inscriptions did not preserve a complete contemporary glossary beside the alphabet. Many familiar names and literal meanings are scholarly reconstructions informed by later Germanic rune-name traditions. The interface therefore labels these fields reconstructed or common-name literal glosses rather than presenting them as direct translations from one ancient source.

Uncertainty is recorded per row. Pertho has no broadly agreed literal gloss. Algiz has disputed name, sound history, and meaning, and the common elk comparison remains qualified. Kauna or Kenaz is shown with the qualified boil or ulcer gloss used by the selected independent table. Eihwaz transliteration, Laguz or Laukaz naming, and several reconstructed vocalizations vary by scholarly convention. The catalogue keeps those disagreements visible rather than replacing them with confident modern symbolism.

Penn State’s institutional reference explains the historical Runic script families, their phonetic function, Unicode encoding, and the possibility that missing fonts show boxes. The Viking Ship Museum independently states that Elder Futhark contains 24 letters and explains the limits of reconstructed early rune names. These sources provide context separate from Unicode’s encoding authority and support the product’s explicit distinction between code-point facts and linguistic reconstruction.

The catalogue does not assign modern spiritual keywords, draw a rune, calculate a reading, diagnose personality, forecast an outcome, or claim supernatural accuracy. Literal name glosses such as cattle, gift, hail, ice, sun, horse, water, day, inheritance, and household are historical-language reference labels. They are not instructions about romance, money, health, career, safety, or future events.

Search and aett filtering run entirely in browser memory. There is no fetch call, third-party dictionary request, account gate, localStorage record, sessionStorage record, or query log from the widget. Reset restores the full 24-entry catalogue and selects the first entry. If the system font cannot draw a Runic character, the Unicode code point and uppercase standard name remain readable.

Controls use native search and selection behavior, minimum 44-pixel targets, and visible focus treatment. Results reflow into a single column on narrow screens, while the rune list gains a bounded vertical scroll only when needed. Every result carries text labels for code point, transliteration, aett, position, literal gloss, Unicode name, and uncertainty, so meaning never depends on decoration alone.

Verification checks 24 external Unicode goldens, three aett groups of exactly eight, contiguous positions within each group, literal search examples, filter interactions, reset behavior, invalid code-point handling, uncertainty markers, privacy boundaries, and the absence of predictive claims. Correctness means preserving the sourced encoding facts and clearly qualified reconstruction—not validating modern divination interpretations.

Methodology & sources

Store a literal 24-row Elder Futhark catalogue using Unicode Runic NamesList characters, code points, and standard names. Add qualified common reconstructed names, transliterations, literal name glosses, row-specific uncertainty notes, and three conventional aett groups of eight. Search normalized catalogue fields locally and filter by aett. Keep disputed meanings explicit; do not add modern divination keywords, draws, prediction, storage, or network calls.

Frequently asked questions

Does Elder Futhark contain 24 runes?
Yes. This catalogue groups 24 encoded Elder Futhark forms into three conventional aett groups of eight, while the broader Unicode Runic block also contains later and variant characters.
Are the displayed rune meanings certain ancient definitions?
No. Unicode names are encoding facts, but many familiar rune names and literal glosses are scholarly reconstructions from later traditions. Disputed entries are marked explicitly.
Does this page provide rune divination or predictions?
No. It is a historical-language and Unicode reference with no draws, spiritual keywords, personality claims, forecasts, or consequential advice.

Related tools

Fortune & Divination guides

View all