
Convert between KB, MB, GB and KiB, MiB, GiB to see why Windows, macOS and upload portals disagree, with real byte counts.
The upload portal says the limit is 5 GB. Your screen recording shows 4.8 GB in the Windows file list, and the upload still fails. Nothing is wrong with either number; they count in different units. File Size Converter shows a size in decimal units and binary units side by side so you can see which side of the limit you really are on.
The video below covers converting between byte units.
Decimal units are powers of 1,000. One KB is 1,000 bytes, one MB is 1,000,000 and one GB is 1,000,000,000. Drive makers, phone makers, network equipment and many web services use them.
Binary units are powers of 1,024. One KiB is 1,024 bytes, one MiB is 1,048,576 and one GiB is 1,073,741,824. Memory is built this way, and so is the size readout in Windows, which still prints the letters GB even though it divides by 1,024 cubed. macOS divides by 1,000 and prints the figure you would expect from the box.
Each step up the ladder widens the gap. At kilo level it is 2.4 percent; at giga level the binary unit is about 7.4 percent bigger than the decimal one; by tera it is about 10 percent.
Open the tool, type 4.8, and choose GiB from the unit menu (the menu labels binary units with 1024 and decimal ones with 1000). The decimal column answers the question: 4.8 GiB is 5,153,960,755 bytes, or about 5.154 GB. The portal's 5 GB limit, if it means 5,000,000,000 bytes, is already exceeded by roughly 154 MB. The file never fit.
The same logic runs the other way. A 5 GB cap equals about 4.66 GiB, so anything Windows shows above 4.66 "GB" is over. Trim the clip or compress it with the video tools until Windows shows 4.5 or less, which leaves headroom.
The conversion happens in the page as you type, and your numbers are not sent anywhere. The page counts one of your 10 trial usages for the day.
Email attachments. A provider advertises 25 MB. A 24 MiB PDF looks safe, yet 24 MiB is 25.17 MB, so it is over a decimal limit. At the other end, 25 MB is only 23.84 MiB, so a file that your computer lists as 24 MB may be refused. When a limit is close, assume the smaller reading.
Drives. Enter 500 with GB selected in the drive box. The tool reports 465.66 GiB, a 6.9 percent gap, because 500,000,000,000 bytes divided by 1,073,741,824 is 465.66. A 2 TB drive shows as 1.82 TiB, a 9.1 percent gap. No space is missing; Windows is describing the same bytes with bigger units.
Cloud plans. A 1 TB plan is 1,000,000,000,000 bytes, about 931 GiB. If your photo library shows 930 GB in the file manager, you are almost full even though the arithmetic "930 of 1000" feels comfortable.
Before you send anything large, write down the limit and its unit from the service's own page, convert your file to bytes with the tool, and compare the two byte counts. If the limit is stated in MB, test the decimal column; if it says MiB, test the binary one; if the page does not say, use the lower figure. Leave about five percent of headroom, because some services count the encoded size of an attachment, which can be larger than the file on disk. This takes under a minute and avoids retrying a long upload that was never going to pass.
If the converted figure shows a bundle is too big, Zip and Unzip can pack related files together, though compression gains vary by file type. Large spreadsheets exported as CSV can shrink dramatically when you drop unused columns; CSV Converter is the place to reshape them. The wider security and developer tools category lists further utilities.
If you publish a limit in a contract, support page or form, write the byte count or the unit explicitly, for example "10 MiB (10,485,760 bytes)". Support teams then answer fewer tickets that begin "my file is exactly the right size". For contractors delivering large files, naming the unit in the brief removes a whole class of rejected handoffs.
Which limit has tripped you up most, an attachment cap, a portal quota or a drive purchase? Let us know on the contact page.