How to Decode a Passive-Aggressive Text (And What to Say Back)

You got a message. On the surface it seems fine. But something's off — a word choice, a punctuation choice, a shift in tone from how they usually write. You've read it six times. You're not sure if you're being sensitive or if you're reading it correctly. Here's how to figure it out — and what to do either way.

The signals that something is actually there

Not every short reply is loaded. Not every period is a signal. But there are genuine tells that a message carries more than its surface content. Relationship researcher John Gottman, whose work at the Gottman Institute identified passive aggression as one of the strongest predictors of communication breakdown in relationships, describes it as "hostility that dresses itself in politeness" — a way of expressing something without taking responsibility for having expressed it. Once you know what it looks like structurally, it's much easier to spot:

The formal shift. Someone who normally texts in lowercase suddenly capitalizes everything. Someone who uses your name warmly now uses it at the start of a sentence like a teacher about to correct you. Formality in a usually-casual context is almost always doing something.

The acknowledged-but-not-addressed close. "Anyway, hope you're well." or "No worries!" when there are clearly worries. Overly bright sign-offs on a message that was pointedly brief often signal the opposite of what they literally say.

The question that isn't a question. "I mean, it's fine, I just thought you said you'd be there?" is not asking for information. It's making a point.

Some common examples — decoded

When you're not sure if it's loaded

Before you decide the message is passive-aggressive, apply the charitable read: is there a version of this where they just have a dry texting style, they were distracted, or their last message was typed one-handed while doing something else? If the charitable read is genuinely plausible, that's your default. Respond to the surface content.

The mistake is pre-emptively managing a subtext that might not be there. If you respond to a potentially-loaded message by trying to address the subtext, you've introduced the conflict. If the subtext was real, they'll clarify. If it wasn't, you'll have created something out of nothing.

When it's definitely there: how to reply

The best reply to an actually passive-aggressive message is one that names it calmly, without escalating. You're not calling them out — you're opening a door. "This feels a little loaded — did I do something?" is a complete response. It's direct without being accusatory, and it gives them space to either confirm or deny.

What doesn't work: mirroring the passive-aggression back. Two people having a conversation in subtext is exhausting and never resolves the actual issue.