> ## Documentation Index
> Fetch the complete documentation index at: https://dify-6c0370d8-docs-new-agent-experience.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Package as Local File and Share

> Package a Dify plugin into a `.difypkg` file you can install directly or hand off to others, with no marketplace or GitHub release required

A `.difypkg` is the portable form of a Dify plugin. Once you have one, anyone can install it through the Plugins page by uploading the file. This is the right path for **private plugins**, **internal testing**, or **out-of-band distribution** to a small group.

For wider distribution, see the [Publishing Overview](/en/develop-plugin/publishing/marketplace-listing/release-overview).

## Prerequisites

* The [Dify Plugin CLI](/en/develop-plugin/getting-started/cli) installed. Run `dify version` to confirm.
* A completed plugin project. If you haven't built one yet, start with the [Tool Plugin walkthrough](/en/develop-plugin/dev-guides-and-walkthroughs/tool-plugin).
* The plugin tested with [remote debugging](/en/develop-plugin/features-and-specs/plugin-types/remote-debug-a-plugin) before packaging.

<Note>
  The `author` field in `manifest.yaml` and every `provider/*.yaml` must match your GitHub handle. Mismatches cause `plugin_unique_identifier is not valid` at install time. See [General Specifications](/en/develop-plugin/features-and-specs/plugin-types/general-specifications) for the full manifest spec.
</Note>

## Package the Plugin

<Steps>
  <Step title="Move above the project">
    Navigate to the directory **above** your plugin project (so the project is a subdirectory of the current working directory).
  </Step>

  <Step title="Run the packager">
    ```bash theme={null}
    dify plugin package ./your_plugin_project
    ```

    The CLI produces a `your_plugin_project.difypkg` file in the current directory.
  </Step>
</Steps>

<Frame>
  ![Generated Plugin File](https://assets-docs.dify.ai/2024/12/98e09c04273eace8fe6e5ac976443cca.png)
</Frame>

## Install from the File

<Steps>
  <Step title="Open the Plugins page">
    In Dify, click the **Plugins** icon in the top-right corner.
  </Step>

  <Step title="Choose Install Plugin > Via Local File">
    Or drag the `.difypkg` onto the empty area of the Plugins page.
  </Step>

  <Step title="Confirm the install">
    Review the permissions the plugin requests, then click **Install**.
  </Step>
</Steps>

<Frame>
  ![Install Plugin File](https://assets-docs.dify.ai/2024/12/8c31c4025a070f23455799f942b91a57.png)
</Frame>

<Check>
  The plugin is now in the workspace and ready to use in Agents, Workflows, or Tools. No further action required.
</Check>

<Warning>
  Self-hosted Dify enforces signature verification by default. Unsigned `.difypkg` files installed via Local File will be rejected unless you sign them or change the verification setting. See [Third-Party Signature Verification](/en/develop-plugin/publishing/standards/third-party-signature-verification).
</Warning>

## Share the File

Hand the `.difypkg` file to your users directly: over email, an internal file share, or any channel you control. They install it with the same flow above.

If you want broader distribution instead, consider:

<CardGroup cols={2}>
  <Card title="Publish on GitHub" icon="github" href="/en/develop-plugin/publishing/marketplace-listing/release-to-individual-github-repo">
    Attach the `.difypkg` to a GitHub release; users install via repo URL.
  </Card>

  <Card title="Submit to Marketplace" icon="store" href="/en/develop-plugin/publishing/marketplace-listing/release-to-dify-marketplace">
    Open a PR against `langgenius/dify-plugins` for the official catalog.
  </Card>
</CardGroup>

## Related Resources

* [Publishing Overview](/en/develop-plugin/publishing/marketplace-listing/release-overview)
* [Dify Plugin CLI](/en/develop-plugin/getting-started/cli)
* [Remote Debugging](/en/develop-plugin/features-and-specs/plugin-types/remote-debug-a-plugin)
* [Third-Party Signature Verification](/en/develop-plugin/publishing/standards/third-party-signature-verification)
* [General Specifications](/en/develop-plugin/features-and-specs/plugin-types/general-specifications)