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.
Choose a Method#
Compare#
| Marketplace | GitHub | Local File | |
|---|---|---|---|
| Audience | Every Dify user | Anyone with the repo URL | People you give the file to |
| Review | Automated risk and package checks + human review | None | None |
| Install path | One click from Marketplace UI | Install from GitHub dialog | Upload via Plugins page |
| Versioning | New package and PR for every version | 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 |
Tip
Many developers ship to GitHub first for fast iteration, then submit to the Marketplace once the plugin is stable. The same .difypkg works for all three methods; only the distribution channel differs.
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.