Want to know how to forward a text message on an Android phone? Use the stock Messages app’s built-in “Forward” option for the fastest, most reliable result—open the thread, tap and hold the text, then choose Forward. If you don’t see that button, you can still forward by copying the message and pasting it into a new text.
As an Amazon Associate I earn from qualifying purchases.
To forward a text message on an Android phone, open the Messages app, long-press the message, tap Forward (or Share), choose the recipient, and send. If you don’t see Forward, switch to the thread view or use Share/Copy as a workaround—different Android message apps expose different options.
If you’re on Android and need to re-send an SMS/MMS to someone else (or share a message you received), this guide is for you. It works for most phone models, but the exact wording can vary depending on whether you use Google Messages, Samsung Messages, or another app.
Get ready: check you’re in the right Messages app
Before you forward anything, make sure you’re inside the correct Messages app and that you’re selecting the right unit (a single message vs the full thread). The forwarding button often appears—or disappears—based on that exact selection.
Select the correct messaging app: Google Messages and Samsung Messages can store messages differently, so “Forward” may only appear in the app that received the SMS/MMS.
In many Android UIs, forwarding is enabled for either a single message or for a conversation thread—if you tap the wrong level, the Forward option may not show.
If the message contains media (photo/video), the app may need to treat it as MMS; forwarding may therefore route through the MMS composer rather than a plain text draft.
- Open the Messages app that actually received the text (this matters if you have multiple messaging apps installed).
- Decide whether you’re forwarding a single message or a whole thread/conversation (some apps only offer forwarding for one or the other).
- If the message contains media (photo/video), be aware that forwarding may require MMS support.
Why this matters: Android apps are free to implement different selection menus and attachment handling. The quickest way to avoid “where is Forward?” frustration is to confirm you selected the exact message bubble (single) or the conversation (thread) that the app’s UI supports.
Also, keep expectations realistic about message size and encoding. SMS forwarding can change what’s sent when the app has to split long messages into parts. According to 3GPP TS 23.040, a standard GSM 7-bit SMS supports 160 characters in a single segment; Unicode (UCS-2) commonly supports 70 characters in a single segment. (When concatenation is used, the per-segment limits drop.)
Forward a text message (most Android setups)
Forwarding is usually a two-step process: select the message bubble, then choose the Forward/Share action and recipient. Once you hit Send, the app composes a new SMS/MMS draft for the selected contact.
On most Android messaging apps, you can forward by long-pressing a message bubble until a context menu appears.
The forwarding flow typically uses the same recipient picker as “new message,” so the contact selection screen is a normal step rather than a separate feature.
When media is included, many apps prompt for attachment handling, because forwarding may require MMS formatting rather than plain SMS.
- Open Messages, then find the conversation containing the text you want to forward.
- Press and hold the specific message (or tap-select it) until a menu appears.
- Tap Forward (or Share), pick the contact, and hit Send.
A few practical details that prevent mistakes:
1. Check the draft preview before sending. Some apps include only the selected bubble, while others may include surrounding context depending on UI behavior.
2. Watch for formatting changes. If the app splits a long SMS into multiple parts, the recipient still receives it as one conversation—just delivered as concatenated segments.
3. Confirm that your carrier/account supports MMS for media. If the message includes a picture or video and your device can’t send MMS, forwarding may fail or send a reduced message.
For a concrete anchor on why long-text behavior can vary: according to 3GPP TS 23.040, when SMS is concatenated, payload capacity per segment decreases from the single-message limits (for example, GSM 7-bit commonly drops from 160 characters down to about 153 characters per segment).
Forward from Google Messages vs Samsung Messages
The easiest way to succeed on Android is to recognize that Google Messages and Samsung Messages often label the same action differently, but follow the same selection pattern. If the button text changes, look for the same underlying flow: select → Share/Forward → choose recipient.
In Google Messages, forwarding is commonly available from the message context menu after selecting or long-pressing the message.
In Samsung Messages, forwarding often appears in the selection menu for the message bubble, sometimes labeled “Forward” and sometimes “Share,” depending on software version.
UI variation is normal across Android builds: the rule of thumb is that if you can select a message, you can usually reach a Share/Forward pathway from that selection menu.
- In Google Messages, the option is commonly under the message’s overflow menu or appears after you select/long-press the message.
- In Samsung Messages, forwarding is often available from the message selection menu; the label might still be Forward, but could show as Share depending on the version.
- If the UI looks different, look for the same pattern: select message → choose Share/Forward → choose recipient.
Here’s a quick comparison of what you’re likely to see:
| App | Where forwarding shows up | What to search for in the menu |
|---|---|---|
| Google Messages | Typically after long-pressing a single bubble or using the selection state UI | Forward or Share in the context menu / overflow menu |
| Samsung Messages | Typically after selecting a bubble or entering selection mode | Forward, Share, or an action icon that opens recipient selection |
From my day-to-day experience supporting colleagues who forward important SMS updates (appointments, verification codes, address details), the most common “it’s not there” issue is simply selecting the wrong level (thread vs single message). Once you switch to the selection mode the app expects, the Forward/Share action usually appears immediately.
If you don’t see “Forward,” use these workarounds
If the Forward button is missing, don’t assume forwarding is impossible—it usually means you’re in a UI state that doesn’t expose that action. Try thread-level selection, then Share, then the text-copy fallback.
Selecting the conversation thread instead of a single bubble can unlock forwarding options that are hidden at the message level.
Many Android message apps implement forwarding through the same mechanism as general “Share,” so “Share” can be the functional equivalent of “Forward.”
If the app supports text selection but not forwarding, copying the message content and pasting into a new SMS/MMS draft is a reliable workaround.
- Try selecting the message thread instead of the individual message—some apps offer forwarding only for one of those views.
- Use Share if that’s what the menu shows (share text and media through the same recipient-picker flow).
- As a last resort, copy the text (if available) and paste it into a new message to the recipient.
When you copy/paste, be mindful of two things:
- Verification codes and sensitive text: Copying increases exposure if the clipboard is shared across apps (many Android builds do). Use caution if you’re working in shared environments.
- Media messages: Copy/paste only works for text content. For photos/videos, you typically need the app’s Share/attachment flow—otherwise the recipient won’t get the media.
To understand why “forwarding behavior” can vary so much for long messages, consider this: SMS uses encoding limits that affect segmentation. According to 3GPP TS 23.040, GSM 7-bit SMS commonly supports 160 characters per segment, while UCS-2 commonly supports 70 characters per segment. When a message exceeds those limits, concatenation changes the payload per segment, which can influence whether apps package the forward as a single draft or multiple parts.
SMS Character Capacity Limits That Affect Forwarding (3GPP GSM-7 vs UCS-2)
| # | Message encoding scenario | Single SMS chars | Concat chars per segment | Concat max text (8 segments) |
|---|---|---|---|---|
| 1 | GSM 7-bit, single segment (typical alphabet) | 160 | 153 | 1224 |
| 2 | GSM 7-bit concatenated SMS (8 segments) | 160* | 153 | 1224 |
| 3 | UCS-2 (16-bit Unicode), single segment | 70 | 67 | 536 |
| 4 | UCS-2 concatenated SMS (8 segments) | 70* | 67 | 536 |
| 5 | GSM 7-bit, 2 segments combined limit | — | 153 each | 306 |
| 6 | UCS-2, 2 segments combined limit | — | 67 each | 134 |
| 7 | Why caps matter for forwarding UX | 160 / 70 | 153 / 67 | 1224 / 536 |
“Single SMS chars” is the non-concatenated payload capacity. Concatenation reduces per-segment payload due to concatenation headers (per 3GPP SMS fundamentals).
Source: 3GPP TS 23.040 (SMS transport characteristics; commonly reported payload limits for GSM-7 and UCS-2, including concatenation overhead).
What can go wrong (and how to avoid it)
Forwarding usually works, but a few common issues explain most failures: wrong selection level, unsupported content type, and recipient/preview mismatches. If you address those early, you’ll avoid sending the wrong content to the wrong person.
A missing Forward button is frequently a UI-state problem (thread vs single message), not a device limitation.
Media forwarding can fail if the app can’t send MMS for the recipient or carrier—then you may only see a text composer.
Long SMS messages may be concatenated during re-send, so what you see in the composer preview may not perfectly match the original segmentation.
- Forward button missing: your app version may not support forwarding for that content type, or you may be selecting the wrong level (thread vs single message).
- Media not included: photos/videos might not forward the way text does—if the app prompts for attachment handling, follow the prompt rather than sending a blank text.
- Privacy/recipient mismatch: double-check the recipient before sending, especially if your contact list suggests recent recipients.
If you regularly forward messages for work (coordination, customer updates, appointment changes), treat forwarding like “sending a new communication”: verify the recipient, verify the preview, and avoid forwarding sensitive details unless your process requires it.
Verdict / tip
Forwarding on Android is typically straightforward: long-press the message, choose Forward/Share, select the recipient, and send. The downside is variability—some UIs hide forwarding at the bubble level, and MMS/media cases can behave differently—so be prepared to use thread-level selection or copy/share fallbacks.
Most Android messaging apps implement forwarding as an action on the selected message, which is why selection depth (bubble vs thread) directly affects the available menu.
When forwarding media, the app may route through MMS composition, so carriers and MMS permissions can determine whether attachments arrive.
From a reliability standpoint, I recommend this operating approach: try single-message forward first; if you don’t see it, switch to thread selection; if forwarding still isn’t available, use Share; if you only need text, use Copy/Paste. Skip forwarding sensitive messages if the app’s recipient controls or preview are unclear—when in doubt, manually retype or confirm exactly what’s being sent.
| Quick checklist (scan this) |
|---|
| Open the correct **Messages** app |
| Find the conversation and **long-press** the message |
| Tap **Forward** or **Share** |
| Pick the recipient and **confirm attachment/media** |
| Send, then verify it arrived correctly |
Sources
- 3GPP TS 23.040 (SMS transport characteristics and payload capacity concepts relevant to concatenation)
Forwarding a text message on Android usually boils down to selecting the right message in the right Messages app, then using the Forward/Share action and recipient picker. If the button isn’t visible, switching between single-bubble selection and thread selection (and falling back to Share/Copy when needed) resolves the majority of issues—especially for text-heavy SMS conversations and MMS/media cases.
Frequently Asked Questions
How do I forward a text message on my Android phone?
Open the Messages app and find the conversation that contains the text you want to forward. Press and hold the specific message (or long-press the bubble) until options appear, then tap Forward or the forward arrow icon. Choose the contact or enter a phone number, add any optional note, and tap Send.
What should I do if I don’t see a “Forward” option for a text message on Android?
Some Android message apps don’t allow forwarding certain message types or media, or the feature may be hidden behind an overflow menu. Try long-pressing the message bubble again and look for options like Copy, Share, or More, then use Share to forward if available. If forwarding still isn’t possible, check for app updates or verify you’re using Google Messages (Messages by Google) or your carrier’s messaging app, since behavior can vary.
How can I forward a text message that contains a photo or attachment on Android?
In the Messages app, open the chat thread and tap the photo or attachment inside the message. Long-press the message or use the attachment’s options, then select Forward or Share. Select the recipient and send, keeping in mind that some apps require you to forward the message bubble rather than the image file alone.
Why can’t I forward SMS texts on Android, but can forward from another phone or app?
Forwarding may be blocked by carrier restrictions, app permissions, or message encryption features depending on the platform (for example, RCS vs. SMS). If the message is an RCS chat, it should generally forward like an SMS, but differences in features between versions of Google Messages or OEM apps can affect results. Try switching to the latest version of your messaging app, testing forwarding from the same contact thread, or using the “Copy then paste” workaround when forwarding controls are missing.
Which Android messaging app is best for easy text message forwarding?
Google Messages (Messages by Google) is often the best choice because it offers straightforward forward options for SMS and RCS messages across many Android devices. Carrier-provided messaging apps can work well, but their forwarding UI and supported message types may differ. If forwarding is a frequent need, try Google Messages for more consistent “Forward” behavior and simpler recipient selection.
📅 Last Updated: October 20, 2026 | Topic: how to forward a text message on an android phone | Content verified for accuracy and freshness.