Set a Clear Media Upload Policy Inside WordPress

• Hosting limits are usually designed as broad server safeguards. A server may allow 128 MB uploads because a particular application occasionally needs large files, while the WordPress content team should never be uploading 80 MB images into the Media Library.
• Limit Media Upload Size lets WordPress enforce a stricter content policy without lowering the server-wide PHP limit. Enter the maximum media size you want to allow and WP PowerSuite rejects Media Library uploads above that threshold.

Respect the Real PHP and Hosting Limits

• A WordPress plugin cannot safely raise upload_max_filesize or post_max_size beyond what PHP and the server allow. Showing a 100 MB WordPress setting on a host that only accepts 20 MB would create a misleading interface.
• WP PowerSuite therefore calculates the effective upload maximum as the minimum of your configured value, PHP's upload_max_filesize, and PHP's post_max_size. The settings interface shows this effective value, making it clear whether WordPress or the hosting environment is the limiting factor.

Apply the Same Rule to Classic and REST Media Uploads

• Media files can enter WordPress through more than the Media Library screen. Modern editors and integrations may use REST-based media uploads, while classic interfaces use WordPress's normal upload handling.
• The module enforces the limit on both supported paths. Classic Media Library uploads receive a normal upload error when the file is too large, while REST media uploads return an HTTP 413 upload-size error. This keeps the policy consistent instead of allowing an integration to bypass a restriction that only exists in the browser UI.

Show Users the Limit Before They Upload

• Rejecting an oversized file after the upload attempt is useful, but showing the correct limit in WordPress is better for editors.
• On Media Library and media-modal contexts, WP PowerSuite filters WordPress's reported upload limit so the interface displays the same effective maximum the module enforces. Editors can see the policy before they choose a file instead of discovering it only after a failed request.

Control File Size Separately From File Type