TextToolboxTextToolbox

Remove Emojis Tool

Remove recognized complete emoji clusters with pinned Unicode 17.0 matching, explicit text-symbol and spacing choices, and sequence counts.

Built by Saurabh Kumar

Quick Answer

Remove only complete clusters recognized by emoji-regex 10.6.0 / Unicode 17.0. Bare ambiguous text symbols and source spacing stay by default; explicit text presentation always stays. Unknown or decorated clusters are retained for review. Counts describe original removed sequences, not all visible glyphs.

Unicode 17.0 / emoji-regex 10.6.0. Only complete recognized grapheme clusters are removed. Bare text symbols stay by default; explicit text presentation always stays. Limits: 1,000,000 UTF-16 units, 20,000 lines and 50,000 grapheme clusters. Review unknown sequences.

0 removed sequences; 0 unique sequences; 0 removed UTF-16 units; 0 collapsed ASCII spaces.

If Copy fails, select output and copy manually. There is no nonempty text to export when the result is empty.

Whole Emoji Clusters Only

Remove recognized complete emoji clusters while retaining the surrounding source text. Matching is pinned to emoji-regex 10.6.0 and Unicode 17.0 data. Newer, malformed or only partially recognized clusters stay unchanged for review; this is not a promise to remove every possible visible symbol. A second copy of a message for a destination that excludes emoji, an inspection of the removed sequences and their repetition counts, and a text-only draft that keeps names and languages are the typical outcomes.

From Paste to Clean Copy

  1. Paste plain text and keep the original.
  2. Leave Include text-style symbols off to retain bare ambiguous symbols such as copyright and a text-style heart.
  3. Choose Collapse ASCII spaces only if you want repeated ordinary spaces reduced.
  4. Review the automatic output, sequence counts and code-point labels. Copy or Download TXT, or copy a removed sequence for inspection.

What Counts as a Complete Cluster

Intl.Segmenter identifies grapheme clusters. A cluster must match the pinned pattern completely before deletion; joiners and variation selectors are never removed globally. Default-presentation emoji and recognized multi-code-point sequences, including covered flags, keycaps, modifier, tag and family sequences, are eligible. Bare text-presentation emoji-capable symbols stay by default. The symbol option also removes covered bare symbols. Explicit U+FE0E text presentation always stays.

Default output retains source separators, edge spaces and tabs outside removed clusters. Optional spacing cleanup collapses U+0020 runs only, including indentation; it does not trim edges. Counts measure removed clusters, their original UTF-16 units and separately collapsed spaces. Input limits: 1,000,000 UTF-16 units, 20,000 physical lines and 50,000 grapheme clusters. Segmentation depends on browser Unicode data; these limits are not performance certification.

Keeping a Copyright Symbol Deliberately

Two explicit options for ambiguous text symbols
Source code pointsDefaultInclude text-style symbols
Copyright U+00A9KeptRemoved
Copyright plus U+FE0FRemoved as one clusterRemoved as one cluster
Copyright plus U+FE0EKeptKept
Keycap one U+0031 U+FE0F U+20E3Removed as one clusterRemoved as one cluster

What Removal Cannot Judge

Emoji can carry meaning, so removal is not universally correct sentiment preprocessing. Bare symbols can be meaningful too. A whole-cluster policy deliberately retains unknown or decorated clusters rather than partially deleting them. Shortcodes such as :smile:, text emoticons, HTML entity strings and image-based stickers are not automatically decoded or deleted. Removal alone does not validate a CSV file, database encoding or destination field.

Keep spacing cleanup off when whitespace matters. Review the multilingual worked guide and use HTML text extraction with decoding only when the source actually contains encoded text. Unicode Emoji 17.0 defines presentation and sequences; the pinned matcher source documents its versioned scope.