by
Helmut Wandl
5 (4 reviews)
Peak Publisher
One place for all your plugins: publish to wordpress.org without SVN, self‑host the rest, and serve updates — all inside WordPress.
Peak Publisher ranks #34,434 among WordPress.org plugins with 10+ active installations, a 5/5 rating from 4 reviews, and was last updated Oct 24, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1.4
v2.0.0
Current Version v2.0.0
Updated 1 week ago
Last Update on 24 Oct, 2026
Refreshed 1 week ago
Last Refreshed on
Top 50% by installs
Downloads -73.4% this week
Actively maintained
Rank
#34,434
—
No change
Active Installs
10+
-64.3%
KW Avg Position
178
—
No change
Downloads
1.1K
+5 today
Support Resolved
0%
—
No change
Rating
100%
Review 5 out of 5
5
(4 reviews)
Next Milestone 20
10+
20+
11,261
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 3 more installs to reach 20+
Rank Changes
Current
#34,434
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
5.0
4 reviews
Overall
100%
5
4
(100%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 2.0.0
- Last Updated
- Oct 24, 2026
- Requires WP
- 5.8+
- Tested Up To
- 7.1.4
- PHP Version
- 8.1 or higher
- Author
- Helmut Wandl
Support & Rating
- Rating
- ★ ★ ★ ★ ★ 5
- Reviews
- 4
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade Now
Frequently Asked Questions
Common questions about Peak Publisher
No — it works with it. For plugins on wordpress.org, Peak Publisher is the SVN client you no longer need: it publishes, manages assets and the Live Preview and keeps the Stable tag right, while wordpress.org stays the update server. For plugins that do not belong on wordpress.org — client work, private or proprietary extensions — Peak Publisher is the update server itself.
Self‑hosted: your plugin includes an Update URI header that points to your Peak Publisher site, and the bootstrap code makes WordPress core ask its endpoints for update metadata and packages. wordpress.org: as always, through wordpress.org.
PHP 8.1 and WordPress 5.8 or newer, and these PHP extensions: openssl — to connect a wordpress.org account; the SVN password is encrypted with it. xml with its dom and simplexml parts — for wordpress.org (the SVN listings) and for SVG assets on both channels. mbstring — for readme.txt; the parser reads multibyte text. curl — to publish to wordpress.org; the upload is streamed through it, reading works without. intl — for domain names in the whitelist; IP addresses need nothing. Recommended: zip — releases are built with ZipArchive and can be edited after the upload (Tested up to); without it WordPress's own ZIP code builds them and the edit is refused. gd — for the banner color of generated icons. Most hosts ship all of these. Where openssl, intl, dom, zip or curl is missing, Peak Publisher says so at the place that needs it.
Nothing about people. Peak Publisher sends no telemetry, and its requests never carry your site's address. What it stores about the client sites of self‑hosted plugins and what it sends to wordpress.org is described under "Privacy" and "External services".
The version sites receive. Releases have no status: every release is listed and downloadable by version, and the plugin points to the one that is current. Self‑hosted, Peak Publisher serves it; on wordpress.org it is the Stable tag in trunk/readme.txt, which Peak Publisher writes for you. Every upload decides with the switch "Set as current" — a higher version becomes current by default, a pre‑release or a hotfix of an older line does not — and "Make current release" in the release list changes it later, on both channels. The current release cannot be deleted; make another release current first.
Peak Publisher 1.x used drafts to hold a release back. Since 2.0, every release is listed and downloadable by version, and only the current release is offered as an update. After the update, a notice names every former draft; if a version must not be reachable at all, download its ZIP and delete the release.
In the editor, every release has a pencil in its Tested up to column. Self‑hosted, the readme.txt inside the release ZIP is updated in place; on wordpress.org, one commit writes the tag and, when trunk carries the same version, trunk — sites see the new value once wordpress.org has processed the commit. The next upload carries the highest known value — its own or the previous release's — into the readme line that already exists. readme.txt is the place for the value; if your main plugin file carries a Tested up to line as well, wordpress.org and Peak Publisher take that one, so keep both in step or leave the header line out.
A button on your plugin's wordpress.org page that opens WordPress Playground with your plugin installed and activated — a full WordPress in the visitor's browser. It is driven by assets/blueprints/blueprint.json, which Peak Publisher lets you edit with fields for the landing page, the theme and the plugins (or as JSON), test in Playground and commit together with the other assets. The preview installs the required plugins of the current release before your plugin, and a publish that changes the current release keeps them in step. Making the preview public is done on wordpress.org (Advanced View on the plugin page); Peak Publisher shows you whether it is.
Only what the checklist tells you: workspace artifacts are removed by the patterns in the settings (optional), readme.txt is stored as UTF‑8 without a BOM, the release ZIP gets the plugin's slug as its top‑level folder, a lower Tested up to is raised to the highest known value in the lines that already carry one, and on wordpress.org the Stable tag in trunk/readme.txt is set when the release becomes current.
Yes. For self‑hosted plugins you can optionally configure a whitelist of IP addresses, CIDR ranges or domain names for the public endpoints. For stricter access control, consider placing your Peak Publisher site behind a VPN or a reverse proxy, or adding your own authentication layer. The whitelist guards the API; the release ZIPs on disk are guarded by the .htaccess Peak Publisher writes into wp-content/uploads/pblsh-peak-publisher/, which Apache and LiteSpeed honor. On nginx, add a rule that denies direct access to that directory except for the images under plugins/*/assets/ and wporg-plugins/*/mirror/assets/, which are meant to be served directly.