Plugins extend beets’ core functionality. They add new commands, fetch additional data during import, provide new metadata sources, and much more. If beets by itself doesn’t do what you want it to, you may just need to enable a plugin—or, if you want to do something new, writing a plugin is easy if you know a little Python.

To use one of the plugins included with beets (see below for a list), just use the plugins option in your config.yaml file, like so:

plugins: mygreatplugin someotherplugin

The value for plugins can be a space-separated list of plugin names or a YAML list like [foo, bar]. You can see which plugins are currently enabled by typing beet version.

Autotagger Extensions


Path Formats

  • Inline Plugin: Use Python snippets to customize path format strings.
  • Rewrite Plugin: Substitute values in path formats.
  • The Plugin: Move patterns in path formats (i.e., move “a” and “the” to the end).



Other Plugins

In addition to the plugins that come with beets, there are several plugins that are maintained by the beets community. To use an external plugin, there are two options for installation:

  • Make sure it’s in the Python path (known as sys.path to developers). This just means the plugin has to be installed on your system (e.g., with a script or a command like pip or easy_install).
  • Set the pluginpath config variable to point to the directory containing the plugin. (See Configuration.)

Once the plugin is installed, enable it by placing its name on the plugins line in your config file.

Here are a few of the plugins written by the beets community:

  • beetFs is a FUSE filesystem for browsing the music in your beets library. (Might be out of date.)
  • A cmus plugin integrates with the cmus console music player.

Project Versions

Table Of Contents

Previous topic


Next topic

Chromaprint/Acoustid Plugin

This Page