File Hosting & Sharing

File Size Limit

Definition

A file size limit is a hard ceiling on one object. Under it the file is accepted; over it the upload is refused outright, normally before a single byte is written to storage. The figure is quoted in binary or decimal units and the difference is not academic — a 100 MB limit meaning 100,000,000 bytes will reject a file of 100 MiB, which is 104,857,600 bytes and about five per cent larger. Limits often vary by plan and sometimes by file type, with archives and video allowed more room than a single image. Keep it clearly apart from the upload limit, which constrains one request, and from the storage quota, which totals everything you are holding.

Why It Matters

Most files that hit a ceiling did not need to be that size. A 60 MB PDF is usually a 6 MB PDF with uncompressed scans inside it, and a 400 MB video is often a 40 MB video exported at the wrong bitrate by a default nobody changed. Shrinking it is therefore the fix and an improvement at the same time: a visitor on a phone downloads the 6 MB version in seconds and the 60 MB one not at all. Where the size genuinely is necessary — a raw dataset, a layered design source — the honest answer is a ZIP archive split into parts, or a plan that allows it, rather than a workaround that leaves you with half an object in storage.

How It Works

The host compares the declared length against its ceiling at the start of the request and refuses early if it is over, answering 413 with a message that usually names the limit. A browser upload declares its size in Content-Length, so the check costs nothing; a streamed upload with no declared length has to be measured as it arrives and cut off at the threshold instead. Where rules differ by type, the host reads the MIME type or the file extension to decide which rule applies, which is why renaming a .mov to .zip occasionally appears to work and mostly does not. Some hosts apply the limit after decompression as well, so a 40 MB archive that expands into 2 GB of files is rejected on the way out of the archive rather than on the way in.

Real-World Example

A university department tries to publish a 320 MB lecture deck stuffed with embedded video and is turned away at the ceiling. Exporting the videos separately and linking to them leaves a 14 MB deck, which goes to 99helpers as bioscience-lecture-4.99helpers.site without argument. Students on campus Wi-Fi now open it in about two seconds, and the ones on mobile data open it at all. The 320 MB original was never going to be read on a phone.

Common Mistakes

  • Assuming MB means 1,048,576 bytes — a file of 100 MiB is over a 100 MB decimal limit by nearly five per cent and is rejected without explanation
  • Renaming a file to slip past a type-specific rule — hosts inspect the MIME type as well as the extension, and the upload fails anyway
  • Splitting a large file across several uploads without saying so — the recipient receives three parts and no instruction for putting them back together

Related Terms

Put a file online in seconds

Drop in a document, an image, a page or a whole static website and share the link — free, with no build step and no server to set up.

Host a file free →