Uploading Large Files to the Server (Over 128 MB)

In Seravo's server environment, the maximum size for an individual HTTP request is set to 128 MB by default, with a maximum execution time of 3 minutes. This limit corresponds to the server’s PHP directives (upload_max_filesize and post_max_size) and is enforced to ensure server stability and mitigate denial-of-service attempts.

The server-level 128 MB limit cannot be raised directly by modifying php.ini file. If you need to upload larger files to your site, you can achieve this either by using a plugin that automatically splits uploads into chunks or by transferring files directly to the server over SFTP or SSH.

Method 1: Uploading to the WordPress Media Library (Big File Uploads Plugin)

The easiest way to upload large files directly through the WordPress admin dashboard is by installing the Big File Uploads plugin.

The plugin circumvents the server's 128 MB HTTP threshold by automatically splitting large files into small chunks in the browser and reassembling them on the server upon arrival. Because individual chunks remain well within server limits, uploads complete reliably without timing out.

Install and activate the Big File Uploads plugin in your WordPress admin dashboard under Plugins > Add Plugin.
Navigate to the plugin settings via Settings > Big File Uploads.
Enter your desired new maximum file size (for example, 500 MB or 1 GB), keeping your plan’s available disk storage in mind, and save your changes.
Chunking operates automatically in the background—you can now upload large files normally to the WordPress Media Library (Media > Add Media File).

Tip: In the plugin settings, you can also customize upload limits per user role or file category (e.g., separate thresholds for videos vs. images).

Method 2: Direct Transfer via SFTP and Media Library Import (Developers)

If you are dealing with files several hundred megabytes or gigabytes in size (such as database dumps, complete site backups, or large archive files), transferring them directly over a secure SFTP or SSH connection is the fastest and most reliable method.

Open an SFTP connection to the server using an FTP client (such as FileZilla or Cyberduck) by following our SFTP access guide.
Transfer the file directly to your target directory on the server, such as /data/wordpress/htdocs/wp-content/uploads/.
Optional (registering the file in the WordPress Media Library): If you want the transferred image, PDF, or media file to appear in the WordPress Media Library dashboard, register it in the database by running the following WP-CLI command over SSH:
```
wp media import /data/wordpress/htdocs/wp-content/uploads/filename.pdf
```

Note on WordPress Multisite Networks

If your site is part of a WordPress Multisite network, you may encounter an upload size restriction long before reaching the server's 128 MB ceiling. By default, WordPress restricts the upload limit on multisite networks to approximately 1.5 MB (1500 KB).

You can raise this WordPress-level network limit directly under My Sites > Network Admin > Settings > Upload Settings. For detailed steps and a megabyte-to-kilobyte conversion chart, refer to our dedicated guide: How to Change the Maximum Upload File Size in a Multisite Installation.

Troubleshooting and Recommendations

Why can't I edit php.ini directly?
Seravo runs an optimized, secure server architecture where nginx and backend services protect sites from resource exhaustion. Server-level HTTP boundaries are managed centrally for system stability, which is why individual php.ini overrides are disabled.
Uploads failing with a timeout error:
If uploading a large file without a chunking plugin returns a timeout error (such as 504 Gateway Timeout), make sure you are either using the Big File Uploads plugin to handle chunked transfers or uploading the file directly over SFTP.
Should you host large video files in WordPress?
We generally recommend against hosting video files that are tens or hundreds of megabytes directly in the WordPress Media Library. Serving raw video files consumes significant storage and bandwidth and lacks dynamic adaptive bitrate streaming for mobile devices. Consider using specialized video hosting platforms (such as Vimeo or YouTube) or offloading storage to a dedicated cloud provider (such as AWS S3).