Do Text Messages Compress Photos? What Every App Does (2026)

Do Text Messages Compress Photos?

Yes. Every text messaging method compresses your photos to some degree. Standard MMS (the type of message sent between different phone platforms, or when iMessage or RCS aren't available) is the worst offender, reducing photo file sizes by up to 95%. iMessage between Apple devices preserves significantly more quality but still applies compression. RCS, which replaced SMS/MMS for Android-to-Android and now iPhone-to-Android messaging, falls somewhere in between.

The compression happens automatically. You don't choose it, you're never warned about it, and the photo on the other end looks fine on a phone screen - until someone tries to zoom in, print it, or view it on anything larger than a 6-inch display. That's when the blur, the artifacts, and the washed-out colors become obvious.

MMS: Why Your Photos Look Terrible Over Text

MMS (Multimedia Messaging Service) was designed in the early 2000s when a 2-megapixel camera was a flagship feature. Most carriers enforce a file size limit between 300 KB and 1.2 MB per message. A modern smartphone photo from an iPhone 16 Pro or Samsung Galaxy S25 Ultra weighs 4-12 MB. Something has to give.

When you send a photo over MMS, your phone compresses it before it leaves. A 4032 x 3024 pixel photo might get scaled down to 1024 x 768 or smaller. JPEG quality drops from 95% to around 40-60%. Fine details like hair, text on signs, distant faces, and fabric textures turn into blurry mush.

Carrier limits vary. T-Mobile allows up to 1.2 MB. AT&T caps at around 1 MB. Verizon sits at 1.2 MB. International carriers are often stricter - some cap at 300 KB. If you're texting someone on a different carrier or in another country, expect the worst-case compression.

iMessage: Better, but Not Lossless

When both sender and receiver are on iPhones with iMessage active (the blue bubble), photos are sent through Apple's servers rather than the carrier's MMS system. This bypasses the carrier file size limits and preserves significantly more quality.

But iMessage isn't sending your original file. Apple applies its own compression - typically HEIC format at around 80-85% quality. A 10 MB original might arrive as a 2-3 MB file. The difference is invisible at phone-screen sizes but noticeable when printing or cropping heavily. Live Photos, panoramas, and ProRAW files lose substantially more in the transfer.

The moment one person in the conversation doesn't have iMessage - an Android user, an older iPhone with iMessage off, someone with poor cellular connectivity - the entire conversation falls back to MMS or RCS, and quality drops accordingly.

Apple has never published a resolution cap or quality figure for this path, so treat the numbers above, and any percentage quoted elsewhere, as estimates. Two settings change the result. Low Quality Image Mode, under Settings, then Messages, sends a more heavily compressed copy of every photo and video to save mobile data. It is off by default, and it changes what the phone that has it switched on sends. The Camera format setting, under Settings, then Camera, then Formats, decides whether the iPhone shoots HEIC and converts to JPEG only when the destination cannot read HEIC (Automatic) or shoots JPEG from the start (Most Compatible). That conversion is a re-encode of its own, separate from whatever iMessage or MMS does to the file afterwards, and sharing HEIC photos without losing quality covers what each setting costs.

Two Apple routes send the file itself. AirDrop moves the original between nearby Apple devices. Mail offers Small, Medium, Large or Actual Size when you attach a photo, and Actual Size sends the untouched file, within the attachment limit of whichever email provider you use. For a whole album, Apple's answer is iCloud Shared Albums: Apple announced at WWDC 2026 that they would move to full resolution, and iOS 27 did that for albums created on it or upgraded to it. The details are in iCloud Shared Albums going cross-platform.

RCS: The New Default, but Still Not Full Quality

RCS (Rich Communication Services) has replaced traditional SMS/MMS as the default messaging protocol for Android, and since iOS 18 in late 2024, iPhones also support RCS for cross-platform messages. This means the green bubbles between iPhone and Android are no longer carrier MMS - they're RCS messages sent over data connections.

RCS allows file transfers up to 100 MB in the Google Messages implementation, which is a massive improvement over the 1 MB MMS limit. Photos sent over RCS retain much more detail. But they're still compressed. Google Messages applies JPEG compression that typically reduces files by 30-50%. A 10 MB photo arrives as a 5-7 MB file. It's noticeably better than MMS, but it's not the original.

RCS support also varies by carrier and region. Not every carrier supports the same file size limits, and some older implementations cap files at 10 MB. If either end of the conversation doesn't support RCS, the message falls back to MMS compression.

What Messaging Apps Do to Your Photos

Messaging apps like WhatsApp, Telegram, and Signal handle photo compression differently from text messages, but they all compress to some degree.

WhatsApp's default photo sharing compresses aggressively - a problem I covered in detail in why WhatsApp destroys your photo quality. You can work around it by sending photos as documents, but most people don't know to do that. Telegram lets you send uncompressed files by choosing "Send as File" instead of the default photo mode. Signal compresses similarly to WhatsApp but also offers a document sending option.

App by App: Which Ones Keep the Original File

Text messages are one route out of many. Photos also travel through Telegram, Discord, Slack, Gmail, Google Drive, Dropbox and Google Photos, and those split into two groups: apps that re-encode a photo on their default send, and apps that store the file you uploaded and show you a lighter preview of it. The second group keeps getting mistaken for the first, because the preview is the copy people look at.

Telegram

Telegram has two ways to attach an image, and they behave differently. Pick an image with the Photo option, or paste it into the chat, and Telegram re-encodes it as a JPEG at reduced quality before sending. Choose File instead and the exact bytes you selected go out unchanged, up to Telegram's per-file size limit. Both sit in the same attachment menu, so the compression is not hidden, but Photo is the default and most people never look past it.

A photo sent as Photo also arrives without its EXIF data: GPS coordinates, date and time, camera and lens settings. Telegram does not publish the quality setting or a target resolution for that pass. JPEG itself, standardised as ISO/IEC 10918-1, is lossy, so what a lower quality setting throws away is gone for good, and every further lossy pass compounds it. Saved Messages follows the same rule, because it is a chat with yourself rather than a separate storage mode.

Send as File beats WhatsApp's send as document on one point: you can pick several files and send them in one message instead of one at a time. The photos still end up inside a chat thread, with no gallery view and no single link to hand someone who was not in the conversation.

Discord

Discord does not resize every photo to a fixed number of pixels the way WhatsApp and Instagram do. Its Help Center documents a file size limit instead, and a photo under that limit is stored and served back as the file you uploaded. A free account can attach 20 MB per file, raised from 10 MB in August 2026. Nitro Basic allows 50 MB, Nitro 500 MB, and Discord is testing a 250 MB limit a server can buy with five boosts. Whichever limit is higher for that upload applies.

The August 2026 change also moved the check: Discord now measures the file you picked before any compression, where the mobile app used to compress first and only then report that the result was still too large. A single phone photo of a few megabytes sits under every tier. Quality is lost when a file is over the limit and has to be shrunk, either through Discord's own compression prompt, which it offers for video, or by whatever you used to make the photo smaller before trying again.

A photo that looks soft in a channel is usually the inline preview, which Discord's image delivery layer resizes for the space it fills on screen. Open the attachment and compare its pixel dimensions and file size with what you uploaded. Discord does not document whether EXIF data such as GPS coordinates survives an upload, so strip location from anything you would not want geotagged before posting it.

Slack

Slack stores the file you upload at its original resolution and size, and the download button returns that same file. Slack's help center caps uploads at 1 GB per file on every plan from Free to Enterprise+, and describes no quality reduction of the stored file.

What you see in the channel is a separate, lighter rendition built so a busy channel scrolls quickly. Slack's documentation says an image only previews inline if it is under 25,000 pixels on its longest side and under 45 million pixels in total; past that it shows as a plain attachment. A public bug report against Slack's own SDK shows the split: the API returns a file's original dimensions, while the URL used to render it inline points at a smaller, recompressed copy. Screenshots with fine text suffer most in that preview, and uploading them as PNG rather than JPEG avoids most of the softening.

Retention is the larger risk. On the Free plan, Slack's pricing and help pages describe 90 days of access to message and file history, with anything older than a year permanently deleted. Pro, Business+ and Enterprise+ keep unlimited history. A photo shared in a Free workspace does not get smaller over time; it disappears.

Gmail

A photo attached with the paperclip icon goes out as a file: no resize, no re-encode, and its metadata intact. The limit is 25 MB per message across all attachments together. Above it, Gmail does not shrink the photos; it uploads the attachment to Google Drive and puts a link in the message, and the recipient then needs permission on that Drive link to open it.

The other button is where quality goes. Insert photo, the picture icon, places the photo inline in the body and asks for a size: Small, Medium, Large or Original. Anything other than Original downscales the photo before it is sent, and inserting a photo from Google Photos rather than from your device sends whatever quality it was backed up at. When someone says a photo you emailed looks soft, check which button was used and which size was picked.

Google Drive

Google Drive stores a photo the way it stores a PDF: the bytes you upload are the bytes you download, with no resizing, no re-encoding and no quality setting to choose. EXIF data, GPS coordinates included, comes back out unchanged, because Drive never processes the file as an image. The thumbnail and the built-in viewer use a smaller preview that exists only for the interface.

The confusion comes from Google Photos, a separate product that compresses on its default setting and, since June 2021, shares the same 15 GB of free storage with Drive and Gmail. Sharing a folder from Drive keeps every photo intact. The recipient sees a list of filenames like IMG_4523.jpg rather than a gallery, and depending on the permission you set, may be asked to sign in to a Google account first. Drive versus Photos goes further into that trade.

Dropbox

Dropbox's own help pages say its cloud storage does not compress photos, and that compression usually happens in a photo app, a preview renderer, or when a file is shared through email or a social platform. A file uploaded to Dropbox is the same file when it is downloaded again.

When a photo from Dropbox looks wrong, the cause sits on either side of it. The file may have been compressed before it arrived, because it was saved from WhatsApp or Instagram or exported from an editor at reduced quality. The Carousel and other browsing views render a lighter preview for speed, which downloading the file bypasses. Or the photo was forwarded through an app that compresses after it left Dropbox.

The limits are storage, not quality: 2 GB on Basic, the free plan, 2 TB on Plus, from 3 TB on Standard and from 15 TB on Advanced. Uploads through the desktop and mobile apps have no fixed per-file limit, and uploads through a browser are capped per file. A shared folder opens as a list of filenames with no grouping by date or location, which Dropbox compared with Viallo goes into.

Google Photos

It depends on the upload setting. Google's documentation for Storage saver, the setting most free accounts start on, says photos are compressed to a maximum of 16 megapixels and videos to 1080p. A 48 MP photo from a recent flagship phone comes down to roughly a third of its pixel count. Original quality stores every photo exactly as uploaded.

Since June 2021 both settings count against the same 15 GB Google Account allowance shared with Gmail and Drive, so Storage saver no longer buys free space, only smaller files. To check yours, open Google Photos, then Settings, then Backup, and look at the upload size. Changing it affects photos uploaded afterwards and does not restore detail already lost. A shared album serves whatever quality its photos were stored at, so an album of Storage saver uploads is compressed for every viewer. Location, timestamps and camera data are read on either setting, since they drive search and the map view.

When Photo Compression Actually Matters

For a quick snap you're sharing with one person who'll glance at it on their phone and never think about it again, MMS compression is fine. The photo looks acceptable at phone screen resolution and nobody will notice the quality loss.

Compression becomes a problem when:

• Someone wants to print the photo. A compressed 1024 x 768 image can't produce a decent 4x6 print, let alone anything larger.
• You're sharing event or trip photos with the whole family. Grandparents on their iPad, cousins on a laptop - larger screens expose compression artifacts instantly.
• The photos are professional or semi-professional. Client work, real estate photos, product shots, or anything where quality is part of the value.
• You're building a shared album. Once a photo is compressed, you can't get the quality back. If ten people text their event photos to a group chat, every single one arrives degraded.
• You want to preserve memories long-term. Photos compressed today become the only version that exists tomorrow if the originals get deleted from the sender's phone.

How to Share Photos Without Any Compression

The most reliable way to share photos at full resolution is to skip the messaging layer entirely. Instead of attaching photos to a message, upload them to a service that preserves originals and share a link.

Viallo is a private photo sharing platform that stores photos at full resolution - the exact file you upload is the file that gets stored and viewed. You create an album, upload your photos, and share a link. The person on the other end opens it in any browser, sees the full gallery with a lightbox viewer, location grouping, and map view, and can download originals if they want. No account, no app, no compression. The free plan includes 2 albums, 200 photos, and 10 GB.

Other options for full-resolution sharing:

• AirDrop - Full quality, but only between Apple devices within Bluetooth range. Useless for remote sharing.
• Google Photos shared albums - Keeps originals on the "Original quality" setting. The "Storage saver" setting compresses to 16 MP. Anyone with the link can view without signing in; adding photos needs a Google account.
• iCloud Shared Albums - Albums created before iOS 27 compress photos to a maximum of 2048 pixels on the long edge. Albums created on iOS 27 or upgraded to it keep originals.
• Send as document/file - Works in WhatsApp, Telegram, and Signal. Preserves quality but recipients get loose files, not an organized album.

Frequently Asked Questions