Sending Video Without Wrecking It

Why messaging apps shrink video

Not to inconvenience anyone, and not carelessly. Video is by far the largest thing people send, and an app carrying it for hundreds of millions of users pays for every megabyte twice over.

So the app re-encodes: lower resolution, lower bitrate, sometimes a lower frame rate. The result plays instantly on a phone and looks acceptable there, which is what the app is optimising for.

The cost is that the recipient's copy is a generation further from the source, and the loss compounds if it gets forwarded again. A video that has been through three chats has been re-encoded three times — each encode starts from the previous one's output.

Some apps offer a setting to send at original quality, and several offer a document or file option that skips the compression. Both are worth finding once, because the default is compression.

Routes that preserve the file

The email row is the one that surprises people. Attachment limits are small enough that almost any video exceeds them, which is why mail systems increasingly replace attachments with cloud links automatically.

Cloud storage is the pragmatic answer for most cases: the file stays intact, the recipient downloads at their convenience, and nothing is compressed in transit. The trade is that the link needs to keep working for as long as they need it.

When sending the link beats sending anything

If the video is public and still available, the link is better on every measure.

It costs no data, arrives instantly, and gives the recipient the current version — including any correction the creator posted since. It also lets them choose a quality that suits their connection and their storage rather than inheriting yours.

And nothing is lost. A link is not a copy, so there is no encoding, no compression and no generation to count.

The one thing it costs is control. A link depends on the video staying up and on the recipient having a connection when they get to it, both of which are outside your hands in a way a file is not.

Send the file instead when the recipient has no connection where they will watch, when the video may disappear, or when they specifically need it as a file for something — the same reasoning that decides whether to download at all.

Reducing size deliberately, if you must

Sometimes a file genuinely has to be smaller, and the reasons are usually practical — an attachment limit, a slow connection at the other end, a recipient with a full phone.

The best way is to download a lower quality in the first place rather than shrinking afterwards. Choosing 480p instead of 1080p costs one encode; downloading 1080p and compressing it costs two, and the second one starts from already-compressed data.

If the file is already on your device, trimming is usually more effective than re-encoding. Half the video at full quality is a better artefact than all of it at half quality, and every phone has a trimming tool built in.

Re-encoding is the last resort and it works. Just be aware that it is the step this whole article is about avoiding, and doing it deliberately with a known setting beats letting a messaging app do it silently.

If you do re-encode, do it once and from the best copy you have. Compressing a file that a messaging app already shrank produces a third generation from a second, and the result is visibly worse than compressing the original to the same size would have been.

Between your own devices

• Same ecosystem — the built-in device-to-device transfer preserves the file and is usually the fastest option in the room.
• Phone to computer — a cable moves the file untouched and avoids every cloud and messaging question.
• Across ecosystems — cloud storage or a transfer service, since the convenient built-in options rarely cross the boundary.
• To a television — a memory stick, formatted as exFAT, with the file in MP4 — televisions are the pickiest destination.

The cable is underrated. It is unglamorous, it works without an account or a connection, and the file that arrives is byte-for-byte the one that left.

Cloud sync between your own devices deserves a caution. Several services offer to optimise storage by keeping a smaller copy on the device and the full one in the cloud, which is sensible for photographs and occasionally means the file you think you moved is a placeholder.

The signal is a file that opens instantly and a copy operation that takes far longer than the size suggests, because it is downloading while it copies. Worth knowing before leaving with a laptop you assumed had everything on it.

The forwarding problem

The worst case for quality is not one transfer but a chain of them, and it happens without anyone deciding to degrade anything.

A video sent to one person, forwarded to a group, saved by someone there and sent on again has been re-encoded at every hop. Each encode starts from the previous output, so the losses accumulate rather than staying constant — which is why a clip that has circulated for a while looks noticeably soft.

You can recognise the pattern by the artefacts: blocky flat areas, smeared motion, text that has gone mushy. Those are compression damage rather than a bad original, and no amount of processing recovers what each hop discarded.

The way out is to break the chain: if the video is still public somewhere, download it from the source rather than passing along the copy you received. One fresh download beats any number of forwards.

What to check at the other end

Two things worth confirming when quality matters, because both fail silently.

The file size. If the recipient's copy is markedly smaller than yours, something re-compressed it in transit. That is the quickest signal available and it takes one message to check.

That it plays to the end. Transfers can truncate, and a partial file frequently opens and reports the full duration — the check.

For anything important — a deliverable, a record, something that will be edited — those two questions before the source disappears are worth the exchange.

There is a third question worth asking for anything that will be shown publicly: does it play on their device at all. A file that opens on your phone can fail on an older one or on a television, usually because of the codec rather than the transfer — which codec, and why it matters.

That is worth establishing before a meeting or a presentation rather than in front of one. Sending the file the day before and asking whether it opens costs a message and removes the failure that cannot be fixed in the moment.