You can, and for two plugins you should. This exists for the twentieth site handover, the staging rebuild and the new-client setup where the same fifteen or twenty ZIPs go up every time. The saving is not really the clicking, it is that one pass produces one report you can hand to somebody else as evidence of what was installed.

Twelve things, each with its own refusal message. That the file is a readable ZIP at all. That it holds no symbolic link. That it is neither empty nor absurdly large in file count. That the uncompressed size stays under a 256 MB safety limit. That there is exactly one top-level folder. That the folder name is valid. That a real WordPress plugin header exists. That the main plugin file sits directly inside the top-level folder rather than nested deeper. That no path is unsafe. That no path contains a parent-directory segment. That the declared PHP requirement is met by this server. That the declared WordPress requirement is met by this site.

Not unless you tick the box. Replacement is off by default and so is activation, which is the opposite of what a batch tool usually does. The reasoning is simple: a batch that silently replaces a working plugin on a live site is a worse failure than a batch that stops and tells you the folder already exists.

The rest carry on. One invalid archive does not hide the results for the other twenty-four. Each file gets its own operation and its own outcome in the final report, so a bad download is a named line rather than an abandoned run.

In your own database, permanently, until you delete them. Each report holds the filename, the plugin name, the version, the operation performed and the WordPress error message where there was one. It never stores the contents of the uploaded ZIP and it never stores credentials.

Administrators with the WordPress capability to install plugins, and nobody else. It is a tool for the person who already has the keys, not a way to hand out a lesser set of keys.

That is up to your server, not up to the plugin, and it is the one limit we cannot set for you. A batch is an ordinary PHP file upload, so it is bound by upload_max_filesize, post_max_size, max_file_uploads and max_execution_time on the host running the site. A default of 20 in max_file_uploads caps the batch at twenty regardless of what you paid for, a small post_max_size rejects the whole submission, and a short execution limit can end a large run part-way through. Check those four values under Tools, Site Health, Info, Server before you plan a big batch, raise them in php.ini or through your host's panel if you control them, and split the batch if you do not. Twenty-five is the plugin's ceiling, not a promise about your hosting.

It is the preferred path and it is present on almost every host. Where it is missing the plugin falls back to PclZip, which WordPress bundles, though symlink detection is weaker on that route. We would rather tell you that than let you assume the two paths are identical.

Yes. It reads the plugin header inside the ZIP and hands the validated archive to WordPress's own upgrader, so anything that installs through Plugins, Add New, Upload Plugin installs here. Licence activation is still whatever that plugin does after installation.

Buy through the checkout and the download and your licence key arrive by email, usually within the hour. Install through Plugins, Add New, Upload Plugin. Updates come by email for the life of your licence.

14-day money-back guarantee, no questions. Email us and we refund you.