Google Messages encrypts some conversations end to end and leaves others as plain SMS. The difference is visible in the app, and you can check it in under a minute before sending anything sensitive.
Gather what you need before you start
You need an Android phone with Google Messages installed and set as the default messaging app, a working mobile data or Wi-Fi connection, and the person you are messaging on the other end. Encryption in this app depends on both sides, so you cannot verify it alone.
Google Trends recorded rising United States search interest in Google Messages; that signal carries no detail about why, and no specific incident is attached to it. Treat what follows as a check you can run at any time rather than a response to a known event.
Google’s support documentation is the reference point for how the app behaves. Features arrive at different times on different devices and carriers, so a setting described here may sit in a slightly different place on your handset, or may not be present at all. If you cannot find something, the version you are running may not have it yet.
Confirm you are using RCS, not SMS
Google Messages carries two different kinds of message. SMS and MMS are the old carrier text formats. They travel through the mobile network in a form your carrier can read, and they are not end-to-end encrypted. RCS, the newer standard maintained by the mobile industry body GSMA, travels over the internet and supports typing indicators, read receipts and larger attachments.
End-to-end encryption in Google Messages applies to RCS chats, not to SMS or MMS. So the first check is which one is in use. In the app’s settings there is an RCS chats section that shows the current status of the service for your number, including whether it is connected. If RCS is switched off or cannot connect, every message you send falls back to SMS, and encryption is not in play at all.
Look for the lock icon before you send
The practical, per-conversation signal is a small padlock. When a chat is end-to-end encrypted, Google Messages shows a lock on the send button, and encrypted messages carry a lock beside their timestamp in the thread. The absence of that lock is the useful information: it means the message is going out unencrypted, usually as SMS.
Check it in the conversation itself rather than assuming, because a single thread can contain both kinds of message. If the other person loses connectivity, or their device drops off RCS, later messages in the same thread may revert to SMS while the earlier encrypted ones stay where they are. The lock reflects the message you are about to send, not the history above it.
Google Messages also offers a verification code that both people can compare to confirm they are in the same encrypted conversation. Comparing those codes over a separate channel — in person, or on a call — is the step that guards against an impostor rather than an eavesdropper.
Switch on the protections that filter what arrives
Two of the app’s defences concern incoming messages rather than outgoing ones. Spam protection, which Google describes in its support material, screens messages it judges likely to be unwanted and can move them out of the main inbox. It is a filter, not a guarantee, and it works on signals about the message rather than a human review.
Google has also introduced warnings for sensitive content, an on-device check that blurs images it identifies as containing nudity and asks before they are opened or sent. Google states this analysis happens on the device. Availability and default state vary by region, account type and device, and parental controls can affect it on accounts managed for children. Both features live in the app’s protection or privacy settings, where you can see whether they are active.
Secure the device and the backups around it
Encryption protects a message in transit between two devices. It does nothing for a message sitting unlocked on a handset someone else is holding. A screen lock, an up-to-date Android version and a short auto-lock timeout do more for most people’s real exposure than anything inside the messaging app.
Backups deserve a separate thought. Messages may be copied into a backup depending on your device and settings, and a copy stored elsewhere is governed by that service’s protections, not by the end-to-end encryption of the original chat. Check what your phone backs up before you assume a conversation exists only on two devices. The same applies to any linked or paired surface where messages are mirrored: each additional place a message appears is another place it can be read.
Report and block what gets through the filters
When an unwanted message arrives, the app offers blocking and reporting from the conversation. Reporting sends information about the message to Google and, in some cases, to your carrier; blocking stops that sender reaching you again. Neither undoes a message already received.
For anything claiming to come from a bank, a delivery company or a government service, do not use links or numbers in the message. Contact the organisation through a channel you already have. Message content is a poor authenticator, and a convincing sender name is trivially faked over SMS.
Avoid the mistakes people actually make
The most common error is treating the app as uniformly encrypted. It is not: the same inbox holds encrypted RCS chats and unencrypted SMS side by side, and nothing prevents a sensitive message going out on the wrong one.
The second is assuming group chats behave like one-to-one chats. Encryption support has been extended over time and depends on every participant’s app and service status; one participant without RCS is enough to change how the conversation is carried.
The third is expecting encryption across platforms. RCS is now supported outside Android, but the industry specification’s work on cross-platform end-to-end encryption has been a later addition, and support depends on what each side is running. Do not assume an Android-to-iPhone RCS chat is end-to-end encrypted because a chat between two Android phones was.
The fourth is confusing transport security with confidentiality. Metadata about who messaged whom and when is not the same thing as message content, and end-to-end encryption is not designed to hide it.
Recognise when this is the wrong approach
If your threat model involves a capable adversary — targeted surveillance, a legal dispute where messages may be compelled, or work covered by a confidentiality obligation — a default phone messaging app is the wrong tool. A dedicated encrypted messenger where encryption is unconditional, rather than dependent on carrier provisioning and per-chat fallback, removes the failure mode where a message silently downgrades.
It is also the wrong approach when you cannot control both ends. Nothing you configure changes what the other person’s device does with the message once it arrives: screenshots, cloud backups and an unlocked screen are outside the encryption boundary entirely.
Finally, if the concern is regulatory record-keeping rather than secrecy, consumer messaging apps are a poor fit in either direction. Organisations with retention duties generally need a channel built for logging, which is the opposite of what end-to-end encryption provides.
Frequently asked questions
Does Google Messages encrypt all my texts?
No. End-to-end encryption in Google Messages applies to RCS chats, not to SMS or MMS. Because the app handles both, a single inbox can contain encrypted and unencrypted conversations at the same time. The reliable indicator is a padlock on the send button and beside message timestamps in an encrypted thread. If there is no lock, the message is going out unencrypted.
How do I tell whether RCS is working on my phone?
Open the settings inside Google Messages and find the RCS chats section, which shows the current status of the service for your number and whether it has connected. If RCS is disabled or stuck, messages fall back to SMS. Availability can depend on your carrier, device and region, so a failure to connect is not necessarily something you can fix from the app.
Are RCS messages between Android and iPhone end-to-end encrypted?
Do not assume so. RCS support beyond Android arrived later than the encryption Google built for Android-to-Android chats, and end-to-end encryption across platforms depends on the specification version and the software both sides are running. The padlock in the conversation is the check that matters; if it is absent, treat the chat as unencrypted regardless of what devices are involved.
What does spam protection in Google Messages actually do?
It screens incoming messages and can divert those it judges likely to be unwanted, keeping them out of the main inbox. Google describes it as a filter in its support documentation, and filters produce both misses and false positives. It does not verify that a sender is who they claim to be, so a message that arrives in your inbox has not been confirmed as genuine by anything.
Sources and further reading
- Google’s official support documentation for the Messages app, covering RCS chats, end-to-end encryption indicators and spam protection settings.
- Published specifications and technical material from the GSMA, the industry body that maintains the RCS Universal Profile.
- Public technical documentation on the Signal Protocol, the basis for several widely deployed end-to-end encryption implementations.
- Consumer guidance from national data protection and cybersecurity authorities on message-based fraud and device security.
Surfaced from the google:US signal “interest in a messaging app”. AI-assisted draft, editorially reviewed.
