WordPress Plugin Submission Checklist

Complete guide for submitting plugins to WordPress.org repository

Completion Progress

0%
Plugin Developer Portal

Pre-Submission Requirements

Plugin Files & Structure

readme.txt File (Required)

Plugin Assets (Images)

Security & Best Practices

SVN Repository Setup (After Approval)

Final Submission Steps

Asset Size Reference

Plugin Icon
256x256px: icon-256x256.png
128x128px: icon-128x128.png
Or: icon.svg (vector)
Plugin Banner
Standard: 772x250px
Retina: 1544x500px
banner-772x250.png/jpg
banner-1544x500.png/jpg
Screenshots
Recommended: 1200x900px
screenshot-1.png
screenshot-2.png
screenshot-3.png...
⚠️ Important
All images must be under 1MB
Use PNG or JPG format

Who Uses This Checklist?

🚀

First-Time Plugin Developers

New developers submitting their first WordPress plugin to the official directory, ensuring they meet all requirements.

💼

WordPress Agencies

Development agencies creating custom plugins for clients and submitting them to WordPress.org for distribution.

🎓

WordPress Educators

Teachers and course creators teaching WordPress plugin development and submission best practices.

🔧

Freelance Developers

Independent developers building and submitting plugins to expand their portfolio and reach more users.

🏢

SaaS Companies

Software companies creating WordPress integrations and submitting free versions to the plugin directory.

📦

Open Source Contributors

Community members contributing to the WordPress ecosystem by creating and maintaining free plugins.

Frequently Asked Questions

How long does WordPress plugin review take?

The initial review typically takes 1-5 business days. After approval, you receive SVN access to upload your plugin files. Complex plugins or those requiring clarification may take longer.

What are the required image sizes for WordPress plugins?

Plugin Icon: 256x256px and 128x128px (or SVG). Plugin Banner: 772x250px (standard) and 1544x500px (high-DPI/retina). Screenshots: 1200x900px recommended. All images should be under 1MB.

Is readme.txt required for WordPress plugin submission?

Yes, readme.txt is mandatory. It must follow the WordPress readme.txt standard format and includes plugin name, description, tags, version, tested up to, requires at least, license, changelog, and installation instructions.

Do I need to know SVN to submit a WordPress plugin?

Yes, basic SVN knowledge is required. After approval, you use SVN to commit your plugin files to the WordPress.org repository. You need to understand trunk, tags, and assets folders.

Can I submit a premium WordPress plugin to WordPress.org?

Yes, but the plugin in the directory must be fully functional and free. You can offer premium add-ons or pro versions separately, but the core plugin must provide real value without requiring payment.

What happens if my WordPress plugin is rejected?

You will receive an email explaining the reasons for rejection. You can fix the issues and resubmit. Common reasons include security issues, guideline violations, trademark issues, or incomplete functionality.

How do I update my WordPress plugin after submission?

Use SVN to commit changes to the trunk folder for development, then create a new tag folder with the version number when ready to release. Update the readme.txt stable tag to point to the new version.

Recommended Tools

💬 User Comments

Share your thoughts and feedback about this tool

Please login to leave a comment

No comments yet. Be the first to share your thoughts!

×

Rate this tool

Select a rating