File size units like KB, MB, and GB show up constantly — in upload limits, email attachment warnings, storage plans — and having a rough practical sense of what each one actually represents makes these numbers far easier to reason about quickly, rather than treating them as abstract technical jargon.
The basic scale, roughly
- KB (kilobyte) — roughly the size of a short plain-text email or a very small, simple icon.
- MB (megabyte) — roughly the size of a typical compressed photo, a few pages of a text-heavy PDF, or a short audio clip.
- GB (gigabyte) — roughly the size of a lengthy video, a large photo collection, or a substantial software installation.
Why these rough comparisons are more useful than the exact math
Each unit is technically 1,000 (or, more precisely in computing contexts, 1,024) times larger than the one below it, but for everyday practical purposes, having a rough mental sense — "a photo is a few MB, a video is several GB" — is more genuinely useful than memorising the exact conversion factor.
Applying this to common everyday limits
- An email attachment limit around 25MB roughly corresponds to a handful of compressed photos, or a moderately sized PDF.
- A typical image upload limit around 5-10MB comfortably fits most compressed photos, even fairly high-resolution ones.
- A cloud storage plan measured in tens or hundreds of GB corresponds to thousands of photos or a substantial collection of documents and videos.
Why a file's actual size can surprise you
A file's size depends heavily on its content and how it's been compressed, not just its type — a simple, mostly-text PDF can be a fraction of the size of a PDF containing several scanned images, even though both are technically "a PDF." This is why a general expectation like "PDFs are small" doesn't always hold in practice.
Using this knowledge when troubleshooting a size-related error
When you hit a size-related error or limit, having a rough sense of these units helps you quickly judge whether compression alone is likely to solve the problem, or whether the file is fundamentally too large for its type and needs a more substantial change, like removing content or splitting it into smaller pieces.
Where these units show up beyond files themselves
The same units also describe things like mobile data plans and internet connection speeds, which is a useful cross-reference — understanding that a several-GB file will take a meaningfully longer time to upload or download on a slower connection helps set realistic expectations for how long a given file transfer might actually take.
A note on the difference between storage size and transfer speed units
It's worth distinguishing file size units (KB, MB, GB) from the similarly-named units used for internet connection speed (Kbps, Mbps), which measure data transferred per second rather than a fixed total amount. Confusing the two is a common source of miscalculating roughly how long a file transfer might actually take on a given connection.
Why operating systems sometimes show slightly different numbers for the same file
You may occasionally notice a file's reported size differs slightly between your computer's file browser and an upload dialog elsewhere. This is usually down to a difference between the 1,000-based and 1,024-based calculation conventions mentioned earlier, applied inconsistently across different software, rather than the file itself actually being two different sizes.
Why this knowledge helps you communicate about files more clearly with others
Having a shared, roughly accurate sense of these units makes conversations about files considerably more efficient — describing something as "a few MB" versus "several GB" quickly conveys useful information to someone else without either of you needing to check an exact figure first.
Building an intuitive sense over time rather than memorising figures
The most practical way to internalise these units isn't memorising exact conversion factors, but simply noticing and remembering roughly how big your own common files tend to be — your typical photo, your typical PDF — which naturally builds an accurate, personally calibrated sense of scale over time through everyday use.
A quick sanity check worth running before a large upload
Before starting a large upload, a rough mental estimate of the expected file size against the destination's stated limit can save you from discovering a rejection only after the upload has already taken a while to get partway through.
Frequently asked questions
Roughly how big is a typical compressed photo?
Usually a few MB, though this varies with resolution and compression level.
Why do two PDFs of similar page count have very different file sizes?
File size depends heavily on content, particularly embedded images, not just page count or file type.
What does a 25MB email attachment limit roughly correspond to?
Roughly a handful of compressed photos or a moderately sized PDF document.
Is it worth memorising the exact KB-to-MB-to-GB conversion?
Not necessarily; a rough practical sense of scale is generally more useful for everyday decisions than exact conversion math.
Does a slower internet connection affect how these sizes feel in practice?
Yes, the same file size will take meaningfully longer to transfer on a slower connection, which is worth factoring into expectations.
How does this help when I hit a file size error?
It helps you judge whether compression alone will likely solve the problem, or whether more substantial changes are needed.
Are the tools for compressing files on this site free?
Yes. No sign-up, no watermark, and files are removed from the server automatically about an hour after processing.