North East Arrow Crossing South East Arrow ⤮

⤮ (U+292E) 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: North East Arrow Crossing South East Arrow is part of the Symbols family (block: Supplemental Arrows-B). If you need styled or decorative alternatives, try our Fancy Text tool to generate compatible text that works in most modern interfaces.

History & usage: North East Arrow Crossing South East Arrow is a symbol in the Supplemental Arrows-B block and is used in the Common script. In text, the symbol combines two arrows pointing in different directions. It can appear in diagrams or interfaces where paths cross or routes meet. In interfaces and documents, arrows commonly indicate direction and navigation cues. A cross symbol often denotes close or delete in UI or an incorrect state, context permitting. When used with other symbols, it can show a crossing of routes or a junction in a chart. The name and design help designers include it in charts, maps, or control panels. The symbol should be used with care to avoid confusion with other arrows. It is not a standard alphabet character but a symbol for visual guidance. In fonts and typography, proper sizing helps it read clearly. Users expect quick meaning from such marks. This cross of arrows supports quick decision making in layouts that require directional cues, status indicators, or quick actions.

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