About LiteralKit
About LiteralKit
Small tools, exact results. LiteralKit publishes focused utilities for text, symbols, and notation. Each tool is built to finish one clear task and to explain its limits, instead of promising a font, a translation, or a conversion that the underlying standard does not provide.
What LiteralKit publishes
LiteralKit is the responsible publisher of this site. The site is a directory of independent tools and a small set of supporting guides.
- Notation pages turn typed text into real Unicode superscript, subscript, italic, gothic, bubble, and other letter styles.
- Writing pages cover translators such as Morse, Braille, and binary, plus a few alphabet or game-language converters.
- Symbol pages are click-to-copy collections for hearts, arrows, math signs, and similar characters.
- Guides sit beside the tools when a topic needs more explanation than a picker can provide.
- There is no social feed, font store, or marketplace.
- Every published route needs a distinct user job, a truthful name, tested output and limitations, and enough page-specific guidance to stand on its own; overlapping tools are consolidated when that test is no longer met.
Sources, verification, and editorial responsibility
LiteralKit Editorial is the organisation label for the publishing work described here, not a claim about a named person or outside credential. Unicode mappings are checked against Unicode character names, code charts, and versioned data. Symbol collections keep code points visible and are curated by defined category boundaries. Historical glossaries cite the dictionaries used for spot checks; algorithmic pages disclose their formula or rule; guides link their primary or authoritative references in a visible Sources section.
Tests lock deterministic mappings, boundary behavior, metadata, routes, and structured data. A material change updates the affected page date and its tests. Font coverage, app validation, screen-reader output, historical meaning, and contextual translation can still vary, so consequential use needs a destination test or qualified review.
Conversion stays in the browser
Almost every tool converts text locally in JavaScript in your browser. Typing into a generator does not create an account, does not upload the source to LiteralKit for conversion, and does not build a history of what you typed. You see the result on the same page and copy it when you are ready. Shakespeare Translator is the documented exception: it sends the submitted text to LiteralKit’s server and its configured provider only after you press Rewrite or Try another, as described on the Privacy page. All other conversion on the site is designed to work without a network round-trip for the text itself.
Honest Unicode coverage
Fancy-looking letters on this site are Unicode characters, not installable font files. Where Unicode defines a form, the tool maps it. Where Unicode has no form, the character stays plain instead of being replaced with a lookalike from another writing system. Tools label mixed coverage and keep digits or punctuation unchanged when a style has no mapping. Destination apps still draw their own glyphs, so the same pasted character can look different on two phones, and an older font may show a box. That is a font-coverage issue, not a silent rewrite. Each tool’s page states what it converts and what it leaves alone.
No account
Core tools are free and do not require a login. There is no user profile, no saved conversion history product, and no paywall in front of Copy. If a page needs a network call—Shakespeare after Rewrite, or the optional product-suggestion form—it says so on that page. You can use the directory, convert text, and copy a result without creating credentials.
How the site is supported
LiteralKit may eventually be supported by clearly labeled display advertising. During verification, no route is eligible to load live ads. A later launch requires an explicit flag and the published route policy; navigation, trust, error, noindex, and other excluded surfaces remain outside the ad contract. Ads must never be inserted into text, converted output, or Copy controls.
Corrections and material updates
Questions, incorrect results, accessibility problems, and corrections belong on the Contact page. Include the tool URL and the smallest example that reproduces the issue. Do not send confidential text. LiteralKit reviews reproducible reports against the cited source or test, corrects the page and data when warranted, and records a material content change in that route’s last-modified date.
Questions or corrections?
Visit the Contact page to ask a question, report an incorrect result, or suggest a documented correction.