A thumbs-up under “Extra $1,800 for the wall, OK to proceed?” A crying-laughing face after a harsh line. A knife or a skull at the end of a late-night text. In a growing share of message evidence, the disputed content is not a sentence but a small picture, and the exhibit has to show that picture accurately before anyone can argue about it.

This guide is for paralegals and attorneys who handle message exhibits. It covers why emojis matter, why the same emoji looks different across phones, how reactions and Tapbacks show up in exports, how to build a neutral exhibit with an emoji legend, and the discovery and transcription details that trip teams up. It is general information; check your jurisdiction’s rules and the court’s standing orders.

Why do emojis matter in message evidence?

Emojis matter because they often carry the tone, intent or assent that the words alone do not. The same sentence reads differently with a winking face, a heart or a weapon after it, and a lone thumbs-up may be the only response to a proposal. Common situations include:

  • Agreement. A thumbs-up or a heart reaction to a proposed schedule, price or contract term.
  • Tone. A laughing face after an insult, offered to show a joke, or a pointed absence of one.
  • Threats and intimidation. Weapons, fire or skulls alongside words, offered to show intent or fear.
  • Receipt and acknowledgment. A reaction offered to show that someone saw a message on a given date.

An emoji does not get its own evidence rules. It is part of the message, so it is authenticated, tested for relevance and analyzed for hearsay with everything else; see our guides on authenticating text messages under Rule 901 and hearsay and text messages. What emojis add is a presentation problem.

Does the same emoji look the same on every phone?

No. An emoji is a Unicode character: a code point with a standard name. Each platform vendor draws its own picture for that character. The Unicode Consortium’s emoji FAQ says it has no control over the images vendors use or how emoji appear on their platforms, and its charts show only a representative glyph.

Designs also change over time. Emojipedia’s history of the pistol emoji shows a character that was commonly drawn as a handgun until Apple switched to a toy design in 2016, with other major vendors following by 2018. Its Unicode character name is still PISTOL, while its current short name is “water pistol.” A message sent years ago and viewed on a new phone today may not look like what either party saw at the time.

Two more wrinkles matter in practice:

  • Sequences. Many emoji are sequences of several code points, such as a thumbs-up with a skin-tone modifier. An older device may show them as two separate images or as an empty box.
  • Faces. Facial expressions vary the most between vendors, which is exactly where tone disputes arise.

The working question for an exhibit is therefore not “what does this look like on my screen?” but “what did the sender send, and what did the recipient see?”

What should you record about a disputed emoji?

Record the character itself, not your interpretation of it. Unicode’s full emoji list gives each emoji’s code point and CLDR short name, which together identify it unambiguously.

FieldExampleWhy it helps
As rendered👍 (image from the export or device)Shows the picture the exhibit relies on
Code point(s)U+1F44DIdentifies the character regardless of artwork
Short namethumbs upA neutral, standard label for testimony and briefs
Devices and versionsSender: iPhone; recipient: Android (as known)Explains why two versions of the thread look different
LocationBates page and message timeLets the court find it in the exhibit

How should emojis appear in a message exhibit?

Keep the native rendering, add a legend for anything disputed, and keep your own words out of the message text. A practical sequence:

  1. Work from an export, not only screenshots. A structured export preserves the actual characters, so the code points survive. See our guide to exporting iMessages for litigation.
  2. Proof the rendered PDF. Make sure the printed or projected exhibit shows emoji, not empty boxes or question marks, and compare it to the source.
  3. Add an emoji legend. For each disputed emoji, list the image as rendered, the code point and the short name, with the Bates page where it appears.
  4. Show the other side’s view when it matters. If what the recipient saw is at issue, a screenshot from the recipient’s device, identified by device and date captured, can sit alongside the log.
  5. Never translate in the message text. No “[laughing]” or “[threat]” inserted into a message. If a bracketed note is needed, use the standard name, for example “[U+1F602 face with tears of joy].”

Our guide to text message exhibit formatting covers the rest of the layout: header block, time zones, attachments and numbering.

