Welcome to the Elementor Contribution Guidelines
Community contributions are always welcomed and help us remain the Number 1 WordPress Website Builder. Contributors can answer questions on all Elementor GitHub spaces or submit their contributions in the appropriate channels.
Before submitting contributions, all participants should read and follow these Guidelines and our Code of Conduct.
We use GitHub exclusively for well-documented Bug Reports, Feature Requests and Code Contributions (Pull Requests).
Communication should always be in English.
For any other topic, please use the appropriate channels. For all things Elementor visit our website: https://elementor.com.
Note
We are currently collecting feedback and reports for the new Editor V4, a complete re-architecture of the Elementor Editor focused on performance, modularity, and a CSS-first design system.
If you're testing Editor V4, please use the following dedicated forms:
Please note that the Editor V4 is in active development, may be unstable, and may lack some functionality found in Elementor V3. Use it only in testing environments, and make sure to review the scope and purpose of each form before submitting your reports or feedback.
Note that we are unable to offer any level of support through this repository.
Please DO NOT open issues or discussions to request for Personal Support.
For those, use the appropriate channels.
Find out how to submit a Support Ticket here.
Alternatively, you can visit one of these resources:
- Help Center
Visit the Elementor Help Center to find solutions to the most frequent problems, or read the documentation about Elementor's many features. - Academy
Grow your Web Creator skills and learn to make the most of Elementor in the Elementor Academy. - Discord Community
Connect and chat with other Web Creator in different channels (including on multiple languages) through our official Elementor Discord Community. - Global Community
Join the Elementor Global Community on Facebook. Where all kinds of users come together to help each other. - Support Forum
If you have more questions, visit the free Support Forum on our WordPress plugin page. - Elementor Website
For more information about features, FAQs, and documentation, check out our website at Elementor Website Builder.
If you have an active Elementor Pro subscription, you are entitled to personal support. Please see your purchase email or visit your Elementor Account page for details.
As a gentle reminder, we may close support requests submitted to GitHub spaces without action.
Security is paramount at Elementor. If you discover a security vulnerability, we want to hear about it right away, and we appreciate your help in disclosing it to us in a coordinated manner. For this reason, we run community-driven Managed Security Bug Bounty programs.
We leverage the collective expertise of our community, offering round-the-clock crowdsourced vulnerability detection. These programs provide a comprehensive overview of features and endpoints considered 'in scope,' reward specifics where relevant, and our complete terms and conditions.
Join our Managed Security Bug Bounty programs instead and help us maintain Elementor, a secure software, responsibly.
To learn more about our security efforts and how to contact us for security inquiries, please visit our Trust Center.
If you found a bug in the source code and can reproduce it consistently after troubleshooting it, you can help us by submitting a Bug Report.
To help us review and resolve your report efficiently, all submitted bug reports must meet the following requirements. These rules ensure that reported issues are actionable, reproducible, and relevant.
-
All fields in the bug report form are required — no exceptions.
Missing or incomplete information leads to unnecessary delays and often makes issues unreviewable. Issues missing required fields may be closed without review. -
Search for similar issues before opening a new one.
Duplicate reports create unnecessary noise and slow down the triaging process. Before posting, search the open and closed issues to see if your problem has already been reported or addressed. -
Ensure you are using the latest stable versions.
Bugs that occur in outdated versions may already be fixed. Please make sure Elementor, Elementor Pro, WordPress core, your theme, and all plugins are up to date.
Check the changelog. -
Clear all levels of cache.
Issues caused by outdated or conflicting cached data are common. Before submitting a report, clear your browser cache, CDN cache, plugin cache, and server cache — in that order — to avoid false positives. -
Test with only Elementor, Elementor Pro, and the Hello Elementor theme active.
Conflicts from third-party plugins or themes are not actionable by our team. Isolate the issue by deactivating all unrelated plugins and switching to the Hello theme before reporting the problem.
See: Troubleshooting the Editor -
Include your full Elementor System Info.
This diagnostic report helps us understand your environment and replicate the issue. Reports submitted without this information will be closed.
How to get your System Info -
If you are a third-party developer, please identify yourself.
Include your name, company, and a way to reach you. If your report involves compatibility with your own plugin, theme, or integration, this helps us follow up appropriately. -
Only one issue per report.
Submitting multiple bugs in a single issue makes tracking and resolving them harder. Please open separate reports for separate problems.
We can only accept bug reports that fall within the scope of what we actively support. Submissions that do not meet this criteria will be closed without action.
-
Requests for personal support
GitHub is not an efficient support channel. For assistance with setup, common issues, troubleshooting, or how-to questions, please contact our Support Team or visit our Help Center. -
Conflicts with third-party plugins, themes, or services
If the issue only occurs when using tools not officially supported by Elementor, please contact the third-party developer. We do not triage or resolve external compatibility issues. -
Feature requests or missing functionality
If something is not broken but simply not yet supported, it's not a bug. Please use the Feature Request form instead. -
Custom code and unsupported modifications
We cannot help debug issues related to custom snippets, hooks, filters, overrides, or undocumented modifications. Refer to our Developer Documentation if you're building custom integrations. -
Security issues
We take security very seriously. And we want to resolved in a responsible manner. Please, do not disclose vulnerabilities as bug reports. Use our Bug Bounty Program for coordinated and responsible security reporting. -
Complaints, or inappropriate content
GitHub issues are not the right place for complaints about Elementor's products, services, or policies. Reach out to Elementor Support Instead. We also do not tolerate hostile, discriminatory, or disrespectful remarks. See our Code of Conduct. -
Invalid, incomplete, or vague reports
Reports missing required fields, lacking reproduction steps, or submitted without proper validation will be closed to maintain the quality and focus of the issue tracker.
To ensure we can understand and resolve the issue effectively, follow these writing guidelines when filling out the form:
-
Use a clear and descriptive title
A well-written title helps other users (and our team) quickly understand what the report is about and whether it might be related to other reports. -
Describe the issue in detail
Explain what happened, when it happened, and what part of Elementor is affected. Include any error messages, behavior patterns, and relevant context. Screenshots and screen recordings are especially helpful. -
List all steps to reproduce the issue
Reproduction steps are essential for verifying and fixing bugs. Provide a step-by-step guide of what you did, so we can reproduce it - ideally on a clean WordPress install. If we cannot reproduce the issue, we cannot resolve it. -
Explain what you expected to happen
Make clear what the correct or intended behavior should be. This helps us understand if the issue is due to a bug, a misunderstanding, or a missing feature.
As a gentle reminder, issues that do not meet these guidelines may be closed without further action. These standards ensure that our team and community contributors can manage reports effectively and focus on actionable feedback.
Have an idea to improve Elementor? We're always open to feedback that helps us create better tools for web creators. If you'd like to request a new feature or enhancement, you can do so by submitting a Feature Request.
You can also support existing ideas by voting for your favorite requests.
To help us evaluate suggestions effectively, all submitted feature requests must meet the following requirements. These rules ensure each request is unique, well-defined, and relevant to Elementor's core product vision.
-
Search for existing requests before posting.
Duplicate requests reduce clarity and fragment community support. Please search both open and closed requests to avoid duplicates. Prefer to always Vote for existing requests instead of submitting new ones. -
Verify that the feature is not already available.
Before suggesting a new feature, check the Features page and your current Elementor setup to confirm it doesn't already exist. -
Submit only one request per thread.
Submitting multiple suggestions in one request makes it harder to discuss, prioritize, and track individual ideas. Use one form per idea. -
Be specific about what problem the feature solves.
A request that's grounded in a clear problem is easier to evaluate and more likely to be prioritized. Vague requests or "nice-to-have" ideas without a real use case may be closed. -
Explain your proposed solution clearly.
The more detail you provide, the easier it is for our team (and the community) to understand how this could be implemented ad Vote for it.
To stay focused and productive, we may close requests that do not meet the following criteria:
-
Out of scope for Elementor's core mission.
Requests that require major architectural changes, niche workflows, or overlap with third-party integrations that Elementor doesn't directly support may fall outside the product roadmap. -
Already supported or recently released features.
If the feature already exists or was just released, we may close the request and link to the existing implementation. -
Bug reports, support requests, or custom code questions.
These belong in other dedicated forms. Please report confirmed bugs using the Bug Report form, and use Support Channels for troubleshooting or help with custom code. -
Low-detail or unclear submissions.
Requests lacking context, justification, or clear value may be closed to keep the list relevant and actionable.
To ensure your suggestion is well understood, please include the following in your request:
-
A clear and descriptive title.
Helps others quickly understand the purpose of your request. -
The problem it solves.
Describe the need or limitation this feature would address. -
Your proposed solution.
Explain what you'd like to see added or changed in Elementor. -
Any alternatives you've considered.
If you've tried workarounds or plugins, share your experience. -
Extra context.
Screenshots, examples, or links to related ideas can help others understand your vision.
As a gentle reminder, Feature Request discussions that do not meet these guidelines may be closed without further action. These standards ensure that our team and community contributors can manage reports effectively and focus on actionable feedback.
Community contributions are always welcome! We're glad to hear you are interested in helping shape the future of Elementor.
There are many ways to contribute to Elementor
The Elementor User Interface was designed with a global audience in mind. It supports a wide range of languages and is also RTL compatible. Out of the box, we offer support for over 60 languages.
Want to make a difference?
We would appreciate your contribution by adding a new language or helping translate existing ones at translate.wordpress.org. To assist you, we've built a short guide explaining how to translate and localize the plugin.
Join others by answering questions on Elementor's GitHub spaces to help solve issues and engage in discussions.
Your insights and solutions can greatly assist others in navigating similar challenges.
If you can submit fixes, improvements, or enhancements through pull requests, that's fantastic! We'd love your technical contributions. Please refer to our detailed guide on submitting pull requests below for more information.
- Search for Existing Issues
Check if your issue has been reported already by searching through existing Issues. - Create a new Bug Report
If you cannot find a similar issue, please create a new Bug Report. - Read our Documentation
Visit the Elementor Developers Center and read the Developers Documentation to learn how to extend Elementor.
- Fork the Repository
Start by forking the Elementor repository on GitHub. Please ensure you're using themainbranch. - Create a new branch
Create a new branch exclusive to the changes you're going to perform. This way, you can maintain separation between projects. - Make your changes
After you've forked the repository, you can start changing your copy of the code. - Adhere to Coding Standards
While making changes, ensure you stick to the WordPress Coding Standards.
If you've added new functions, actions, or filters, please document them properly following the WordPress PHP Documentation Standards. - Commit with a Reference and Note
When you commit your changes, reference your issue and include a note about your fix. - Submit a Pull Request
After pushing the changes to your fork, you're ready to submit a pull request to the main branch of the Elementor repository. Please follow our Pull Request Template when submitting your PR.
Our team will review your pull request and, if approved and everything is in order, merge it into the main branch. We are here to assist you in making sure your code aligns with the standards described above.
Your contributions, big or small, play a significant part in the continued development of Elementor. We can't wait to see what you have to share!