Unicode symbols & emoji

Double Sided Arrow Copy And Paste

Copy left right arrow, inspect its exact Unicode sequence, and check appearance, spacing and character support in your destination.

By Uddhav Gopani, FounderPublished 27 September 2026Updated 29 September 2026

Use the exact left right arrow sequence below as plain text. This is one left-right arrow character. It is different from two separate arrows placed beside each other. Font width and line thickness can change, but its left-and-right direction is part of the character identity.

Copy the actual characters

Copyable left right arrow

↔

Click or tap inside the example field, select its contents, and copy. On a desktop, Ctrl+A while the field has focus selects that field’s text; on macOS use Command+A. Paste into a private draft or a plain-text note first. Check that you selected the character sequence rather than the field label, quotation marks from surrounding prose or a screenshot of the example.

What this sample contains

The base example contains 1 Unicode code point: U+2194. Those code points describe the text itself. They do not record a fixed pixel width, font weight, foreground color or app-specific drawing.

A character above U+FFFF uses two UTF-16 code units in JavaScript, even though it is one Unicode code point. A combined emoji can contain several code points while appearing as one visible unit. That is why a website’s raw string length, a code-point count and an app’s visible-character limit can disagree without any text having been lost.

Test it in the intended destination

Paste one complete example into a draft before publishing or sending it.
Inspect the draft at the normal viewing size and check whether its font supports every character.
Save the draft, reopen it, and confirm that line breaks, spacing and the chosen symbol survived.
If people will read it on another device, preview the saved text there as well. A matching character identity does not guarantee an identical picture.

Test the exact field you plan to use. A chat message, profile name, document heading and spreadsheet cell can apply different fonts or validation rules within the same application. Success in one field does not establish compatibility in another. Keep a plain-text copy of the sample so you can compare it with the saved result.

Solve appearance problems without changing meaning

A square box normally points to missing font support; replacing it with a visually similar but unrelated letter can change what the text means. If an exact color, transparent background, rotated shape or consistent outline is required, create or use an appropriate image instead of claiming that plain text guarantees those properties. A larger font can enlarge a glyph, but it does not create a separate “large” character.

For a long sequence, shorten the example until you know which part the destination accepts. Check for an accidental extra newline at the end. Do not repeatedly send large blocks merely to test a character limit: work in an unsent draft and use the application’s own counter or validation message. Preserve a useful word label alongside a decorative symbol when the message must remain understandable without the picture.

Keep the surrounding message readable

Screen readers may announce character names and can make repeated decorative symbols tedious to navigate. Use a short sequence when one example conveys the same meaning. Do not replace important instructions, a person’s actual name or a status explanation with an unexplained pictograph. For multiline art, provide a brief ordinary-text description and expect the visual arrangement to be lost when read aloud.

Symbol Copy Paste Tool offers additional characters to inspect and copy. The useful check is whether the chosen character has the intended identity and survives in the destination field. Neither the tool nor this guide grants platform verification, installs a missing emoji font or converts a symbol into an editable image.

Standards references

Unicode emoji structure and presentation and Unicode text segmentation explain the distinction between encoded text, presentation and visible character boundaries.