> ## Documentation Index
> Fetch the complete documentation index at: https://enterprise-docs.dify.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Plugin Development Guidelines

> Requirements every Dify Marketplace plugin must meet to pass review, covering quality, language, privacy, IP, maintenance, and prohibited content

By submitting a plugin to the Dify Marketplace, you agree to follow the requirements on this page. Meeting them up front gets your plugin through review faster and helps keep the Marketplace useful and trustworthy.

## Value and uniqueness

* **Generative AI focus.** The plugin's core capability should integrate models, tools, or services that meaningfully extend AI applications on Dify.
* **No functional duplicates.** Don't reskin an existing Marketplace plugin. Each plugin should be unique and stand on its own.
* **Meaningful updates.** New versions must add real capability, not just metadata bumps.
* **Explain new submissions.** In your PR description, say briefly why the plugin is needed and what gap it fills.

## Plugin checklist

Before opening the publish PR, confirm each item:

* **Unique name.** Search the Marketplace first.
* **Brand alignment.** The plugin name reflects what it actually is.
* **Works end-to-end.** Tested via [remote debugging](/en/3.11.x/develop/plugins/features-and-specs/plugin-types/remote-debug-a-plugin); production-ready.
* **README in English** with setup steps, required credentials, and usage. No exaggerated claims, ads, self-promotion, offensive content, real user data in screenshots, or dead links.
* **Clear error messages** for required fields and failure modes.
* **Authentication steps documented in full**, with no skipped steps.
* **Privacy policy ready.** See [Privacy Guidelines](/en/3.11.x/develop/plugins/publishing/standards/privacy-protection-guidelines).
* **Credentials handled securely**, never hardcoded, never exposed.
* **Performance acceptable.** Does not noticeably degrade Dify itself.

## Language

English is the primary language for every user-facing string: plugin name, description, field labels, help text, error messages. Additional translations are welcome on top of English.

## Prohibited and restricted plugins

| Category                                         | Reason                                                         |
| ------------------------------------------------ | -------------------------------------------------------------- |
| **Prohibited**: misleading or malicious behavior | spam, phishing, credential theft, deceiving the review process |
| **Prohibited**: offensive content                | violence, hate speech, discrimination                          |
| **Prohibited**: financial transactions           | payments, asset transfers, token transfers                     |
| **Restricted**: frequent defects                 | repeated submissions with critical bugs                        |
| **Restricted**: unnecessary splitting            | multiple plugins for the same API/auth; bundle them instead    |
| **Restricted**: duplicate submissions            | re-submitting essentially the same plugin                      |

Prohibited plugins are rejected. Restricted plugins may be delayed or asked to consolidate.

## Monetization

**The Dify Marketplace currently accepts free plugins only.** Pricing policies, if introduced, will be announced separately.

## Trademarks and intellectual property

* **You must have the rights** to any logo, trademark, or copyrighted material you include. We may ask for proof for recognizable third-party brands.
* **Do not use Dify's logos** in your plugin assets.
* **Image quality** must be sharp and well-cropped. No misleading or offensive icons.

Dify may ask for changes or remove a plugin if a rights holder complains or if unauthorized use is found.

## Updates and versioning

* **Announce breaking changes** in the plugin description or via GitHub Release Notes before users hit them.
* **Update regularly** for bug fixes, Dify platform changes, security patches, and upstream-service changes.
* **Deprecation notice.** If retiring a plugin, give users time to migrate and suggest alternatives where possible.

## Maintenance and support

You own technical support for your plugin. Provide **at least one** support channel (GitHub repository or email) and keep it active.

If a plugin is left unmaintained and the owner doesn't respond after a reasonable notification, Dify may tag it as `Maintenance Lacking` or `Potential Risk`, restrict new installs, and eventually unpublish it.

## Privacy and data

You **must** declare whether your plugin collects personal data and, if so, what types. The full guidelines are in [Privacy Guidelines](/en/3.11.x/develop/plugins/publishing/standards/privacy-protection-guidelines).

Your privacy policy must state:

* What data is collected
* How it is used
* What is shared with third parties (with links to their privacy policies)

Plugins that handle sensitive data (health, finance, children's information) get extra scrutiny. Collecting or transmitting user data without consent is grounds for removal.

## Review and discretion

* Dify may reject or remove plugins that don't meet these requirements or that abuse the review process.
* Reviews aim to land within a reasonable window; turnaround depends on submission volume and complexity.
* Reviewers communicate via the support channel you provide; keep it monitored.

## Related resources

* [Publishing Overview](/en/3.11.x/develop/plugins/publishing/marketplace-listing/release-overview)
* [Publish to Dify Marketplace](/en/3.11.x/develop/plugins/publishing/marketplace-listing/release-to-dify-marketplace)
* [Privacy Guidelines](/en/3.11.x/develop/plugins/publishing/standards/privacy-protection-guidelines)
* [Remote Debugging](/en/3.11.x/develop/plugins/features-and-specs/plugin-types/remote-debug-a-plugin)

***

[Edit this page](https://github.com/langgenius/dify-docs/edit/main/en/develop-plugin/publishing/standards/contributor-covenant-code-of-conduct.mdx) | [Report an issue](https://github.com/langgenius/dify-docs/issues/new?template=docs.yml)