Downwards Triangle-Headed Paired Arrows ⮇

⮇ (U+2B87) 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: Downwards 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: DOWNWARDS TRIANGLE-HEADED PAIRED ARROWS is a symbol in the Miscellaneous Symbols and Arrows block, with the code point U+2B87. It is part of the Common script group, which means it appears across many languages and basic text sets. In practical use, arrows commonly indicate direction and navigation cues in interfaces and documents. This helps users understand how to move or where to look next. The symbol itself shows two arrows that point downward, sharing a triangle shape at their heads. It can be used to suggest a flow to lower sections, a list that expands downward, or a transition to a next step that lies below. In apps and on pages, it may reinforce commands like scroll or continue, guiding attention without words. Designers use such arrows to create quick visual cues for readers and users. As with other symbols in this block, it blends with text and icons, fitting into layouts that mix symbols with labels. The usage aims for clarity and quick recognition in diverse interfaces.

Copy and input: the quickest method is to copy the character here. You can also insert it by its codepoint U+2B87 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.