My WhatsApp export shows squares instead of emojis
The squares are not damage. Every emoji is still in the file, intact — what you are seeing is the program reading it either decoding the bytes wrongly or lacking a font that can draw them. Two different failures, same symptom, and each has a different fix. Open the file as UTF-8 in something with a colour-emoji font and the hearts come back.
Which squares do you have?
| What you see | What actually happened | The fix |
|---|---|---|
| □ □ hollow squares (tofu) | The text decoded fine; the font on show has no glyph for those emoji. | Open the file in an app with an emoji font — a browser, or any modern editor set to one. |
| ? ? or â½ð characters | Wrong encoding entirely: the reader guessed a legacy codepage instead of UTF-8. | Reopen with encoding set to UTF-8 (Notepad: Save/Open dialog; Word: reopen with encoding). |
| Fine on screen, squares on paper | The printer’s fonts, not yours, did the rendering. | Print from a browser or a PDF with the font embedded, not from a raw text app. |
Why a .txt loses what the app shows perfectly
WhatsApp draws its own emoji itself, so it never needs your system font. The export writes the same emoji as their standard Unicode characters — 💛 is one code point, U+1F49B — and from that moment their survival depends on whatever opens the file next. Windows Notepad for years had no colour-emoji font to hand; some printers render text with resident fonts from 1998. Nothing about your chat degraded. To print the chat looking like the chat, the renderer has to embed an emoji font in the output — which is why screenshots and browser printing muddle through and raw text printouts don’t.
If you're making something keepable
This is the quiet difference between a transcript and a rendered conversation: the render carries its own fonts, so the emoji that survived the export survive the printer. In the studio here the whole chain — parse, typeset, PDF — keeps emoji as typed, including the ones Android and iPhone draw differently from each other (you get whichever flavour the sender’s phone wrote, which is the truthful version).
Questions people actually ask
Are the emoji gone from my chat?
No. Both the chat on your phone and the export file still contain them — this is purely a display problem in whatever opened the file. Fix the reading side; nothing needs re-exporting.
Why do my emoji look different from the other person's?
Android and iOS draw the same Unicode emoji differently — Google's and Apple's artwork. An export keeps whichever the sender's phone used, so a mixed conversation is a mixed book. That's fidelity, not a fault.
Will emoji print correctly from Word?
Usually, yes — modern Word embeds the emoji font when it makes a PDF. Printing straight from Word to paper depends on the printer's fonts, so make the PDF first and print that.
What about the emoji my printer simply drops?
That's the tofu case wearing a different coat: the glyph exists, the printer's font table doesn't. Same fix — render to PDF with fonts embedded (a browser's Print-to-PDF does this) before the paper stage.
Emoji, kept.
Render the chat — freeThis is one of the guides — or see everything we’ve written.