To transfer cloud storage between units, convert every size to bytes first, then divide by 1,000 (decimal, what providers use) or 1,024 (binary, what your operating system shows) per step on the ladder — the gap between the two is exactly why a "1 TB" cloud plan reports as roughly 931 GB after upload. The same byte count underwrites every label on the cloud-storage ladder, from a 5 MB attachment up to a petabyte-scale data-center backup; what changes is which prefix you divide by. A cloud-storage plan is almost always quoted in the decimal standard — 1 KB = 1,000 bytes, 1 MB = 1,000,000 bytes, 1 GB = 1,000,000,000 bytes — because that is the convention drive and SSD manufacturers, mobile-data carriers, and cloud providers all use in marketing. Your operating system, by contrast, divides the same byte count by 1,024 at every step and labels the result with the same word (KB, MB, GB), even though the binary units are officially KiB, MiB and GiB under IEC 80000-13:2008. When you transfer cloud storage between services, or compare two plans side by side, that mismatch is the silent source of every "missing gigabyte" complaint. The fix is a single conversion pass: pick a standard, type the value, and read the answer in your target unit. The Data Storage Converter does exactly that — bytes to KB, MB, GB, TB, PB and bits, in either decimal (1000) or binary (1024), entirely in your browser with nothing uploaded.
Why the Numbers Don't Match When You Transfer Cloud Storage
When you move files between cloud services, or compare two cloud storage plans side by side, the same label can quietly mean two different things. A plan advertised as "1 TB" by the cloud provider usually refers to 1,000,000,000,000 bytes under the decimal standard. Your operating system, on the other hand, reports the folder you are about to upload in binary, dividing the same bytes by 1024 four times and labelling the result with the same word "TB" — even though the binary form (TiB) is officially a different unit.
This is the classic "missing space" problem dressed up in cloud-storage clothing. Nothing is lost; the units just disagree. If you are planning to transfer 500 GB from one provider to another and both quotes are decimal, the math is simple. The moment one side is decimal and the other is binary, the numbers stop lining up by about 2.34 percent per step on the ladder. After three steps — say KB to MB to GB to TB — the gap is large enough to throw off any estimate of how much data your transfer will actually consume.
For a single worked example, take 1 TB as advertised by a provider. Under the decimal standard, 1 TB is exactly 1,000,000,000,000 bytes. To see what your operating system shows, divide by 1024 three times: 1,000,000,000,000 ÷ 1024 = 976,562,500 KiB; 976,562,500 ÷ 1024 = 953,674.31640625 MiB; 953,674.31640625 ÷ 1024 ≈ 931.3225746154785 GiB. Your OS will round that and label the result as "931 GB" — close to the often-quoted "1 TB = 931 GB" rule of thumb. Run this through the converter to confirm the exact figure for any value you are about to transfer.
Convert Cloud Storage Units Before You Move a Thing
- Type the amount you want to convert into the storage value field.
- Pick the prefix standard — Decimal (1000) for what your cloud provider advertises, or Binary (1024) for what your operating system reports — then choose the source and target units.
- Read the converted result instantly, or tick "Show all units at once" to see bits through petabytes together so you can compare every step of the ladder at a glance.
This three-step flow lets you keep both numbers in view at the same time. Type the plan's advertised quota once, flip between Decimal (1000) and Binary (1024), and read the matching figure your computer will actually show after upload. You can also flip the source and target units — say, KB to GB, or bits to bytes — to answer questions like "how many MB is this 4.7 GB video folder?" without retyping the value.
Decimal vs Binary: The Two Standards Behind Every Cloud Plan
| Unit (common label) | Decimal value (bytes) | Binary equivalent (IEC) | Where it is used |
|---|---|---|---|
| 1 KB | 1,000 | 0.9765625 KiB | Network speeds, cloud plan marketing |
| 1 MB | 1,000,000 | 0.9536743164 MiB | File downloads, mobile data caps |
| 1 GB | 1,000,000,000 | 0.9313225746 GiB | Cloud quotas, SSD labels |
| 1 TB | 1,000,000,000,000 | 0.9094947017 TiB | Cloud plans, hard-drive boxes |
| 1 PB | 1,000,000,000,000,000 | 0.8881784197 PiB | Data-center scale |
The decimal column follows the SI (International System of Units) powers of 1000 that drive and cloud-storage manufacturers use. The binary column follows the IEC 80000-13:2008 prefixes (KiB, MiB, GiB, TiB, PiB) that operating systems use when they display file sizes. Switching the converter between Decimal (1000) and Binary (1024) shows both answers at once, which is what makes planning a cloud transfer reliable rather than guesswork.
Because the binary label on a "1 TB" drive is roughly 0.909 TiB, the gap grows as plans get bigger. A 100 GB plan shows about 93.13 GiB; a 10 TB plan shows about 9.09 TiB. That gap is exactly the same fraction on every step, which means you can sanity-check any cloud-storage quote by remembering one rule: the binary number is the decimal number divided by 1.024 raised to the power of how many steps you climb.
Bits vs Bytes: The Hidden Trap in Cloud Transfer Speeds
Storage is measured in bytes (uppercase B). Internet and network speeds are quoted in bits (lowercase b). One byte is exactly 8 bits in both decimal and binary. The classic trap is reading "100 Mb/s" on a cloud-storage upload tool and expecting 100 MB of data per second — when in fact 100 Mb/s is 100 megabits per second, which is 100 ÷ 8 = 12.5 megabytes per second.
This is why a "gigabit" upload link that promises "about 125 MB/s" feels slower than the marketing copy suggests. It also explains why a 50 GB cloud backup over a 50 Mb/s home line takes more than two hours instead of the 16 minutes the raw number seems to promise. Converting bits to bytes — or bytes to bits — is the missing step in almost every cloud-transfer time estimate. The same converter that handles GB to TB also handles the bits column so you can switch units without re-entering the value.
How Big Is a Petabyte of Cloud Storage
The cloud-storage scale climbs fast. 1 GB is a thousand MB; 1 TB is a thousand GB; 1 PB (petabyte) is a thousand TB — roughly a million gigabytes, or 10^15 bytes in the decimal standard that providers use. Under the binary standard, the equivalent pebibyte (PiB) is 1024^5 bytes, which is about 1.126 × 10^15.
Petabyte-scale cloud storage is what large data centers, scientific archives, and video-streaming backbones deal in, but the same unit math applies to consumer plans too: a 2 TB plan is 2,000 GB decimal or about 1,863 GiB binary; a 200 GB plan is 186.26 GiB binary. Knowing where your own plan sits on that ladder makes it much easier to compare offers across providers. For a quick sanity check on the exact byte count, enter the value into the converter and read it in your preferred standard.
Plan Capacity vs Real Capacity: Checking Your Cloud Provider's Math
Most consumer cloud plans — Google Drive, iCloud, OneDrive, Dropbox, and the rest — quote capacity in the decimal standard, which means a "100 GB" plan is 100,000,000,000 bytes of storage, not 107,374,182,400 bytes. That is the same convention drive and SSD makers use on the box, so the marketing and the receipt agree.
The mismatch appears only when you compare that figure to what your computer reports after upload. A 100 GB decimal plan is about 93.13 GiB binary. After the system overhead of the cloud client's local cache, the visible "free space" can land closer to 90 GB. The bytes are all there; the labels just use different rulers. When you transfer cloud storage between providers, plan for the binary number as your "real" usable figure and use the decimal number for plan quotes and receipts — the converter handles both sides with one toggle.
If your transfer plans are tracked in a spreadsheet — for example, a list of folders with their sizes in one column and the destination quota in another — converting text-formatted values such as "4.7 GB" into numbers is a common stumbling block; the Convert Storage Values Stored as Text in Excel guide walks through that specific case. The conversion factors used here (1 GB = 1,000,000,000 bytes decimal, or 1,073,741,824 bytes binary) flow directly into spreadsheet formulas, so you can keep a single source of truth for both standards.
Privacy and Local Processing for Cloud Storage Numbers
Cloud transfer planning often involves file counts, folder sizes, or quota numbers that you may not want to paste into a public web form. The Data Storage Converter runs entirely in your browser, so the values you type stay on your device. There is no upload, no server round-trip, and no account needed — the conversion is computed locally using the NIST and IEC 80000-13:2008 factors of 1000 (decimal) and 1024 (binary). That makes it a reasonable choice for working out a sensitive migration size before you commit to moving files between providers.