Why "Liked a photo" Arrives as a Separate Text Message

What a reaction actually is

When you double-tap a message and pick a heart, you are not sending a message. You are sending an instruction: attach this symbol to that earlier message. The receiving app finds the message you pointed at and draws the symbol on it.

That instruction needs somewhere to live. It needs a way to identify which earlier message you meant, and a way to carry the symbol as data rather than as text. Modern protocols have both. SMS and MMS have neither — they can carry a message and nothing else. There is no field for “this refers to that”.

So your phone does the only thing left. It writes a sentence describing what you did — “Liked a photo”, “Loved ‘see you at 8’”, “Emphasised an image” — and sends that sentence as an ordinary text message. From the receiving end it is indistinguishable from you having typed those words, because that is exactly what arrived.

Where it works and where it does not

Two iPhones on iMessage: reactions attach properly. This is the behaviour everyone is used to and the reason the fallback feels like a malfunction.

Two Android phones on RCS: reactions attach properly.

An iPhone and an Android phone on RCS: this is the interesting case, and the one that has changed recently. Reactions are believed to attach properly here rather than arriving as text, which was not true in the earliest releases of RCS support on the iPhone.

We are being careful with that paragraph on purpose. This specific behaviour changed at some point, we have not confirmed exactly when against Apple’s documentation, and getting it wrong would mean telling you your reactions are fine when your friends are being spammed. Our checker marks this row as unverified for the same reason. If you want certainty rather than a probability: react to something and ask the person what they saw.

Anything on SMS or MMS: reactions become sentences. Always. There is no version of this that works.

Why it is so much worse in groups

In a one-to-one chat, a stray “Liked a photo” is mildly annoying. In a group of eight it is a small disaster, and it is worth understanding why the maths is so bad.

Each reaction becomes a message, and each message goes to every participant. So one person reacting to one photo produces a notification for everybody. If four people react to the same photo, that is four messages each. If people then react to the reactions — which happens — it compounds.

And because one non-RCS participant drops the entire group to MMS, this is the default state of a lot of mixed groups. Everyone is reacting normally on their own phone, and the group is filling up with sentences.

The group case has a second irritation: the descriptions quote the message being reacted to. So a long message gets partially reproduced inside every reaction to it, and the thread becomes hard to read as well as noisy.

How to stop sending them

There is no universal switch labelled “stop sending reactions as text”, but there are three practical approaches.

Turn the fallback off, if your phone offers it. Some versions of iOS have a setting that stops Tapbacks being sent as text to people who cannot receive them properly. If your phone has it, this is the clean solution: the reaction simply does not go rather than going as a sentence. You still see it on your side.

Just reply instead. If you would have hearted it, type “love it”. This is not a workaround so much as an acknowledgement that in an MMS conversation, a reaction was always going to become words — you may as well pick better words. One message either way.

Get the conversation onto RCS. The durable fix. It solves this alongside the photo quality and the group behaviour, because they are all the same underlying problem.

How to stop receiving them

Harder, because the sending decision is not yours.

You cannot filter them out reliably — they are ordinary text messages with no marker identifying them as reactions, so nothing can distinguish “Liked a photo” from someone typing that phrase. Some third-party messaging apps attempt to detect and collapse the pattern, with mixed results.

Which leaves the social option: tell the person. Most people have no idea this is happening, because on their screen the reaction looks perfectly normal. The sender sees a heart on a photo; you see a sentence. Neither of you can see the other’s view. A single “hey, your reactions arrive as separate texts on my end” usually solves it permanently, and it is the fastest fix available.

The bit that surprises people

If you are on an iPhone and this is happening, your instinct is that the Android phone is at fault, because your side looks fine. It is not. Your phone made the decision to convert the reaction to text, because your phone is the one that knows the conversation cannot carry it.

The reverse is also true — Android reactions arriving on an iPhone as text are the Android phone making the same call. Whoever is sending is the one converting, and it is a sensible fallback rather than a bug. A reaction that silently vanished would be worse than one that arrives clumsily.

The real fault, if it is anywhere, is in the twenty-year-old protocol that has no way to say “this refers to that”. Everything in this guide follows from that one absence.

Version facts on this page: not verified yet — the site-wide verification pass has not been completed. See the update log

Related guides

• Do Read Receipts Work Between iPhone and Android?
• Why Group Chats Break When Someone Has a Different Phone
• Why Your Photos Look Blurry When You Send Them to Android
• The full feature-by-feature comparison

Published 1 September 2026. Last reviewed 1 September 2026. This guide depends on facts F4, F1, F22 in our verification table — if one of those changes, this page gets rewritten and the change is logged in the update log.