Skip to main content

What to do when a file is too large to upload

When a file is too large to upload, compare its actual size with the destination’s stated limit before changing the document. If the file exceeds that limit, compressing, splitting or sharing it another way may solve the problem; if the site rejects the file type instead, reducing its size will not help. For a broader guide to transfer limits and alternatives, see sending large files.

An upload can fail because of size, format or submission rules

Example file 30 MB · 5 MB over
shrink first Images 22.5 MB example limit · 25 MB +5 over
  • Images22.5 MB · 75%
  • Embedded fonts3.0 MB · 10%
  • Text1.5 MB · 5%
  • Metadata3.0 MB · 10%

To clear the limit you only need to remove the overshoot — trimming the images alone takes this example file back under the line.

The example file runs past the example limit, and because the images are the largest part, shrinking them is the quickest way back under the cap.

A “file too large” message usually means the upload service has compared your submission with a maximum size and rejected it. On the web, a server may report this as an HTTP 413 Content Too Large error, although many sites replace the technical response with their own wording.

The relevant limit may apply to one file, the combined upload or the account receiving it. For example, a form might allow each attachment to be no larger than 10 MB, impose a 20 MB total across all attachments, or reject an upload when the account has no storage space left. These are different limits and require different fixes.

File size is measured in bytes, normally displayed as KB, MB or GB. Do not confuse it with the number of pages in a document. A 100-page PDF containing mostly text can be smaller than a five-page PDF filled with high-resolution photographs or scanned pages.

Large document files commonly contain one or more of the following:

  • High-resolution photographs or scanned pages.
  • Full-color images where grayscale would be sufficient.
  • Images placed at a much higher resolution than the document needs.
  • Embedded fonts, attachments, thumbnails or other stored resources.
  • Comments, layers, form elements or editing data left in the exported file.
  • Multiple documents combined into one PDF.
  • Media, detailed illustrations or other complex content.

The warning can also hide a different problem. An upload form may accept only specified formats, such as PDF, DOCX, JPG or PNG. File-selection controls can guide you toward those formats, but the service still checks the submitted file on its server. A 200 KB file can therefore be rejected if it is the wrong type, just as a valid PDF can be rejected for exceeding a size cap.

Other restrictions can resemble a size failure:

  • A combined-request limit: Each file fits individually, but uploading several at once exceeds the form’s total allowance.
  • An account or storage quota: The receiving account has insufficient remaining space.
  • A page-count rule: The file size is acceptable, but the system permits fewer pages.
  • A filename rule: The name is too long or contains characters the service does not accept.
  • A browser or network interruption: The upload starts but stalls, resets or times out.
  • A document-specific rule: A portal requires one PDF, a particular PDF standard or a document without encryption.
  • A permission problem: Your account can view the destination but cannot add files to it.

The wording and timing of the failure are therefore important. An immediate rejection after selecting a file often points to a known size or format rule. An upload that reaches part of the way and then stops is more likely to involve a connection, browser, timeout or server-processing problem.

Compare the file with the destination’s exact requirements

Start with the error message rather than compressing the file immediately. The quickest diagnosis comes from identifying the stated limit, checking the file’s properties and testing one variable at a time.

  1. Keep the original file unchanged. Work on a copy so you can compare quality, restore removed content or try a different method later.
  2. Read the complete error message. Look for a maximum size, accepted format, page limit or filename requirement. A message such as “Maximum file size: 5 MB” gives you a clear target.
  3. Check the file’s actual size. On Windows, right-click the file and select Properties. On macOS, select the file and choose File > Get Info. On a phone or tablet, use the file manager’s information or details command.
  4. Confirm the unit. A limit stated in MB is much smaller than the same number in GB. If your file is close to the cap, aim below it rather than trying to match it exactly.
  5. Check the filename extension. Confirm that the extension matches a format listed by the destination. If extensions are hidden, view the file’s type in its properties.
  6. Try one file at a time. If individual files upload but the group fails, the restriction probably applies to the combined submission or number of files.
  7. Check the destination’s storage and permissions. This is especially important when uploading to a shared folder, case-management system or organization account.
  8. Test another current browser or the service’s desktop app. Do this when the upload begins but repeatedly stalls, not when the service has already given a clear size or format warning.

The following symptoms help separate the most likely causes:

What happens Most likely cause What confirms it Appropriate response
The file is rejected immediately with a maximum size Per-file upload cap File properties show a size above the stated cap Compress or split the document
One file uploads, but several together fail Combined size or file-count limit The same files work when submitted separately Upload separately or reduce the total
A small file is rejected as unsupported Format restriction Its extension is absent from the accepted-formats list Convert it to an accepted format
The upload reaches part of the way and stops Connection, timeout or browser problem The file is within the published size limit Retry on a stable connection or use another supported upload method
The file uploads but cannot be previewed or processed Format structure, protection or service-specific rule The destination reports a processing error rather than a size error Create a clean compatible copy
Every file fails despite being small Storage, account or permission problem The destination is full or the account lacks upload access Free storage or request the correct permission

