One Master Video, Four Deliveries: Export Sizes For YouTube, TikTok, WhatsApp And Email

The Export That Bounced

The campaign video was finished at four in the afternoon: ninety seconds, one product, shot vertically and horizontally because the client wanted it everywhere. I exported the YouTube version first, a handsome 93.6 MB file, and sent it to the client's WhatsApp group for approval. WhatsApp refused it on the spot. The limit for a video sent as a media message is 16 MB, and my approval copy was nearly six times that. The re-export, the re-send and the lost hour all came from solving the easiest platform first.

The rule that came out of that afternoon, and the short answer to this whole page: export in order of strictness. Solve the tightest ceiling first, because its bitrate decision is the only one that can fail, and every looser platform is then a quick render at settings you already understand. What follows is the four ceilings, the delivery table for that same ninety second video, and the checklist my export folder now runs on.

The Four Ceilings

Each platform states its limit differently, so I keep one table. WhatsApp's media documentation sets 16 MB for a video message. Gmail accepts attachments up to 25 MB. TikTok's ceiling depends on the app: 72 MB on Android, 287.6 MB on iOS, with the desktop uploader allowing far more. YouTube sits at the other extreme, 256 GB or twelve hours per upload. For any single video, the binding constraint is whichever of your platforms is smallest, and for most small businesses that is WhatsApp, because approval groups and customer chats live there.

The right-hand column is the working trick of this whole article, and it is one line of arithmetic: ceiling in megabytes, times eight, divided by seconds, gives the highest total bitrate that fits. Every export below was solved that way first, then priced exactly with the video file size calculator before anything rendered.

One Video, Solved Four Ways

Here is the campaign video delivered four ways, in the order I now solve them. The master itself is a ProRes 422 file at 147 Mbps, which for ninety seconds weighs 1,653.75 MB, about 1.65 GB. It goes to the archive drive and nowhere else.

Start with the strictest platform and every other export becomes easy. I learned that order by breaking it.

Two rows deserve a second look. The TikTok export is deliberately solved against the Android ceiling, not the iOS one, because a file that passes everywhere never has to be re-rendered for a colleague's phone.

And the WhatsApp row is the one that shapes the afternoon: at 720p and 1.2 Mbps the picture stays honest on a phone screen, which is the only screen it will ever be judged on. The YouTube row hides one more convenience: at a 20 Mbps uplink it uploads in about 0.62 minutes, while the master on the same line would take about eleven minutes, which is how the flipped order used to eat the end of my Fridays.

The Order I Export In Now

Step 1: weigh the master and file it away. Note its size for the archive, then exclude it from every delivery decision. Masters are editing assets, not sending files.

Step 2: solve WhatsApp first. Ceiling times eight divided by seconds gives the total bitrate budget. Subtract the audio rate, set the video rate to what remains, and confirm the size in the calculator.

Step 3: solve email next, if the video travels by email at all. Same arithmetic against 25 MB. Most of my client videos skip this row; approval happens in chat.

Step 4: render TikTok and YouTube from the master, not from each other. Every delivery comes from the master file, so no version inherits another version's compression. Live launches follow a different logic again, since the stream itself is the delivery, and I set those bitrates by the headroom rule in The Live Streaming Bitrate Guide.

Step 5: name files by platform and check sizes before sending. The folder holds video-youtube, video-tiktok, video-whatsapp. A file whose size disagrees with the table does not get sent; it gets re-exported while the fix is still free.

What Goes Wrong When The Order Flips

The flipped order, YouTube first and everything else shrunk from it, fails twice. It fails on quality, because a file compressed for YouTube and then compressed again for WhatsApp carries two rounds of damage, and it fails on time, because the strict export is discovered last, usually at the moment someone is waiting on it. I have made both mistakes on client work, and the second one costs more.

The master-first habit behind this checklist is the same one that ended the launch-week drive failure in The Story Of The 11 GB Lesson Video: keep the master for editing, price every delivery from it, and never send the archive file by reflex.

The use case is any small team shipping one video to many places: a shop launching a product, a teacher sending a lesson to a class group and a channel, a creator cutting one shoot into a week of posts. The platforms will keep their ceilings. The only variable is whether you meet the strictest one at the start of the afternoon or at the end of it.