Integrations /Build Plugins /

Build Plugins

Netlify Build Plugins are integrations that extend the functionality of the Netlify Build process. You can install plugins made by others, or write your own. You can save them locally in your repository, or share them with others.

Build Plugins expand what your Netlify builds are capable of. For example, you can use plugins to:

  • speed up builds by optimizing and debugging your build cache
  • import and convert data from external sources
  • check for broken links in a site after building
  • analyze and optimize site asset handling for better runtime performance
  • generate content like sitemaps, RSS feeds, and search indexes

# Install a plugin

To get a sampling of what plugins can do, visit Integrations in the Netlify UI at the team or site level. You’ll find different types of integrations, including plugins from our partners as well as plugins from the community. Plugins can be installed directly from the Netlify UI. They can also be installed using the Netlify configuration file, which allows more configuration options. Netlify automatically installs plugins or runtimes recommended for certain frontend frameworks when you link a repository for a new site.

Use a compatible Node.js version

For optimum compatibility while developing or running plugins, we recommend using the default version of Node.js installed by Netlify. However, you can also specify a different version for your project’s setup, if needed.

# UI installation

  1. In the Netlify UI, select the Integrations tab from any team-level or site-level page.
  2. Search or browse for the plugin you want.
  3. Select Enable.
  4. Follow the installation guidance in the Netlify UI to install the plugin on a site. You may be prompted to add build environment variables required by the plugin.
  5. To use your new plugin, visit the Deploys tab for your site and select Trigger deploy.

Consider the context

UI-installed plugins run in all deploy contexts. To limit the context for the plugin, consider using file-based installation instead.

# Required environment variables

Though many plugins that can be installed using the Netlify UI require no configuration for default operation, some may require you to set one or more build environment variables for your site during or after installation. Refer to the plugin’s documentation, linked from Options menu in the plugin’s listing.

# File-based installation

File-based plugin installation allows advanced plugin configuration.

You can use file-based installation for either of the following:

  • installing local plugins that you write and store in your repository
  • accessing a wide selection of plugins published by the community on npm

In both cases, you configure settings in netlify.toml. For a plugin published to npm, you also add it as a dependency. Then you can test or run the plugin as part of a build.

# Configure settings

To run a plugin during your build, add it to a Netlify configuration file stored in your site’s base directory. A plugin configured globally with [[plugins]] runs in all deploy contexts, but you can also configure a plugin by deploy context.

Here’s a sample configuration with two plugins installed in all deploy contexts.

# Configuration for a plugin published to npm
package = "netlify-plugin-lighthouse"

  output_path = "reports/lighthouse.html"

# Configuration for a local plugin
package = "/plugins/netlify-plugin-hello-world"

Each [[plugins]] entry accepts two keys:

  • package (required):
    • for a plugin installed from npm, the npm package name of the plugin.
    • for a local plugin, the absolute path to a directory containing the plugin’s index.js and manifest.yml files. The package value for a local plugin must start with . or /.
  • inputs: custom settings that the plugin author may specify as required or available for configuring the plugin. To specify inputs per deploy context, refer to configure by deploy context.

For npm-published plugins, you can find these details in each plugin’s package documentation on the npm Public Registry.

Sometimes order matters

Different plugins run during different stages of your build. When multiple plugins are set to run in the same stage, they will run in the order they are listed in the Netlify configuration file. An npm-published plugin’s README should indicate if order is important to that plugin’s functionality.

# Configure by deploy context

Using specific settings in your Netlify configuration file, you can limit a build plugin to run in a certain deploy context only, or you can configure a plugin’s inputs settings differently per context.

Here’s an example configuration that runs the Sitemap plugin in the context of production deploys only.

# Use double brackets since `plugins` is an array of tables.
package = "@netlify/plugin-sitemap"

And here’s an example configuration that runs the Cypress plugin differently based on deploy contexts.

# Use Cypress plugin for this site.
# This section, by itself, configures the plugin
# for all deploy contexts (production, branch deploys, Deploy Previews).
package = "netlify-plugin-cypress"
  record = true

# Don’t record Cypress tests in Deploy Previews.
# Since this entry is more specific, it overrides the entry above.
# `context.deploy-preview.plugins` and `package` must be included.
package = "netlify-plugin-cypress"
  # Use single brackets since `inputs` is an object property
  record = false

This configuration records test results and artifacts on the Cypress Dashboard for production and branch deploys only, not Deploy Previews.

UI-installed plugins run on all contexts

To limit a plugin to certain deploy contexts, ensure that you’ve configured the plugin for your site using file-based installation only and not UI installation.

# Next steps

If you’re installing a local plugin, you can run and test it after configuration. Otherwise, you’ll add a dependency to package.json.

