RCS messages don't always render the same way on iPhone as they do on Android, especially on iOS, where Apple's RCS implementation is still maturing. This guide walks you through the most important differences so you know what to expect when designing RCS messages and have a reference if something looks "off" on iPhone.
Note: This article reflects RCS behavior as of iOS 26.2. Apple's RCS support is evolving, so individual quirks may change over time. When in doubt, send yourself a preview on both an iPhone and an Android device before sending your message.
Why iOS and Android RCS Look Different
RCS messages are rendered by the native Messages app on each operating system and Apple and Google have made different design choices about how to display the same content. The result is that the message you send is identical, but layout, button placement, and interactive elements can look noticeably different on each device.
None of these differences mean RCS is broken on iOS, but they're rendering choices baked into the operating system, and most can be designed around once you know they exist.
iOS vs. Android at a Glance
Behavior | iOS | Android |
GIF animation in Rich Cards | Static image only | Animated |
Carousel card sizing | Varies with media and text length | Uniform (media center-cropped) |
Message-level suggested actions (chips below a message) | Persistent; placed above any replies; collapsed under an "Options" dropdown when there are more than two | Transient chips (disappear once a new message is received) |
Message-level suggested replies (chips below a message) | Persistent list (until subscriber interacts) | Transient chips (disappear once a new message is received) |
Rich Card buttons | Grey color, lower visual prominence; multiple buttons collapse into a dropdown | Full color, displayed inline |
Rich Card text overflow (>6 lines total) | Card becomes tappable; opens full-text view (media and suggestions hidden) | Full-text view includes media and suggestions |
Sender name/branding | Agent ID may display instead of agent name; banners may not render | Displays consistently |
iOS Behavior Summary
Note: These iOS behaviors are dictated by Apple's RCS implementation at the operating system level. Postscript, Google, and carriers can't override or patch them. Specific behaviors may also vary by iOS version, device model, and carrier.
Hyperlinks and Link Previews Are Picky
iOS treats hyperlinks differently depending on where they sit in your message:
If a URL is the last element with no trailing text, iOS may render it as a separate "tap to preview" bubble subscribers have to take an extra tap before they see the preview card.
If the URL is followed by text, iOS won't render a preview card at all. The link will appear as raw text.
Android renders previews regardless of position.
A few rules that make link previews more reliable on iOS:
Use one hyperlink per message.
Start the URL with https://.
Place the link as the last element in the message.
Add a period or other punctuation immediately after the URL to keep the preview inline instead of triggering the separate "tap to preview" bubble.
Make sure the destination page has an og:image meta tag. Without it, iOS shows a smaller, less visual link preview
TIP! If the iOS link preview behavior is causing problems, swap the hyperlink for a single suggested action (CTA button). You'll get a cleaner, more consistent layout across both platforms.
Sender Name and Agent Branding May Render Inconsistently
This is one of the most commonly reported iOS quirks. On some iPhones, the agent ID will appear in place of your configured agent name, and branding banners on the agent information page may not display.
A couple of patterns we've observed:
It typically happens on the first RCS message a subscriber receives from your brand. That first message is when the device fetches your agent assets (name, description, and branding) and that fetch can be slow depending on network and device conditions. Once the assets load, subsequent messages display the Agent’s name and branding correctly.
iMessage on Mac doesn't render agent name or description. When subscribers view RCS messages from iMessage on a laptop, the agent's name and description don't display the same way they do on iPhone. The message still arrives just without the full branded experience.
GIFs Don't Animate
If you send a GIF inside a Rich Card or Carousel, iOS will display it as a static image. The animation works as expected on Android.
Tip! Plan your creative so the first frame still works as a standalone image.
Rich Card Buttons Look and Behave Differently
Suggested action buttons inside Rich Cards have a few iOS-specific quirks
Buttons appear grey and have less visual prominence than on Android.
When a Rich Card includes more than one suggested action, iOS collapses the extras into a dropdown labeled "Options" rather than displaying them inline.
Button labels can be cached by iOS and occasionally display the previously-sent label instead of the updated one in a thread.
Suggested action buttons (Open URL, Add Calendar Event, etc.) render inside the card on iOS, instead of in a separate bubble below the card as they do on Android.
Suggested reply buttons can sometimes render in a separate bubble below the card on iOS, the inverse of where iOS places suggested actions.
TIP! For the cleanest cross-platform experience, design Rich Cards around a single primary CTA and avoid stacking multiple action types in one card.
Media Rendering and Cropping
iOS and Android handle Rich Card and Carousel media differently:
Vertical / Portrait images: iOS preserves portrait aspect ratios. Android center-crops portrait images, so the same image can look noticeably different across devices.
Carousels: iOS sizes each card based on its media and text length, so cards in the same Carousel can render at different heights. Android keeps every Carousel card the same size by center-cropping media to fit.
TIP! To keep your creative looking great on both platforms, keep critical content well inside a safe zone away from the edges, and use the same aspect ratio across every card in a Carousel. For full media specs and aspect ratio recommendations, see the Guide to Media in RCS Cards and Carousels.
Rich Card Text Has a 3-Line Limit on iOS
On iOS, Rich Card titles and descriptions are each limited to 3 lines of text, and the number of characters that actually fit within those lines varies based on the subscriber's device font size settings and screen orientation. If your title and description together exceed 6 lines, the entire card becomes tappable on iOS and opens a separate full-text page (up to 200 characters for the title and 2,000 for the description). On iOS, that full-text view excludes media and suggested actions/replies. On Android, the full-text view includes them.
TIP! Keep titles and descriptions concise to avoid copy being clipped on iOS and to keep the card rendering inline alongside your media and CTAs.
Suggested Actions Stack Above Replies
When you mix suggested actions (CTAs) and suggested replies in a single message, iOS always places all actions above all replies regardless of the order you defined them. If you have more than two suggested actions, iOS hides the extras under an Options dropdown.
Tip! For the most consistent layout across both platforms, place your single primary CTA as the first suggestion and try to limit yourself to one action per message.
Suggested Replies Persist Differently
On iOS, suggested replies stay visible as a list until the subscriber interacts with one of them. On Android, replies appear as transient chips and disappear as soon as the subscriber sends a message or until a subsequent message is received.
"One Message" Preview Without a Title
If a Rich Card doesn't include a title, iOS will show "One Message" as the lock screen and conversation list preview instead of pulling text from the body. Always include a title on Rich Cards so iOS subscribers see something meaningful in their notifications.
Android Behavior Summary
Here's a quick summary of how Android handles the same patterns differently from iOS:
Center Cropping Is Universal
Android applies center cropping to portrait media and standardizes Carousel card sizes, so creative looks uniform but may lose edge content.
Message-Level Suggestions Are Transient
Suggestion chips that appear below a message disappear once the subscriber sends a reply or a subsequent message is received. Buttons inside a Rich Card or Carousel stay visible, they're part of the card itself and aren't subject to the same transience.
Rich Card and Message Suggestions Are Separate
When a Rich Card with suggestions is followed by message suggestions, Android keeps them visually distinct (suggestions inside the card; chips below). iOS combines them into one stacked list.
Full-Text Overflow Includes Everything
When a Rich Card's text exceeds the inline limit, Android's full-text view shows the media and suggestions alongside the longer text.
Cross-Platform Best Practices
A short checklist for RCS message that you want to look great on both iPhone and Android:
Keep titles and descriptions short. Three lines or less per field prevents truncation on iOS and avoids triggering the tappable full-text view.
Use one CTA per message. A single suggested action keeps the layout clean and avoids iOS's "Options" dropdown.
Lead with the action. Place your primary suggested action first so iOS's "actions above replies" rule doesn't reorder your layout unexpectedly.
Put hyperlinks last. Or replace them with a suggested action button for cleaner cross-platform rendering.
Design for static images. Don't rely on GIF animation as the focal point of a campaign.
Keep critical content inside the safe zone. Edges may be cropped depending on the platform. See the Guide to Media in RCS Cards and Carousels for guidance.
Always include a Rich Card title. This prevents iOS from showing "One Message" in notifications and conversation previews.
Preview on both platforms. Before activating a flow or scheduling a campaign, send yourself a test on an iPhone and an Android device to confirm the layout works as expected.
What to Do If You Spot an iOS RCS Issue
If something looks off on iPhone, whether it matches one of the quirks above or it's a new one, the most effective thing you can do is file a bug report with Apple. RCS on iOS is rendered entirely by Apple's Messages app, so OS-level fixes have to come from Apple. The volume of reports Apple receives on a specific issue is the single biggest factor in whether it gets prioritized.
File a Bug Report with Apple
Head to the Apple feedback page for Messages, select your country, and choose Bug Report as the type. In the description, walk through what you observed, the iOS version, the device model, and the steps to reproduce. Include screenshots if you have them or can provide them. When you reach the What Messages feature is your feedback about? prompt, select Other. After you submit, hang on to the Feedback ID that appears.
Share the Feedback ID with Us
Once you've filed with Apple, send the Feedback ID to Postscript Support. We use these to spot patterns across merchants, aggregate similar reports, and escalate where we have partner channels all of which helps build the case for Apple to prioritize a fix.
Get Support
Have questions? Please feel free to reach out to our Support team at [email protected] or via live chat.
Need ongoing channel strategy guidance? Please fill out this form and we'll connect you to one of our certified partners.