Drag the ZIPs in, run the batch, read the report. Every archive is checked before WordPress writes a single byte, replacement and activation are both off until you say otherwise, and what happened is recorded per plugin rather than guessed at afterwards.
FROM $49/YEAR · 25 ZIPS PER BATCH · 14-DAY GUARANTEE
“New site, same nineteen plugins. Upload, wait, back, upload, wait, back…”— Thursday afternoon, every agency
The clicking is the visible cost and the smaller one. The real cost is that nobody can say afterwards which version of which plugin went onto which site, and one silently failed upload does not announce itself until a client rings. One pass, one report, and a refusal that tells you why.
Each one covers a single thing properly rather than summarising all of it badly.
The twelve checks every archive passes before WordPress writes a byte, and why a refusal beats a repair. Read it →
The four stages of a run, the two switches you control, and the jobs this was built for. Read it →
What a batch leaves behind, where it lives, what it never stores, and why the CSV is the point. Read it →
Everything in the build, plus the server limits that decide the batch size you can actually send. Read it →
Three plans, all the same Pro build. You are only choosing how many sites. See the plans →
What it refuses, what it overwrites, what happens when one ZIP in the batch is bad. Read the FAQ →
Already know what it does? The documentation covers setup and every refusal message, and the changelog records what changed in each release.