Skip to main content
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

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
AudienceEvery Dify userAnyone with the repo URLPeople you give the file to
ReviewYes: 12 automated checks + human reviewNoneNone
Install pathOne click from Marketplace UIInstall from GitHub dialogUpload via Plugins page
VersioningNew PR per version, automated workflow availableGitHub releases with .difypkg assetRepackage and redistribute
Best forPolished, broadly useful pluginsOpen-source projects, internal tools shared by URLPrivate plugins, internal testing, ad-hoc distribution
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.

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