To suggest a feature for WordPress Core, first search the Core issue tracker (Trac) for an existing ticket. If you do not find one, submit a clear request that explains the problem, who it affects, relevant use cases, and how the change would improve the user experience. For a broader idea that needs exploration—or a feature you are prepared to lead—use the appropriate feature-project or feature-plugin proposal route instead.
Choose the right place for your WordPress idea
Start by deciding whether you need help using WordPress or want to propose a change to the software. Those are different requests and belong in different places.
| What you need | Where to take it | Best fit |
|---|---|---|
| Help with a WordPress problem or question | WordPress Support | Support questions, rather than proposals to change Core. |
| A defined improvement to WordPress Core | A ticket in the Core issue tracker, Trac | A scoped feature request with a clear problem and user benefit. |
| Exploration of a larger or less-defined idea | A Core feature project or wider Core discussion | Ideas that need contributors to investigate and shape possible approaches. |
| A feature you are prepared to organize and develop | A feature-plugin proposal | A contributor expects to take an active, primary role in moving the work forward. |
The Core handbook also points contributors to Core tickets and contributor channels for development proposals. For a broader discussion, the community tutorial recommends grounding the conversation in a concrete issue on GitHub or Trac before raising it in an appropriate meeting; a Make blog post can suit a larger proposal. See Navigating the Community for discussion routes.
Submit a WordPress Core feature request
- Search Trac before opening a ticket. Look for tickets about the same problem or proposed change. As you enter a summary, related tickets may appear. If you find a match, add useful context to that ticket instead of creating a duplicate.
- Write a specific summary. State the requested change in a way that helps other contributors understand the proposal quickly.
- Explain the problem and its value. Describe the use cases, who would benefit, and what would improve in the user experience. The Contribute with Code handbook says: “If you are submitting a feature request, include a thorough description of your idea, stating use cases and/or user experience improvements.”
- Choose the relevant component and workflow keywords. Select the component that best matches the area of Core involved. The handbook gives
needs-patchandneeds-feedbackas examples of workflow keywords to use when appropriate. - Submit the ticket and take part in discussion. A ticket gives contributors a concrete place to assess the idea, ask questions, and provide feedback. It is a proposal, not a commitment that the feature will be built.
When to propose a feature project or feature plugin
Feature projects: explore an idea with others
A feature project is a way to gather people around a potential Core idea and investigate it. Work can begin as exploration and develop into patches or plugins, but starting a project does not guarantee that its work will be merged into WordPress Core. The Feature Projects overview describes this route.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
Feature plugins: organize and lead active work
A feature-plugin proposal is a better fit when someone is ready to take an active, primary role in the work. The handbook describes a short proposal covering the idea’s overview, current stage, interested participants, and the help needed. Consult Features as Plugins for the proposal route.
What happens after you submit an idea?
Contributors can discuss, refine, or develop a proposal, but its submission does not establish that it will ship in Core. For feature-plugin merge consideration, the handbook identifies several factors: a well-tested user experience, mature design, positive community feedback, core-quality code, and a belief that the feature belongs in Core. The release lead and Core team decide whether a feature is ready and suitable to merge. An idea may remain an experiment or plugin, or stop before implementation.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Can users vote on WordPress feature requests?
A WordPress.org forum moderator response says the former feature-voting area had been removed and points people to the Requests and Feedback forum and the Core handbook. That response is a forum post, not formal current policy documentation: see the moderator response and use the official Core contribution guidance for current proposal routes. Voting should not be treated as a decision mechanism for what Core builds.
Quick Recap
Best Value
Rank #4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Recommended Free Tools