If the service does not publish a limit, note the file’s size and ask its support team or the receiving organization for the maximum permitted size. Avoid repeatedly applying stronger compression without knowing the target. A document reduced from 80 MB to 40 MB is still unusable if the portal permits only 10 MB, while unnecessary compression can make images and small text harder to read.

Choose a fix that preserves the document’s purpose

The best fix is the least destructive change that satisfies the actual restriction. First correct a format mismatch if one exists. If the format is accepted but the file is too large, reduce the content that consumes space, split the document when separate parts are allowed, or use a link when the recipient accepts linked files.

Compress an oversized PDF

Compression is usually the first choice when the destination accepts PDF and the complete document must remain in one file. PDF compression can reduce image resolution, compress image data, remove redundant items and optimize stored resources.

Use moderate compression first, then inspect the result before choosing a stronger setting. Check:

  • Small text at normal reading size.
  • Photographs, diagrams and screenshots.
  • Signatures, stamps and form fields.
  • Searchable text in scanned documents.
  • Links, bookmarks and page order.
  • Any page containing fine lines or detailed graphics.

Image-heavy and scanned PDFs often provide the greatest opportunity for reduction. A scan can store every page as a large image, even when the visible content is mostly black text on a white background. Downsampling those images or using more suitable image compression can reduce the file substantially, but aggressive settings may blur handwriting, diagrams or small print.

If you still have the source document, exporting a new PDF with an appropriate “standard,” “web” or reduced-size preset may produce a cleaner result than repeatedly compressing an existing PDF. Keep the original high-quality version for printing, archiving or later editing.

Split the document when separate files are permitted

Splitting is appropriate when compression cannot bring the document below the limit without unacceptable quality loss. It also works well when the recipient needs only part of a long document.

Choose a logical boundary rather than cutting at an arbitrary page number. Useful divisions include:

  • Main document and appendices.
  • Application form and supporting evidence.
  • One chapter or section per file.
  • Text pages and image-heavy exhibits.
  • Separate date ranges or document categories.

Name the parts clearly, such as Report-Part-1-of-3.pdf, so the recipient can identify the correct order. Check whether the destination imposes a combined total: splitting one 30 MB PDF into three 10 MB files does not help if the form allows only 20 MB across the whole submission.

Do not split a file when the receiving system explicitly requires one complete document. In that case, compression, re-exporting or asking for an alternative submission method is safer.

Convert a file only when its format is the problem

Convert the document when the upload form accepts a different format and that format is appropriate for the content. For example, a portal that accepts PDF but not a word-processing file requires a real PDF export, not an extension change.

Review the converted copy before uploading it. Conversion can change:

  • Page breaks and margins.
  • Fonts and character spacing.
  • Image quality.
  • Hyperlinks and bookmarks.
  • Comments, tracked changes or spreadsheet formulas.
  • Forms, layers, animations or other format-specific features.

PDF is often useful when the recipient needs a stable page layout rather than an editable source file. However, conversion is not automatically a size-reduction method. A poorly exported PDF can be larger than the original, particularly when it contains high-resolution images or retains extensive editing information.

Use ZIP or cloud sharing only when the destination allows it

A ZIP archive can bundle several files and may reduce the size of uncompressed content. It is less effective for data that is already compressed. JPEG images and many PDFs, videos and modern document formats may become only slightly smaller when placed in a ZIP file.

ZIP also changes what you are submitting. A portal that requests a PDF may reject a ZIP archive even when that archive contains the correct PDF. Use ZIP only when the accepted-formats list includes it or the recipient has agreed to receive an archive.

Cloud sharing avoids attaching the complete file to a message or form. Upload the document to an approved storage service, set the correct access permissions and send a sharing link. Before relying on this method, confirm that:

  • The recipient accepts links instead of direct uploads.
  • The recipient can open the link without requesting access.
  • The link will remain available for the required period.
  • The storage location is suitable for the document’s sensitivity.
  • Downloading, printing or copying permissions match the intended use.

A cloud link cannot replace an upload when a portal must store, inspect or validate the actual file. For a required application, legal filing or formal submission, ask the receiving organization for an approved alternative rather than entering a link in an unrelated field.

Whatever method you choose, compare the final file with the destination’s limit before trying again. Leave a reasonable margin below the maximum, open the new file from beginning to end, and preserve the original separately. That confirms both parts of the fix: the document is now small enough to upload, and it still contains what the recipient needs.

Source: Upload-size response behavior from RFC 9110: HTTP Semantics, RFC Editor; accepted file-type behavior from the HTML Standard file upload specification ), WHATWG; PDF image, font and cleanup optimization guidance from PDF Optimizer settings and Reduce PDF file size, Adobe; and archive-compression guidance from Zip and unzip files, Microsoft Support. Page last checked 2 October 2026.