Object Replacement Character U+FFFC

If you have ever pasted text and found a small empty box —  — sitting in the middle of it, you have met the Object Replacement Character (U+FFFC). It is one of the most commonly encountered "mystery characters" on the web, and it almost always means the same thing: an image or attachment used to be there.

When you copy rich text that contains an inline image, sticker, equation, or attachment, the underlying system needs a way to mark the spot where that object lived. Unicode reserves U+FFFC for exactly this purpose. The visible object is dropped when the content becomes plain text, but the placeholder character stays behind — and most fonts render it as an empty rectangle or a blank gap.

Where the  Box Comes From

The Object Replacement Character shows up most often when content moves from a rich editor into a plain-text field:

• iMessage and Apple Notes. Copying a message or note that contained a photo, sticker, or audio clip leaves a  where the attachment was.
• Google Docs and Microsoft Word. Copying a paragraph with an inline image into a chat box, code editor, or form field.
• PDFs. Extracting text from a PDF that had embedded figures or form fields.
• Email. Forwarding or quoting messages that contained inline images or logos.
• Web pages. Copying content where an emoji image, icon, or embedded widget sat inside the text.

In every case the object is gone but its placeholder survives, which is why the box can travel silently into usernames, form submissions, code, and databases.

How to Remove It

The fastest way is to paste your text into the Invisible Character Viewer on the homepage and click Strip Invisible Characters — it removes every Object Replacement Character (and any other hidden characters) in one pass, locally in your browser.

In code, match it by its code point:

// JavaScript: detect and removetext.includes('')          // true if presenttext.replace(//g, '')      // remove all

# Pythontext = text.replace('', '')

Technical Details

The Object Replacement Character is classified as Symbol, Other (So) and lives in the Specials block, alongside the better-known Replacement Character. It is a real character in the text stream, not a rendering glitch: it occupies one code point, survives copy-paste and storage, and is preserved by most text-processing systems.

 vs � — Two Different "Mystery" Characters

These two are constantly confused because both look broken, but they mean opposite things:

If you see a box, it is usually U+FFFC (a dropped image). If you see a black diamond with a question mark (�), it is usually U+FFFD (an encoding problem).

Why It Matters

Because it is invisible-ish and survives copy-paste, the Object Replacement Character can quietly cause problems:

• Form validation. A  pasted into a name or email field can fail validation in confusing ways, or pass and corrupt your data.
• Search and matching. Stored text containing U+FFFC will not match a clean search query, so records can silently "disappear."
• String length. It counts as a character, so length checks and truncation behave unexpectedly.
• Code and config. Pasted into a config file, script, or commit message, it can break parsing with no obvious cause.

When in doubt, run the text through the viewer on the homepage to reveal and strip it.