Skip to main content

Marketplace and Packaging

Plugins are packaged products

The Logitech plugin ecosystem treats plugins as distributable packages that are verified and reviewed before public marketplace release.

1. Package format​

The public docs define the distributable format as:

  • .lplug4

The approval docs and sample repo also reference:

  • plugin metadata,
  • plugin icon in the metadata folder,
  • package verification before submission.

2. Approval flow​

The public marketplace guidelines say:

  1. test the plugin properly,
  2. ensure the icon is present in metadata,
  3. pack the plugin as .lplug4,
  4. submit through the marketplace contribution form,
  5. wait for automated and manual review.

The current guidance also says Logitech may take longer than expected and suggests contacting marketplace@logitech.com if you hear nothing within ten working days after upload.

3. Node.js packaging​

npm run build:pack

4. C# packaging​

logiplugintool pack ./bin/Release/ ./MyPlugin.lplug4
logiplugintool verify ./MyPlugin.lplug4

5. What to test before submitting​

  • plugin installs cleanly,
  • actions appear in Installed Plugins,
  • actions work through Actions Ring or supported devices,
  • settings survive restarts,
  • the plugin behaves correctly on supported OS versions,
  • icons and metadata are complete,
  • no local-only development paths leak into the package.

6. What this means for you​

If you want a private desk workflow, Smart Actions may be enough.

If you want a real reusable integration for MX Keys and MX Master 3, the marketplace plugin path is now real and public.