Skip to main content

Troubleshooting

File upload errors: size limits, timeouts, and large media

Last updated Fri, Oct 16, 2026

Find the message you saw in the table below. Each one points to a different limit, and knowing which one saves a round of questions.

MessageWhat it meansFirst thing to try
"exceeds the maximum upload size for this site" (WordPress)The file is larger than the site allowsMake the file smaller; see below
"exceeds the upload_max_filesize directive"The server's PHP limit was hitMake the file smaller, or ask for the limit to be reviewed
"413 Request Entity Too Large"The web server or CDN refused the file before the CMS saw itAsk support; this limit is not in the CMS
"not allowed to upload this file type" (WordPress)The file type is blocked for securityConvert the file, or ask whether the type can be allowed
"Only files with the following extensions are allowed" (Drupal)The field does not accept this file typeUse an allowed type, or ask for the field settings to change
"HTTP error" or an upload that stalls, then failsUsually a timeout, or the server ran out of memory processing a large imageResize the image and try again
Upload seems to work, but the file is missing or emptyThe request exceeded a size limit and arrived with nothing attachedTreat it as a size problem

Why there is more than one limit

An upload passes through several layers, and each has its own limit. The smallest one wins:

  1. CDN or firewall: may cap the size of a request.
  2. Web server: refuses requests over its maximum body size, with a 413 error.
  3. PHP: two settings, the maximum file size and the maximum size of the whole form, which must be raised together.
  4. Timeouts: a slow connection uploading a large file can run out of time at any layer.
  5. The CMS: WordPress shows the site's limit on the Add Media screen; Drupal sets a maximum size and allowed types on each file or image field.

Raising one limit without the others usually just moves the error, which is why limits are best changed together by whoever manages the hosting.

Fix it yourself first

  • Photos: a photo straight from a phone or camera is often 5 to 15 MB and 4,000 or more pixels wide. Resize to the largest size the page displays, about 2,000 pixels for a full-width banner and much less for content images, and export as JPEG or WebP. The file usually drops below 1 MB, and the page loads faster too.
  • PDFs: scanned documents and print-ready brochures are often huge. Export a web version with compressed images, or use your PDF tool's "reduce file size" option.
  • Video: upload to a streaming service such as YouTube, Vimeo, or your organization's video platform, and embed it. Video files belong on services built to stream them, not in the CMS media library.
  • Audio and data files: check whether a link to the source system, such as a document repository or open data portal, would serve visitors better.

When to ask for a higher limit

Some files are legitimately large, such as high-resolution maps, board meeting packets, or research datasets. Ask for a limit to be raised when the file cannot reasonably be made smaller and visitors need to download it from your site. Say how large the files are and how often you upload them, so the limit can be set to fit rather than raised as far as possible: very high limits make the site easier to abuse.

Notes by platform

WordPress: the current limit appears under Media, Add New. A file type error on a common format such as SVG is deliberate, because SVG files can carry scripts; ask before enabling a plugin that allows them. Drupal: limits and allowed types are set per field, so the same file can upload to one content type and fail on another. Cascade: uploads go into Cascade, not your web server; if a large file uploads to Cascade but fails to publish, that is a publishing issue for support.

How eWay handles uploads

On sites eWay manages, upload limits are treated as one chain, PHP, web server, gateway timeouts, and CMS field settings, and tuned together so a change does not just move the error. Uploaded files are restricted by type and scanned. Shared file storage means every server in an autoscaled site sees the same media.

What to include in a support ticket

  • The exact message, with a screenshot
  • The file's type and size
  • Where you were uploading: the page, content type, or field
  • How often you upload files that size

eWay customers can open a ticket in the support portal or email support@ewaycorp.com. Related reading: Core Web Vitals and page speed.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article

Platform Notes

Get practical WebOps and cloud insights in your inbox

We publish articles on managed operations, cloud infrastructure, CMS platforms, government technology, and security, written by engineers who operate these environments every day. No marketing fluff. Unsubscribe any time.

We respect your privacy. No spam, no third-party sharing. Unsubscribe any time.