Transform words into medieval Old English blackletter and gothic fraktur typography.
Search for an old english text generator and what you almost certainly want is blackletter, the dense, angular script that says diploma, beer label, tattoo. What the name misleadingly promises is Old English the language. Those are two unrelated things wearing one label.
Old English, also called Anglo-Saxon, was spoken in England from roughly the fifth century until about 1150, when it shifted into Middle English. It was not written in blackletter, because blackletter did not exist yet. Scribes used insular minuscule, a rounded hand inherited from Irish monastic practice, and their alphabet included letters English has since dropped: thorn (þ, U+00FE) and eth (ð, U+00F0) for the two th sounds, wynn (ƿ, U+01BF) for w, and ash (æ, U+00E6). The Beowulf manuscript looks nothing like a heavy metal logo.
Blackletter arrived centuries later, from around 1150 onward in northern France and Germany, as a compressed writing style that fit more words onto expensive parchment. The name Old English was attached to it by nineteenth-century type foundries selling antique-looking display faces, and it stuck hard enough that it is now the phrase most people type into a search box.
Knowing which one you mean matters here, because this page generates the typeface, not the language. If you actually need thorn and eth, you want a character picker, not a style list.
Blackletter is a family, not a font, and its four branches differ enough that calling them all Old English hides the choice you are making.
Textura is the dense, vertical, angular hand of northern Europe. The one Gutenberg's 42-line Bible was set in around 1455. Its verticals end in diamond-shaped feet and its minims are nearly identical, which is why a run of letters like minimum reads as a picket fence. It is the most formal and the least legible.
Rotunda developed in Italy and Spain and kept the round bowls that Textura squared off. It is wider, calmer, and stayed in use for liturgical and legal printing long after northern Europe moved on.
Schwabacher is the rounder German hand that dominated German printing from roughly 1480 to 1530, with bulging bowls and a looser rhythm.
Fraktur appeared around 1513 in Nuremberg, commissioned for the Triumphal Arch project of Emperor Maximilian I, with the type cut by Hieronymus Andreae. It mixes broken angular strokes with sweeping curves and gives capitals their distinctive elephant-trunk flourishes. It went on to dominate German-language printing for four centuries, until a decree dated 3 January 1941 pushed German printers toward Antiqua instead.
Only one of those four hands has a styled alphabet in Unicode, which is the constraint everything else on this page follows from.
The blackletter you picture when someone says Old English is almost never a fifteenth-century type. It is a nineteenth-century revival. Victorian and Edwardian foundries in Britain and the United States sold decorative display faces under names like Old English, Cloister Black and Engravers Old English, aimed at diplomas, invitations, memorial cards and shopfronts. Those revivals softened Textura's rigidity, added hairline spurs and swelling curves to the capitals, and widened the lowercase so it survived being set large on a certificate. Every digital Old English on your machine descends from that commercial revival, not from a facsimile of a scribal hand.
That matters for what this page can do. The 66 entries in the Blackletter and gothic set are not typefaces at all. They are character substitutions, so what your reader sees depends entirely on which font their device picks to render the code points. On Windows that is usually Segoe UI Symbol or a Noto fallback; on Apple devices it is a system fallback face; on Android it varies by manufacturer.
You are choosing letterforms only in the loosest sense: you pick a Unicode alphabet, and someone else's operating system picks the shapes. Two people can copy the identical string and see visibly different blackletter, and neither of them is seeing a design decision you made.
Unicode's Fraktur alphabet starts at U+1D504, MATHEMATICAL FRAKTUR CAPITAL A, and you would reasonably expect the other twenty-five capitals to follow in order. They do not. Five slots in that run are left unassigned and hold nothing: U+1D506, U+1D50B, U+1D50C, U+1D515 and U+1D51D, exactly where C, H, I, R and Z belong.
Those five letters exist, just somewhere else. They had already been encoded in the Letterlike Symbols block (U+2100–U+214F) before the mathematical alphabets arrived, because mathematicians used them as standalone notation: ℭ at U+212D, ℌ at U+210C, ℑ at U+2111, ℜ at U+211C and ℨ at U+2128. Unicode avoids encoding the same character twice, so the mathematical range was left with holes rather than duplicates.
The practical consequence is that any converter written as naive offset arithmetic (take the letter, add a fixed number, emit the result) produces unassigned code points for those five letters, and your reader gets empty boxes in words like Chrome, Rise or Zion. A correct implementation carries an explicit exception table for them.
The bold Fraktur alphabet beginning at U+1D56C has no such problem: it was encoded in one pass and runs contiguously through U+1D59F. Lowercase is complete in both sets; only the capitals are broken.
The Mathematical Alphanumeric Symbols block was not created to make text look medieval. It was added in Unicode 3.1, released in March 2001, so mathematical writing could distinguish variables whose meaning depends on their styling, a Fraktur ℜ for the real part of a complex number is a different thing from an italic R, and a paper loses meaning if the two collapse together. Every blackletter style on this site borrows from that block.
Two consequences follow. First, these characters carry compatibility decompositions: under Unicode Standard Annex #15, applying NFKC or NFKD normalization maps them straight back to ASCII letters. Any system that normalizes input before storing it (many username fields, some search indexes, plenty of databases) will quietly turn your blackletter into plain letters, and nothing you do on your end prevents it.
Second, semantics. To software, ℌ is a mathematical symbol, not the letter H. Spell checkers do not check it. Language detection does not recognize it as English. Text-to-speech has no reason to pronounce it. Translation tools pass it through untouched.
None of that is a fault in your text or in this tool. It is the difference between applying a font, which leaves the characters alone, and swapping the characters for different ones that happen to resemble them.
Fraktur characters live in Plane 1, the Supplementary Multilingual Plane, above U+FFFF. In UTF-16, the encoding JavaScript strings and many platform character counters use internally, anything above U+FFFF is stored as a surrogate pair, so one visible letter occupies two UTF-16 code units. A field that counts code units rather than characters therefore accepts roughly half as much styled text as plain text. An Instagram bio caps at 150; in blackletter, expect to fit somewhere near 75 letters before the field cuts you off, with the counter disagreeing with what your eye sees.
There is a wrinkle specific to this alphabet, and it comes straight from the code point holes. The five letterlike capitals, ℭ ℌ ℑ ℜ ℨ, sit inside the Basic Multilingual Plane at U+2100 and above, so they cost one code unit each while the other twenty-one capitals cost two. The same word costs a different amount depending on which letters it contains, which makes estimating by hand useless. Watch the per-row counter instead.
The practical move is to style short strings: a display name, a headline, a first line. Style a whole paragraph and you pay the doubling on every character, burn your cap, and hand your reader a wall of text they have to decode letter by letter.
This is the cost worth stating plainly. Screen readers handle these characters inconsistently: depending on the reader, the verbosity setting and the installed speech dictionary, a blackletter word may be spelled out character by character, read as a string of symbol names, or skipped in silence. Someone using assistive technology does not receive your styling. They receive noise or nothing. If the text carries information rather than ornament, put a plain version somewhere the reader can reach.
Search is the other loss, and it is total. Plain-text search does not match substituted characters, so a reader pressing Ctrl+F for the word gothic will never match its blackletter twin, a site search will not surface your post, and a search engine crawling a bio written this way has no reason to connect it to the words you meant. Autocomplete misses. Alphabetical sorting files styled entries wherever their code points fall, far above the Latin letters rather than beside them.
Copy and paste is lossy in the other direction too: pasting blackletter into a form that rejects non-ASCII input gets you an error, or a silently stripped string you never notice until later.
Style what is decoration. Leave what has to be searchable, readable and machine-parseable as ordinary characters.
Blackletter never disappeared; it retreated to jobs where the connotation is the point. Newspaper mastheads keep it because a masthead is a signature, and several of the longest-running English-language dailies still set their nameplate in a Textura-derived face. Diplomas, certificates and legal engrossments keep it because the document is supposed to look older than you are. Beer and spirits labels keep it as a claim of German or Belgian brewing lineage. Metal band logos and tattoo lettering keep it because it is the most aggressive script the Latin alphabet offers.
Notice what those uses share: all of them are rendered as print or images, where a real typeface is installed and the shapes are under someone's control. That is the right way to use blackletter whenever you have the choice. Set an actual font (a licensed digital revival, loaded in CSS with @font-face or chosen in your design tool) and you get proper letterforms, kerning, ligatures, and text that stays selectable and searchable underneath the styling.
Unicode substitution is the workaround for places where you cannot install anything: a social bio, a chat message, a comment field, a game name box. That is a genuine need and this page serves it for free, in your browser, with nothing to sign up for. It is still a substitute for typography rather than typography.
There are two causes and they are easy to tell apart. If most characters break, the reader's device lacks a font covering Plane 1 and the renderer falls back to a .notdef box. If only C, H, I, R or Z break, the converter emitted the unassigned Fraktur slots instead of the letterlike symbols those five letters actually use.
In type history, yes, gothic, blackletter and Old English all name the same broken-script family. But in American type naming, gothic also means a sans serif: Franklin Gothic, News Gothic and Highway Gothic contain no blackletter at all, and Japanese typography uses goshikku for sans serif too. Only context tells you which sense someone means.
Not practically. No keyboard layout ships with the Fraktur alphabet, and Windows Alt codes reach only a small slice of the Basic Multilingual Plane. Your realistic options are copy and paste, a character picker such as Windows Character Map or the macOS Character Viewer, or hexadecimal code point entry in software that supports it.
Use the page to settle on wording, not on characters. The shapes you see come from whichever fallback font your device chose, so your artist may see different letterforms on their screen. Give them a named typeface reference or a vector file, and agree on the exact capitals before anything becomes permanent.
It is more tangled than people assume. The Nazi regime used Fraktur early, then reversed itself: a decree dated 3 January 1941 declared it unsuitable and pushed printers toward Antiqua. Today it appears throughout ordinary German branding (breweries, newspapers, restaurants) while far-right groups do appropriate it. Context and audience decide how it reads.
Avoid all three. Passwords are worst: normalization can rewrite your input to ASCII on one system and leave it alone on another, so identical keystrokes stop matching. Filenames usually survive but break in shell scripts and archives. A few languages permit non-ASCII identifiers, but nearly every style guide forbids them.
Because a blackletter page should not bury blackletter. This route filters to the Blackletter and gothic set (Fraktur, bold Fraktur, and the decorated and framed variants built from them) so every row is comparable. A toggle above the list opens all 358 styles whenever you want the rest.
It works, but it is the wrong tool there. The per-row Word export writes plain letters plus a real font-family instruction where a genuine blackletter face exists, because substituted characters pasted into a document without a Plane 1 font print as boxes. For anything you control, install a real typeface instead.