How do reactions and Tapbacks show up in exports?

Inconsistently, which is why they need a line in the legend. On iPhone, Apple’s guide to Tapbacks describes reactions that include a heart, thumbs-up or thumbs-down, laughter, exclamation points, a question mark and any emoji, Memoji or sticker. A Tapback is attached to a specific message, only one per person per message, and the person who added it can change or remove it later.

Across platforms, the same reaction may arrive differently. Google’s help page on expressive features in Google Messages describes a “Show iPhone reactions as emoji” setting; with it off, iPhone reactions arrive as texts instead. Apple also distinguishes iMessage, RCS and SMS/MMS conversations, and how reactions travel has changed as iPhone and Android messaging has moved to RCS. Confirm current behavior with test messages rather than relying on how it worked last year.

For exhibits, that means:

  • Keep a reaction exactly as the export recorded it, whether as an icon or a separate “Liked …” line
  • Do not count reaction lines as messages when someone summarizes message volume
  • Note that a reaction seen in an old screenshot may since have been changed or removed
  • Explain in the legend when two parties’ exports show the same reaction in different formats

Example

A paralegal at a small firm represents Rivera Stoneworks (a fictional contractor) in a payment dispute with Linden Court Property Management (also fictional). The client says the manager approved a change order on March 4, 2026 by reacting with a thumbs-up to “Extra $1,800 for the retaining wall, OK to proceed?”

The manager’s production, exported from an iPhone, shows the thumbs-up attached to that message. The client’s Android export shows a separate line at the same minute: Liked “Extra $1,800 for the retaining wall, OK to proceed?” The team produces both exports, adds a legend entry identifying the reaction as U+1F44D thumbs up and explaining that both lines record the same event, and describes the exhibit as “Text messages between A. Rivera and Linden Court Property Management, March 2–6, 2026.” Whether the reaction amounted to approval is left for argument.

What discovery and transcription issues come up with emojis?

Most emoji problems are preventable at the request and collection stage.

  • Requests. Define “message” to include emoji, reactions, stickers and attachments, and ask for exports that preserve reactions and timestamps. Our guide to producing text messages in discovery covers form of production.
  • Encoding. Some conversions, especially through spreadsheets, garble emoji. Spot-check every converted file against the source before review begins.
  • Searching. Search for the emoji character, and include variants. Unicode lists the plain thumbs-up and five skin-tone versions as separate sequences, so one search term can miss most of them.
  • Depositions and hearings. A transcript may not reproduce an emoji. When a witness discusses one, identify it on the record by exhibit page and legend entry, such as “the emoji identified in the legend as U+1F602 face with tears of joy.”
  • Other languages. Emoji use varies across cultures and communities. If a thread is in another language, ask the translator to flag emoji whose use in that community may be unfamiliar to the court.

Who decides what an emoji meant?

The fact-finder decides, based on the evidence of context. The litigation team’s job is to present the emoji accurately and gather that context, not to settle the meaning in an exhibit description. Useful context includes:

  • The messages immediately before and after the emoji
  • How the same person used the same emoji elsewhere in the thread
  • What each participant’s device showed, if that is known
  • Later conduct consistent or inconsistent with a reading, such as work starting the next day
  • Testimony from the sender and recipient about what they meant and understood

Be careful with popular emoji dictionaries and websites. They describe common usage, which may not match how these particular people used a symbol, and whether to offer evidence of general usage, and through whom, is a strategy call for the attorney. Keep the record clean so that whatever argument is made rests on an accurate exhibit.

How CourtBriefly helps

When an emoji sits in a long thread, it needs a page number before anyone can cite it. Message Extractor ingests the client’s exports from sources such as iMazing, SMS Backup & Restore, WhatsApp, Facebook, Instagram, Google Voice and email, merges duplicates into one thread model and produces a paginated, Bates-stamped, fingerprinted PDF log with an index and a source manifest. Your team adds the emoji legend and makes the judgment calls; the log gives every entry a stable place to point to.

Start freeFree plan, no card