What this arrow symbols guide covers
The core Arrows block spans U+2190–U+21FF. It includes familiar directional signs such as ←, ↑, →, and ↓ alongside double arrows, hooked arrows, dashed arrows, and other forms used in technical writing. The block is not a single visual theme. Characters were encoded to preserve distinctions already needed in standards, mathematics, dictionaries, diagrams, and document exchange. The guide starts with that block because font coverage is usually strongest there.
Additional families live elsewhere. Supplemental Arrows-A covers U+27F0–U+27FF, Supplemental Arrows-B covers U+2900–U+297F, and Miscellaneous Symbols and Arrows covers U+2B00–U+2BFF. Dingbats, U+2700–U+27BF, also contains arrow-shaped marks. A complete arrow search therefore cannot assume that nearby-looking glyphs share one block or the same age of font support. This arrow symbols guide names the blocks so a missing glyph is easier to diagnose.
Wingdings 3 adds an important legacy chapter. Released in 1997, the icon font maps ordinary character positions to an extensive arrow set. A Wingdings document originally depended on that font being installed; copying the underlying letters did not carry the pictured arrows. Modern Unicode mappings let many of those shapes travel as real symbols, but the receiving font will not necessarily reproduce Microsoft’s original drawings exactly. The guide keeps that history next to the copy board.
Arrows at work
Interfaces use arrows as affordances: a right arrow may mean continue, open, or move forward; a down arrow may reveal a menu; a circular arrow may mean refresh or retry. Those meanings are conventions rather than properties guaranteed by Unicode. Pair an important control with a text label and an accessible name, especially when direction could mean navigation, sorting, download, or expansion. The guide will not assign a product meaning that Unicode does not encode.
Plain-text diagrams benefit from compact arrows because the connection survives in email, code comments, and notes. A sequence such as input → transform → output communicates order without an image. Bidirectional arrows can show exchange, while hooked or return arrows can suggest a branch. Alignment still depends on the destination font, so a complex diagram is safer in a monospace environment or a real diagram tool.
Mathematics and logic assign precise meanings to particular arrows. ⇒ often represents implication, → can name a function or limit direction, and ↦ commonly maps an input to its image. Authors and fields choose conventions, so visual similarity does not make characters interchangeable. In formal work, follow the notation source and use an equation system when spacing, labels above arrows, or extensible length matters. The guide is not a logic textbook; it only keeps those identities from collapsing.
Compatibility and font coverage
Basic arrows in the older U+2190 block have broad font coverage, but a valid Unicode arrow from a supplemental block may be absent in an older or narrow font. The usual symptom is tofu, an empty box standing in for a missing glyph. Font fallback can prevent tofu yet produce a symbol with different weight or vertical alignment from the surrounding text. Use this guide when you need to decide whether the box is a missing font or the wrong code point.
Emoji presentation can affect a small subset of arrow-like characters, while most mathematical arrows remain text. Platform fonts also disagree about shaft length, arrowhead angle, and whether a heavy character feels filled or outlined. Unicode preserves the identity and direction; it does not require every font designer to draw the same artwork. A symbol copied correctly can therefore look unexpectedly different without being corrupted.
Paste the exact arrow into the actual destination and test the devices that matter. Check that direction remains unambiguous at small sizes, that a fallback glyph does not resemble another operator, and that assistive text explains any interactive meaning. If the arrow carries a safety instruction or critical navigation choice, add words rather than relying on shape alone. The guide’s compatibility rule is the same on every page: test the exact character.
Direction can also change meaning across writing systems and layouts. A right-pointing arrow may feel like forward navigation in a left-to-right interface, while a mirrored layout can use the opposite direction. Do not hard-code cultural reading order into a control without testing localization. For plain text, state the action beside the symbol; for an interface, let the design system and bidirectional-layout rules determine whether an icon should mirror.
Copying an arrow from a styled page does not copy the page font. The destination stores the code point and chooses its own glyph, so weight and spacing can shift after paste. If exact artwork is a requirement, use an accessible icon asset with a text alternative. Use Unicode when searchability, compact plain-text exchange, and character identity matter more than pixel-level consistency. This arrow symbols guide prefers identity over artwork.
Using the LiteralKit arrow collection
LiteralKit’s Arrow Symbols collection contains 40 characters in five groups of eight: Horizontal, Vertical, Diagonal, Hooked, and Circular. Each entry includes a Unicode name and code point. The board is a practical selection of directional forms, not an exhaustive catalog of every mathematical or supplemental arrow in Unicode. The guide is the decision layer; the board is the copy step.
Start with the role you need. Horizontal covers common left, right, bidirectional, barred, and long arrows. Vertical and Diagonal cover movement on those axes. Hooked includes return, loop, wave, and tail forms. Circular contains rotation and corner shapes. Copy one candidate, compare its name with the intended meaning, and test it in the target font before publishing. The guide will not invent a name Unicode does not give.
Use the Wingdings Translator when the goal is to reproduce or decode a legacy Wingdings arrow mapping rather than select by Unicode name. Use Math Symbols when an arrow participates in logic or another mathematical expression and you also need related operators. These tools overlap visually, but their contracts differ: curated arrow copying, legacy font translation, and mathematical symbol reference. Read the guide, then open the matching tool.
Choosing an arrow by meaning, not shape
Two right-pointing marks can still be the wrong object. A short → is a poor stand-in for ⇒ if the surrounding text is about implication, and a maps-to arrow is the wrong choice for a “next page” control. Sort the candidate by Unicode name and by the sentence you need to survive a font change. If the name does not match the job, pick again. This arrow symbols guide exists because shape search collapses those jobs.
Interactive uses need an accessible name even when the visible glyph is obvious to you. “Next,” “Expand,” “Download,” and “Move item right” are different actions that can share a similar arrowhead. Put the action in visible text where users could reasonably disagree, and keep the accessible name in sync when the layout mirrors. A decorative arrow in a diagram can stay unlabeled if the surrounding words already state the direction.
When the destination cannot be trusted—an older phone, a locked form, a PDF that substitutes fonts—fall back to words. “Then,” “from … to …,” or “implies” will outlive a missing supplemental glyph. Keep the Unicode arrow for compact notes and for readers whose fonts cover it. The guide is a filter, not a promise that every arrow on the board will draw on every device. Test once in the real destination before the arrow becomes the only instruction.
Frequently asked questions
Why are there several different right arrows?
Unicode preserves distinctions in length, weight, tail, hook, bar, direction, and technical meaning. A plain right arrow, a maps-to arrow, and an implication arrow may look related while serving different notation. Choose by the character name and context, not by shape alone. The guide repeats that rule because shape search is the usual failure.
Why does an arrow show as an empty box?
The selected font lacks a glyph for that code point and the system found no suitable fallback. Try a common arrow from U+2190–U+21FF or a font with broader symbol coverage, then verify the result on the audience’s devices. The guide treats tofu as a coverage problem, not a corrupt copy.
Are Wingdings 3 arrows the same as Unicode arrows?
Wingdings 3 is a 1997 symbol font that draws arrows at ordinary character positions. Unicode later provides identities for many comparable symbols. A Unicode mapping travels as a character, but its modern font glyph may not look exactly like the original Wingdings artwork. The guide keeps those identities separate.
Can I use an arrow instead of a button label?
Only when the meaning remains clear and accessible. Arrows can mean next, open, sort, download, expand, or move. Give interactive controls an accessible name and add visible words where users could reasonably interpret the direction in more than one way. This arrow symbols guide is not a replacement for that label.
Sources
Unicode Arrows chart — Official names and code points for the core Arrows block.
WAI-ARIA Authoring Practices: button pattern — Accessibility reference for labeling icon-only controls.