# Add dependency

For a plugin from npm, there’s an additional step beyond editing the Netlify configuration file. You must use npm, yarn, or another Node.js package manager to add the plugin to devDependencies in your site’s package.json.

Evaluate the plugin code

Plugins available on npm but not yet listed in the Integrations Hub have not been reviewed or approved by Netlify staff. Review plugin code for security concerns before installing.

From your project’s base directory, use a command like this to add the dependency:

# Replace `BUILD_PLUGIN_NAME` with a real plugin name, 
# like `netlify-plugin-lighthouse`
npm install -D BUILD_PLUGIN_NAME
# Replace `BUILD_PLUGIN_NAME` with a real plugin name, 
# like `netlify-plugin-lighthouse`

# Run and test

When you save your changes to your repository and push them to your Git provider, the build that’s triggered on Netlify will run with plugins installed for that deploy context. If you would like to test a plugin before running it in a production build, you can use a branch deploy or Deploy Preview, or you can run the build locally with Netlify CLI.

# Automatic installation

When you link a repository for a new site, Netlify runs a framework detection utility to determine whether your site uses a particular frontend framework. Certain frameworks have recommended Build Plugins or runtimes. These help extend the functionality of the Netlify Build process to support key framework-specific features. Recommended plugins and runtimes may have site conditions requirements, such as a minimum Node.js version.

If your new site uses a framework with recommended plugins or runtimes, Netlify checks whether these are already installed in a Netlify configuration file. If not, Netlify automatically installs them. These automatically installed plugins run in all deploy contexts.

For an existing site that’s already linked to Netlify, you can choose to install framework-specific recommended plugins yourself.

# Manage plugin versions

Netlify encourages plugin authors to regularly update functionality and release new versions using semantic versioning. Minor plugin version updates introduce only backward compatible new features, while major plugin version updates can introduce breaking changes. Refer to the plugin’s changelog, linked from the Options menu for the plugin listing in the Netlify UI, for version details.

The steps for managing plugin versions for your site depend on the plugin installation method.

For plugins installed in the UI or installed automatically, Netlify updates your site for minor plugin version releases automatically. To manage major plugin updates for a site, take the following steps:

  1. Go to your site’s page.
  2. Search or browse to find the plugin you want to manage.
  3. Select .
  4. Select the desired major version.
  5. Select Change version to save.

Subsequent builds will use the plugin version that you’ve chosen and confirmed.

For plugins installed through file-based installation, you can manage versions in your site’s package.json file under devDependencies.

# Remove a plugin

The steps for removing a plugin depend on how it was installed or whether it is an Essential Gatsby or Next.js Runtime plugin.

For plugins installed in the UI or installed automatically:

  1. For your selected site, go to Integrations > Enabled.

  2. Find the plugin you want to remove.

  3. In the plugin’s card select Disable.

    Subsequent builds will not use the uninstalled plugin and environment variables entered for this integration will not be deleted.

For plugins installed through file-based installation:

  1. Open your site’s netlify.toml.

  2. Delete or comment out the plugin’s configuration fields.

    When you push your committed changes, the resulting build will run without the plugin. If you’re removing an npm-published plugin and want to avoid installing code you won’t use, you can uninstall the plugin package using npm.

Plugin not uninstalling correctly? Check for conflicting configurations

It’s possible to configure a plugin both in the Netlify UI and your site’s netlify.toml — though the configuration file takes precedence. If you follow the above steps to remove a plugin from netlify.toml and the plugin is still installed, make sure it’s not also configured in the Netlify UI, and vice versa. Removing the plugin from one does not automatically remove it from the other.

For the Essential Gatsby and Next.js Runtime v4 plugins:

  1. For your selected site, go to .
  2. In Build configuration, find your plugin in the Runtime field and select Remove.

# Create a plugin

Once you’ve had a chance to try out plugins, you may want to make one of your own. To learn how, visit the create plugins doc.

A new way to build deep integrations

Visit the Netlify SDK docs to learn about new tools and options for building Netlify Integrations. With the SDK, you can make an integration that interacts with more parts of the Netlify platform than a build plugin can. This new toolset also provides a streamlined experience for both integration developers and integration users.

# Get help

Netlify Build Plugins are created by our partners and developers at Netlify and in the community. If you need help with a plugin, contact the plugin author by submitting an issue on the plugin repository. For plugins in the Netlify UI, you can find a link to the plugin issues under the Options menu for the plugin listing. If a plugin author doesn’t respond to an issue within a week, you can request deactivation of the plugin from the Netlify UI.

For more general questions, or to discuss Build Plugins with other members of the community, visit the Netlify Support Forums.

# More Build Plugins resources