> ## 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.

# Publish Plugins

> Three ways to distribute a Dify plugin (Marketplace, GitHub repository, or local file) and how to pick the right one

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](https://enterprise-docs.dify.ai/en/3.13.x/develop/plugins/publishing/standards/contributor-covenant-code-of-conduct.md).

## Choose a Method

> [card] [Marketplace](https://enterprise-docs.dify.ai/en/3.13.x/develop/plugins/publishing/marketplace-listing/submit-plugin-to-marketplace.md)
>
> Official catalog. Reviewed, trusted, one-click install for every Dify user.

> [card] [GitHub Repository](https://enterprise-docs.dify.ai/en/3.13.x/develop/plugins/publishing/marketplace-listing/release-to-individual-github-repo.md)
>
> Self-hosted on GitHub. No review; users install via repo URL.

> [card] [Local File](https://enterprise-docs.dify.ai/en/3.13.x/develop/plugins/publishing/marketplace-listing/release-by-file.md)
>
> 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** | 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**.

## Related Resources

> [card] [Plugin Development Guidelines](https://enterprise-docs.dify.ai/en/3.13.x/develop/plugins/publishing/standards/contributor-covenant-code-of-conduct.md)
>
> Quality bar for Marketplace submissions.

> [card] [Privacy Guidelines](https://enterprise-docs.dify.ai/en/3.13.x/develop/plugins/publishing/standards/privacy-protection-guidelines.md)
>
> `PRIVACY.md` and data-disclosure requirements.

> [card] [General Specifications](https://enterprise-docs.dify.ai/en/3.13.x/develop/plugins/features-and-specs/plugin-types/general-specifications.md)
>
> Manifest fields every plugin must set.

> [card] [Getting Started](https://enterprise-docs.dify.ai/en/3.13.x/develop/plugins/getting-started/getting-started-dify-plugin.md)
>
> New to plugins? Start here.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.