Rightwards Triangle-Headed Paired Arrows ⮆

⮆ (U+2B86) is a standard Unicode character that you can copy and paste anywhere text is accepted. This page provides a concise reference with safe tips, internal links, and practical guidance so you can use it reliably across apps and platforms.

What it is and where it’s used: Rightwards Triangle-Headed Paired Arrows is part of the Symbols family (block: Miscellaneous Symbols and Arrows). If you need styled or decorative alternatives, try our Fancy Text tool to generate compatible text that works in most modern interfaces.

History & usage: Arrows commonly indicate direction and navigation cues in interfaces and documents. The symbol discussed here is the RIGHTWARDS TRIANGLE-HEADED PAIRED ARROWS. Its codepoint is U+2B86. The name identifies it as a pair of arrows with triangle heads that point to the right. It belongs to the Miscellaneous Symbols and Arrows block and uses the Common script. In use, designers assign it to show forward steps, progression, or linked actions. This symbol helps readers move through menus, flows, or guides. Because it is part of the Common script, it works in many languages and settings. The pairing and direction suggest a sequence or a forward path. Systems may render it in standard fonts and sizes, depending on the platform. The usage note helps explain its role without assuming any specific tool. Keep in mind that this symbol is an option for indicating forward movement in lists and instructions. It is one of many arrows used to support navigation and clarity in digital documents.

Copy and input: the quickest method is to copy the character here. You can also insert it by its codepoint U+2B86 in many development tools or editors. Some operating systems provide a character viewer or input palette that lets you search by name or code and insert the glyph into documents.

Display and fallback: if you see an empty box (tofu) or a placeholder rectangle, the active font might not include this codepoint. Switching to a font with broader Unicode coverage or using a fallback font usually fixes the issue. On the web, ensure the page’s font stack includes a general‑purpose fallback.

Related references: browse the Categories for similar characters. When choosing a symbol, prefer the official codepoint for semantic clarity and better compatibility with search, copy, and accessibility tooling.

See our category page for related symbols.