Dify supports three ways to distribute a plugin. They differ in how much vetting happens up front and how broad an audience the plugin reaches. Before publishing, finish development and testing, and read the Plugin Development Guidelines.Documentation Index
Fetch the complete documentation index at: https://docs.dify.ai/llms.txt
Use this file to discover all available pages before exploring further.
Choose a method
Marketplace
Official catalog. Reviewed, trusted, one-click install for every Dify user.
GitHub Repository
Self-hosted on GitHub. No review; users install via repo URL.
Local File
A
.difypkg file you hand off directly. Right for private or internal plugins.Compare
| Marketplace | GitHub | Local File | |
|---|---|---|---|
| Audience | Every Dify user | Anyone with the repo URL | People you give the file to |
| Review | Yes: 12 automated checks + human review | None | None |
| Install path | One click from Marketplace UI | Install from GitHub dialog | Upload via Plugins page |
| Versioning | New PR per version, automated workflow available | GitHub releases with .difypkg asset | Repackage and redistribute |
| Best for | Polished, broadly useful plugins | Open-source projects, internal tools shared by URL | Private plugins, internal testing, ad-hoc distribution |
Quick rules of thumb
- Want broad reach and review? Use the Marketplace.
- Want full control over releases and versioning? Use GitHub.
- Private or one-off use? Use a Local File.
Related resources
Plugin Development Guidelines
Quality bar for Marketplace submissions.
Privacy Guidelines
PRIVACY.md and data-disclosure requirements.General Specifications
Manifest fields every plugin must set.
Getting Started
New to plugins? Start here.
Edit this page | Report an issue