Unicode Fraktur text
Turn plain letters into Unicode blackletter that keeps its gothic look wherever you paste it: Hello Fraktur becomes ℌ𝔢𝔩𝔩𝔬 𝔉𝔯𝔞𝔨𝔱𝔲𝔯, while digits, spaces and emoji stay as they are. Fraktur text converts back to plain letters too. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Text
- Hello Fraktur
- Calculation mode
- Encode
- Result
- ℌ𝔢𝔩𝔩𝔬 𝔉𝔯𝔞𝔨𝔱𝔲𝔯
- Direction
- encode
- Mapped
- 12
- Unmapped count
- 1
Unicode Mathematical Fraktur turns ordinary Latin letters into blackletter look-alike characters from the Mathematical Alphanumeric Symbols block and a handful of Letterlike Symbols, so a title or caption can appear gothic even when a platform strips fonts, rich text, or markdown. Designers, metal and folk bands, heritage brands, and social creators paste those glyphs into bios, event posters, product names, and story stickers because the style travels with the characters themselves rather than with a stylesheet or image asset. Digits, spaces, punctuation, hashtags, emoji, and other scripts pass through unchanged and are listed in an unmapped report so you always know what did not convert.
How Mathematical Fraktur maps letters
Unicode Mathematical Fraktur is a fixed code-point assignment, not a font weight or OpenType feature applied by a word processor. Most capital letters live in the Mathematical Alphanumeric Symbols block starting at U+1D504 for capital A, but five capitals reuse older Letterlike Symbols: capital C is U+212D, capital H is U+210C, capital I is U+2111, capital R is U+211C, and capital Z is U+2128. Those five leave intentional holes in the 1D5xx range, so a correct converter never invents private code points for them.
Lowercase a through z form a contiguous run from U+1D51E through U+1D537. Encode walks each Unicode scalar value in your string, replaces every plain Latin letter with the matching Fraktur code point, and leaves everything else in place. Decode walks the same way in reverse: each Fraktur letter becomes the corresponding ASCII character, while spaces, digits, punctuation, and unrelated symbols stay as they are.
Because many Fraktur characters sit outside the Basic Multilingual Plane, the implementation iterates by code point rather than by UTF-16 unit, so a single Fraktur glyph is never split into half of a surrogate pair.
Where Fraktur Unicode text shows up in real work
Brand and packaging teams still reach for blackletter Unicode when a product name, festival title, or heritage mark must stand out without embedding a custom font that fails on mobile previews and messaging apps. Musicians and event organizers generate Fraktur band names and setlist headers that survive paste into ticketing platforms, Instagram bios, and Discord channels that strip rich text. E-commerce and marketplace tools need a deterministic encode path so every SKU title variant uses the same alphabet rather than a one-off paste from an unreliable generator site.
Support desks and moderation queues receive Fraktur Unicode from users and need a reliable decode path back to searchable plain text for ticketing, spam rules, and knowledge bases. If you need Mathematical Bold, bold Fraktur, HTML font tags, CSS font-family blackletter faces, Braille translation, or leetspeak substitutions, treat those as separate search intents and landings rather than overloading this Fraktur page.
What you can do with it
Gothic social captions and bios
Style Latin letters in bios, story stickers, and post captions with copy-paste Mathematical Fraktur that survives platform plain-text fields.
Decode blackletter paste into searchable plain text
Convert customer messages, band names, or scraped titles that use Fraktur Unicode back to ordinary ASCII for search, CRM, and moderation.
FAQ
What characters can become Fraktur?
Latin letters A–Z and a–z. Digits, spaces, punctuation, emoji, and other scripts pass through unchanged and are listed in the unmapped field. Unicode has no regular Mathematical Fraktur digits.
Why do C, H, I, R, and Z use different code points?
Unicode reuses older Letterlike Symbols (ℭ ℌ ℑ ℜ ℨ) for those five capitals and leaves holes in the Mathematical Fraktur range. This tool maps them correctly so round-trips match the standard.
How does auto mode choose direction?
If the input contains any Mathematical Fraktur letter (including Letterlike capitals), auto decodes to plain text. Otherwise it encodes plain letters to Fraktur.
What happens to characters that cannot map?
They stay in the result in their original form.
What does it cost?
The browser tool is free and runs locally.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/enc/fraktur-unicode \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"text":"Hello Fraktur"}'const res = await fetch("https://api.kit.forhosting.com/enc/fraktur-unicode", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"text": "Hello Fraktur"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/enc/fraktur-unicode",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"text": "Hello Fraktur"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/enc/fraktur-unicode", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"text":"Hello Fraktur"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"text":"Hello Fraktur"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/enc/fraktur-unicode", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"text": "Hello Fraktur"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "enc.fraktur_unicode",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
This capability maps A through Z and a through z in either direction: encode produces Mathematical Fraktur code points (with the standard Letterlike exceptions for capital C, H, I, R, and Z), decode restores plain ASCII letters, and auto mode picks the direction by detecting whether any Fraktur letter is already present.
How Mathematical Fraktur maps letters
Characters that have no Fraktur counterpart—digits, commas, spaces, emoji, CJK ideographs, currency signs—are not invented or dropped; they pass through and appear once each in the unmapped list so API clients can audit coverage. This page implements only regular Mathematical Fraktur letters, not bold Fraktur, Mathematical Bold, italic, double-struck, monospace, or sans-serif styles, which are separate code ranges and separate search intents.
What you send and what you get back
Send a required string field named text containing the caption, title, or label you want to style or restore. Optionally send mode as encode, decode, or auto; when omitted, auto is the default. Classic checks include encoding Hello Fraktur into blackletter letters while listing space as unmapped, decoding a Fraktur phrase that includes Letterlike capitals such as H back to plain ASCII, confirming that digits remain passthrough unmapped characters, and verifying that an empty text field is rejected rather than returned unchanged. Aliases such as input, value, data, message, and string are accepted for the same field so scripts can reuse existing payload shapes. Direction aliases such as op, operation, and direction, and short values like enc, dec, to_fraktur, from_fraktur, and blackletter are also accepted. On success the response echoes the original text, returns result as the transformed string, mode as the requested operation, direction as the resolved encode or decode path, mapped as the count of characters that hit the table, unmapped_count and unmapped as the unique passthrough characters that did not map, length as the Unicode scalar length of the result, plus script, block, and standard labels naming Mathematical Fraktur. Missing text, non-string objects for text, empty strings, unknown mode values, and strings longer than the documented maximum fail with invalid_input and a clear English message. Validation failures do not consume prepaid balance. Pricing for successful API calls is the published base of $0.002 per item.
Where Fraktur Unicode text shows up in real work
Because this capability is a pure parse engine, API pricing is the published base of $0.002 per successful item and failed validation does not consume balance.
Integration use cases
Deterministic fixtures for branding pipelines
Generate golden encode and decode vectors so design tools and CI checks always apply the same Mathematical Fraktur alphabet.