EmDash plugins: registry directory

What are EmDash plugins?

EmDash plugins extend your site with publishing workflows, admin tools and integrations. They can respond to content changes, store plugin data, expose settings, add dashboard widgets, serve API routes and connect to external services.

The public registry is the supported catalog for sandboxed plugins. Each package has a public name combining its publisher’s handle and package slug, such as @peachfinthemes.com/auto-unpublish-posts. Native plugins install through your project’s npm dependencies and configuration.

All EmDash plugins by category

The registry includes plugins for publishing, SEO, media, forms, email and analytics. Some names appear more than once because different publishers use the same name. Check the linked handle before installing.

New listings include commerce and payment integrations for product catalogs and checkout, alongside cookie consent, accessibility tools and moderated reviews. Other additions provide announcement bars, tables of contents, polls, reaction buttons, knowledge bases and content synchronization.

How to install an EmDash plugin

Registry installation requires an administrator account with plugins:manage permission, configured storage for downloaded bundles and an available sandbox runner.

Set up the sandbox for your runtime

On Cloudflare Workers, the sandbox requires the Workers Paid plan, a worker_loaders binding named LOADER in wrangler.jsonc, and a Worker entry point that exports PluginBridge. Import sandbox from @emdash-cms/cloudflare and set sandboxRunner: sandbox() inside the emdash() integration in astro.config.mjs. The sandbox bridge uses the D1 binding named DB; sandboxed plugins are not available on a Hyperdrive deployment. Follow the platform setup instructions before deploying.

On Node.js, install the runner and its runtime dependency with npm install @emdash-cms/sandbox-workerd workerd. Set sandboxRunner: "@emdash-cms/sandbox-workerd/sandbox" inside emdash() in astro.config.mjs. Install with optional dependencies enabled on the platform where the server runs, so the correct workerd binary is available. The Node.js sandbox instructions cover deployment and troubleshooting.

If installation returns SANDBOX_NOT_AVAILABLE, the runner is missing or unavailable. Check the server’s error message, fix the runner configuration or runtime dependency, and redeploy.

Install and configure a registry plugin

1. Open Registry in the EmDash admin.
2. Search for a plugin by title, description or complete public name, then open its details.
3. Choose a release and review its publisher, metadata, verification status and requested permissions.
4. Select Install, then review and confirm the consent dialog.
5. Open Plugins to configure or disable the installed package. Follow its setup instructions for any required service accounts or credentials.

EmDash checks the downloaded bundle’s checksum, name, version and permissions before installation. The consent dialog also identifies routes exposed as Model Context Protocol (MCP) tools when the plugin declares them. Review each permission: access such as content:write permits changes to your content.

Install a native or config-managed plugin

Native plugins run inside your site’s process and can provide React admin components, Portable Text renderers and HTML fragments for public pages. Install the npm package, follow its instructions to register it under plugins: [] in the emdash() configuration in astro.config.mjs, then deploy. Treat native code as trusted application code.

Config-managed sandboxed plugins also install through npm, but use sandboxed: [] and require the sandbox runner. Config-managed plugins change when you update the dependency and deploy; they cannot be installed or removed from the admin panel.

Read each package’s installation notes. The Custom 404 registry entry installs an information page; its working 404 implementation is a separate native npm plugin. The marketplace-test package is a development fixture for registry, consent, runtime and admin testing.

Are EmDash plugins free?

The registry is free to browse and install from. Some publishers sell additional features separately, and external services or hosting can have their own costs. Check each package’s license and service requirements.

Our Auto Unpublish Posts plugin can unpublish, trash or retag posts on a date, with collection defaults and email alerts. Our Comment Spam Protection plugin applies rules for blocked words, links, language, duplicates and rate limits on your site, with a reason for each decision. Both have free registry editions and separate Pro upgrades.

Our free Instant Indexer notifies participating search engines through IndexNow when public pages are added, changed or removed.

How to judge an EmDash plugin

• Publisher and review status: check the account handle, registry labels and installation verification. Registry moderation screens listing text, links and images. A listing review does not guarantee the safety of all the plugin’s code.
• Version and last update: read the release notes and required EmDash version. Check whether an upgrade needs configuration or data changes.
• License and costs: read the publisher’s license and identify any paid upgrades, external accounts or service fees.
• Source repository: follow the listing’s source link where supplied. Look for installation instructions, issue reports and maintained releases.
• Permissions and fit: compare the requested access with the job you need done. Approved permissions authorize real operations, even when a plugin runs in a sandbox.

If a required integration is missing or a plugin’s maintenance is unclear, resolve that dependency before committing a site to it. Choosing a theme does not replace checking each plugin’s installation and rendering requirements.

For the site design, our 40 Astro themes with EmDash editions use plain Markdown content by default, with optional EmDash CMS support. The Astro Pass includes the full Astro theme collection.

Registry listings and updates

The public EmDash registry contains 88 packages from 46 publisher identities as of 16 October 2026. New releases, additions and removals appear in the live registry.

To update a registry plugin, open Plugins, select Check for updates, then Update and review the consent dialog. Updates require fresh confirmation when they add permissions or MCP tools, or change a route from authenticated to public. The installed version stays in place until you approve the change.

To remove a registry plugin, expand it under Plugins and select Uninstall. Stored plugin data remains by default. Select Also delete plugin storage data only if you do not need it for a later reinstall.

For the wider ecosystem, see EmDash statistics. For core compatibility and upgrade dates, use the EmDash release tracker.

Frequently asked questions

How many EmDash plugins are in the registry?

The public registry contains 88 packages from 46 publisher identities as of 16 October 2026. This includes a development fixture and an informational package.

Source: public registry API.

How do I install an EmDash plugin?

Registry installs require an administrator with plugin-management permission, configured bundle storage and an available sandbox runner. Open Registry, choose a plugin and release, review its publisher, verification status and permissions, then confirm installation. Open Plugins to configure it.

Source: installation guide.

Are all EmDash plugin features free?

The registry is free to browse and install from, but some publishers sell paid upgrades separately. Peachfin offers free editions of Auto Unpublish Posts and Comment Spam Protection with separate Pro upgrades. External services and hosting can also have costs.

Sources: registry, Auto Unpublish Posts and Comment Spam Protection.

What is the difference between sandboxed and native plugins?

Sandboxed plugins run in a separate runtime with declared API access. Cloudflare Workers requires the Workers Paid plan and Worker Loader; Node.js uses @emdash-cms/sandbox-workerd with workerd. Native plugins run inside the site process and install through npm and astro.config.mjs, followed by deployment.

Sources: plugin overview and plugin sandbox setup.