WordPress Plugin Boilerplate Generator
Generate a WordPress plugin boilerplate with your name, prefix and requirements, plus an optional admin page, saved settings, a widget and documented hooks. Download a ready-to-install ZIP.
Did this tool work for you?
Community
User Reviews & Ratings
Be the first to share your experience
About this tool
About WordPress Plugin Boilerplate Generator
WordPress Plugin Boilerplate Generator creates the starting files for a new plugin with your details already in place. Enter the plugin name, description, author, URLs, version, text domain, a constant prefix and the minimum WordPress and PHP versions, and the tool writes the main plugin file with a valid header, a singleton plugin class, activation and deactivation hooks, text-domain loading, and front-end CSS and JavaScript loaded the WordPress way. A readme.txt in the WordPress.org format and a helper functions file are always included. Optional parts are added only when you tick them: an admin menu page with tabs, a settings form built on the Settings API with sanitised saving, an example widget, and documented extension hooks that other developers can use. Every function, option and hook name uses a prefix made from your plugin slug, and the widget class is named after your plugin, so two generated plugins can run side by side. The ZIP is built in your browser and installs through Plugins → Add New → Upload Plugin.
How to use WordPress Plugin Boilerplate Generator
1
Describe your plugin
Enter the name, description, author, URLs and version. The text domain is filled in from the name.
2
Set requirements
Choose the constant prefix and the minimum WordPress and PHP versions for the plugin header.
3
Pick features
Add an admin page, saved settings, an example widget or documented hooks as needed.
4
Download and install
Download the ZIP, then upload it at Plugins → Add New → Upload Plugin and activate it.
Key features
Activates without errors
Every generated file passes PHP syntax checks, with valid prefixes and escaped strings even when names contain apostrophes.
Working settings page
The optional admin page includes a real Settings API form that saves and sanitises its option.
Plays well with others
Prefixed functions, options and hooks, and a uniquely named widget class, avoid clashes with other plugins.
Lean by default
Optional files are only included when enabled, and admin CSS loads only on the plugin’s own screen.
1 / 2
Who needs a plugin boilerplate
Start with structure instead of a blank file
Site-specific functionality
Move custom code out of functions.php into a plugin so it survives theme changes.
ExampleGenerate “Acme Site Tweaks” and paste existing snippets into includes/functions.php.
Client feature plugins
Deliver a feature with its own settings screen that clients can manage.
ExampleEnable the admin page and settings to give the client an on/off switch under their own menu item.
Learning plugin development
See how hooks, the Settings API and widgets fit together in working code.
ExampleInstall the generated plugin locally and follow how the settings form saves through options.php.
Plugins for WordPress.org
Start with the header fields and readme.txt structure the plugin directory expects.
ExampleFill in Requires at least and Requires PHP, then complete the generated readme.txt before submitting.
Moving code out of a theme
Keep shortcodes and custom functions working when the theme changes.
ExampleCustom shortcodes are moved from functions.php into a generated plugin before a redesign.
Agency starter plugins
Start every client add-on from the same clean, prefixed structure.
ExampleEach client feature plugin uses the agency as author and a client-specific prefix to avoid clashes.
Tips for a solid plugin
Good habits from the first file
Check capabilities and nonces
Protect every form and AJAX action with current_user_can() and a nonce. The functions reference has copy-ready examples.
Open WordPress Functions ReferenceClean up on uninstall
Add an uninstall.php that deletes the plugin’s options when it is removed, so it does not leave data behind.
Keep the version in sync
Update the Version header, the version constant and the readme.txt Stable tag together when you release.
Need a content type?
Generate register_post_type() code with the CPT builder and add it to your plugin.
Open the CPT GeneratorEscape everything you output
Use esc_html, esc_attr and esc_url when printing data, as the generated admin page does, to prevent XSS.
Use the hooks for extensions
Fire your own actions and filters, like the generated _init and _loaded hooks, so other developers can extend your plugin.
