deadbeef.sourceforge.io

DeaDBeeF is a modular, cross-platform audio player for people who want one program to play, convert, tag, and organize a local music library. It runs on GNU/Linux, macOS, Windows, *BSD, OpenSolaris, and other UNIX-like systems, and it is aimed at users who keep audio files on disk rather than in a streaming service. If you want a lightweight player you can reshape with plugins and scripting, DeaDBeeF is built for that; if you need a polished, zero-configuration app, its direct file-and-playlist approach may feel more manual.

What DeaDBeeF actually does

The player covers four core jobs:

• Playback of a wide range of formats, including chiptune and tracker files.
• Conversion between supported audio formats.
• Tag reading and writing, with a dedicated tag editor.
• UI customization, from layout to DSP and playlists.

It is described as modular, meaning features beyond the core player are added through plugins.

Supported formats

DeaDBeeF plays “nearly anything you throw at it,” according to the project. Documented support includes:

If a format is not listed, FFMPEG support is the extension path to check first.

Tags, cuesheets, and metadata

DeaDBeeF reads and writes ID3v1, ID3v2.2, ID3v2.3, ID3v2.4, APEv2, Xing/Info, and VorbisComments tags, and it can read many other metadata formats in most supported file types. It also handles non-Unicode ID3 tags with automatic character set detection, including cp1251, iso8859-1, optional Chinese cp936, SHIFT-JIS, and MS-DOS CP866 for selected formats. Unicode tags (UTF-8 and UCS-2) are fully supported.

For albums stored as single files plus a cuesheet, DeaDBeeF splits them into tracks automatically. It supports embedded and external .cue files, uses heuristics to match audio files with cuesheets, and can extract chapter information from formats such as m4b audiobooks and ogg files.

Organizing a music library

DeaDBeeF takes a direct approach: files are added to the player from the filesystem. You can build multiple playlists using tabs or a playlist browser, and sort or group tracks with advanced Title Formatting scripting that is compatible with Foobar2000. That compatibility matters if you already have Foobar2000 title-format strings you want to reuse.

Sound shaping and playback quality

• 18-band graphical equalizer plus other DSP plugins.
• Highly customizable DSP pipeline with a number of available plugins.
• Gapless playback for correctly encoded files.
• ReplayGain, including a Scanner.
• Album art display, which can be enabled in the player and loaded from image files or from audio files.

When DeaDBeeF is a good fit

Choose DeaDBeeF if you:

• Run Linux, macOS, Windows, or a UNIX-like system and want the same player across them.
• Keep a local library with mixed formats, including chiptunes or tracker modules.
• Want to edit tags, convert formats, and manage cuesheets in the same tool.
• Enjoy customizing the interface and DSP chain through plugins and scripting.

Look elsewhere if you want a player that requires no setup, or if your listening happens mainly through streaming services rather than local files.

Getting started

The project site provides Download, Get Plugins, Screenshots, FAQ, and WIKI sections, plus a GitHub issues tracker. Start with Download for your platform, then Get Plugins for format or DSP extensions. The in-player Help page is the documented place to look for enabling Album Art.

DeaDBeeF reads and writes the major tag formats used across its supported audio types, and it adds two things many players skip: automatic character-set detection for legacy non-Unicode ID3 tags, and a tag editor that accepts custom fields. If your library mixes modern FLAC/Vorbis files with older MP3s carrying Cyrillic, Chinese, or Japanese text, that combination is the practical reason to care about this part of the player.

Tag formats it reads and writes

According to the project's own description, DeaDBeeF can both read and write:

• ID3v1
• ID3v2.2, ID3v2.3, ID3v2.4
• APEv2
• Xing/Info
• VorbisComments

Beyond those, it also reads many other tag and metadata formats across most of the audio types it supports. The distinction matters: read-and-write coverage is what you need for editing your own library, while read-only coverage is enough for playback and display.

Character-set detection for legacy tags

Older MP3s often carry ID3 tags written before Unicode was standard, so the text is stored in a local encoding with no reliable marker saying which one. DeaDBeeF applies automatic character-set detection to non-Unicode ID3 tags. The project lists support for:

The practical effect: a file whose artist or album name shows up as mojibake in a player that assumes one fixed encoding has a better chance of displaying correctly here, because the player attempts to identify the encoding rather than guess once.

Unicode support

Unicode tags are fully supported in both utf8 and ucs2. This covers the modern case — files tagged by current software — so you are not trading legacy compatibility for correct handling of contemporary libraries. Both paths work in the same player.

The tag editor

DeaDBeeF includes what the project describes as a high-quality tag editor with custom fields support. Custom fields are the part worth noting: if you keep non-standard metadata (a mood field, a source field, a catalog number), you can store and edit it rather than being limited to the fixed set of frames a format defines.

Cuesheets and chapters as metadata

Two related features sit alongside tags:

• Cuesheet support — .cue files, both embedded and external, are handled with charset detection and conversion, and DeaDBeeF applies heuristics to match audio files with their cuesheets. Albums are split into tracks automatically.
• Chapter information — can be extracted and used from selected formats, with m4b audiobooks and ogg files given as examples.

If you manage audiobooks or single-file album rips, this is metadata handling in a broader sense: the structure of the content is derived from sidecar or embedded information rather than from separate files.

What this means in practice

Choose DeaDBeeF for tag work if your library is heterogeneous — a mix of formats and eras — and you want one editor to handle both. The read/write list covers the common cases; the charset detection addresses the files that usually cause trouble; Unicode support keeps current files correct.

One caveat to keep in mind: the project notes that cp936 support is optional, so Chinese legacy tags may depend on how your build was compiled. If that specific case matters to you, verify it on your own installation rather than assuming it is always active.

DeaDBeeF plays most common lossy and lossless audio formats out of the box, plus chiptune and tracker module formats, and it can extend coverage further through FFMPEG. If your library is mostly MP3, FLAC, Ogg, AAC/M4A, or WAV, DeaDBeeF will handle it directly. If you collect chiptunes, SID files, or tracker modules, those are also supported natively. For anything outside these lists, the FFMPEG plugin is the fallback.

Natively supported formats

According to the DeaDBeeF project page, the player handles the following without extra plugins:

Common audio formats

• MP3
• Ogg Vorbis
• FLAC
• APE (Monkey's Audio)
• WV / ISO.WV (WavPack)
• WAV
• M4A / M4B / MP4 (AAC and ALAC)
• MPC (Musepack)
• TTA (True Audio)
• CD Audio

Chiptune formats

• NSF
• AY
• VTX
• VGM / VGZ
• SPC
• SID — with HVSC song length database support

Tracker modules

• MOD
• S3M
• IT
• XM
• and other tracker module formats

Extending format support with FFMPEG

The page states that "even more formats" can be played using FFMPEG. This means if a format isn't in the native list above, the FFMPEG plugin is the path to try. The project doesn't enumerate which additional formats FFMPEG unlocks, so treat this as a general extension mechanism rather than a guaranteed list.

Quick reference

What this means for your library

If your collection is standard digital audio — ripped CDs, downloads in MP3/FLAC/AAC/Ogg — DeaDBeeF covers it natively. If you have a mix that includes game music rips or demoscene modules, those are first-class citizens too, not afterthoughts. The main gap to watch for is any format not listed and not covered by your FFMPEG build; in that case, check whether FFMPEG supports it, since that's the extension route DeaDBeeF provides.

DeaDBeeF organizes music with a direct, filesystem-first approach: you add files to the player straight from your disk, then manage them through multiple playlists and scriptable sorting rather than through a managed library database. This suits listeners who already keep their music in folders and want the player to reflect that structure. It also means there is no import-and-index step to wait for — but equally, no automatic library scanning that reorganizes files for you.

Files come straight from the filesystem

DeaDBeeF does not build a separate library catalog. According to the project's own description, "your files are added to the player directly from the filesystem." In practice this means the playlist is a list of file paths, and what you see is what exists on disk. If you move or rename a file outside the player, the playlist entry points at the old location.

This has a few consequences worth knowing before you commit:

• No hidden database. There is no library file that can drift out of sync with your folders.
• You control the structure. Folders, naming, and directory layout are your organizational system.
• Portability. Because playlists reference paths rather than an index, behavior depends on those paths staying valid.

Multiple playlists via tabs or a playlist browser

DeaDBeeF supports multiple playlists, and you can switch between them using tabs or a playlist browser. This is the main way to separate different collections — for example, one playlist per genre, per artist, or per listening context.

The practical pattern is to treat each playlist as a working set rather than a permanent classification. Because files are added directly, you can build a playlist for a specific purpose without touching the underlying files.

Sorting and grouping with Title Formatting

The most powerful part of DeaDBeeF's organization is its sorting and grouping. You can "sort and group the tracks in any order you wish, using advanced Title Formatting scripting, compatible with Foobar2000."

Title Formatting is a scripting syntax that builds display strings and sort keys from track metadata. Two things follow from this:

1. Sorting is metadata-driven, not filename-driven. You can order tracks by album artist, then disc number, then track number, regardless of how files are named.
2. Foobar2000 compatibility matters. If you already have Title Formatting strings from Foobar2000, they are designed to carry over, which lowers the cost of switching.

For example, a grouping scheme that separates albums by artist and orders tracks within each album relies on the same tag fields the player already reads and writes. If your tags are consistent, the grouping works; if they are messy, the grouping exposes that.

Cuesheet support splits albums into tracks

DeaDBeeF has "very nice Cuesheet support, automatically splitting albums into tracks for you." This covers both embedded and external .cue files, with charset detection and conversion.

The details that matter:

• Embedded and external cuesheets are both handled, so single-file album rips with a companion .cue work as expected.
• Smart heuristics match audio files with cuesheet files, which reduces manual pairing.
• Chapter information can be extracted and used from selected formats, such as m4b audiobooks and ogg files.

If you rip an album as one large audio file plus a cuesheet, DeaDBeeF presents it as individual tracks without you splitting the file.

What this means for choosing DeaDBeeF

The trade-off is consistent across all of these: DeaDBeeF gives you direct control and scripting power, and in return expects you to keep your files and tags in order. If your collection is already organized on disk, the player mirrors that organization rather than imposing its own.

DeaDBeeF is a modular, cross-platform audio player for GNU/Linux, macOS, Windows, *BSD, OpenSolaris, and other UNIX-like systems. Its playback and customization features are aimed at listeners who want control over sound, layout, and library behavior rather than a fixed, minimal interface. The features below apply to the standard player; some depend on correctly encoded files or on optional plugins.

Playback features

Gapless playback

DeaDBeeF supports gapless playback for correctly encoded files. This means tracks that are meant to flow into each other — live albums, DJ mixes, classical works — can play without an audible gap, provided the files themselves are encoded in a way that preserves the necessary timing information.

ReplayGain, including the Scanner

ReplayGain support is built in, and it includes the Scanner. ReplayGain normalizes perceived loudness across tracks or albums so you don't have to adjust the volume between songs. The Scanner component lets you analyze files to generate the gain information.

18-band graphical equalizer and DSP plugins

If you want more low-end punch or other tonal adjustments, DeaDBeeF provides an 18-band graphical equalizer along with other DSP (digital signal processing) plugins. The DSP pipeline is highly customizable, and a number of plugins are available to extend it. This is the main route for shaping output beyond simple EQ.

Customization features

Album art display

Album art can be enabled for display. According to the player's own documentation, you turn it on via the Help page inside the player. Artwork can be loaded from image files or from the audio files themselves.

UI customization

DeaDBeeF lets you customize the UI in almost any way you want, and additional plugins can extend it further. The project's own screenshot shows a highly customized DeaDBeeF running on Linux with several additional plugins — so the default look is a starting point, not a limit.

Playlists and track organization

• Files are added directly from the filesystem.
• Multiple playlists are supported using tabs or a playlist browser.
• Tracks can be sorted and grouped in any order using advanced Title Formatting scripting, which is compatible with Foobar2000.

Tags and metadata

DeaDBeeF reads and writes ID3v1, ID3v2.2, ID3v2.3, ID3v2.4, APEv2, Xing/Info, and VorbisComments tags, and reads many other tag/metadata formats in most supported formats. It includes automatic character set detection for non-Unicode ID3 tags (cp1251, iso8859-1, optional Chinese cp936, SHIFT-JIS, MS-DOS CP866 for selected formats), full Unicode tag support (UTF-8 and UCS-2), and a high-quality tag editor with custom fields.

Cuesheet support

Cuesheet (.cue) support includes charset detection and conversion, embedded and external cuesheets, and smart heuristics for matching audio files with cuesheet files. Albums can be automatically split into tracks. Chapter information can also be extracted from selected formats such as m4b audiobooks and ogg files.

What this means in practice

If your priority is accurate, uninterrupted album playback, the gapless and ReplayGain features are the relevant ones. If your priority is shaping sound, the 18-band EQ and customizable DSP pipeline are the tools to look at. If your priority is appearance and workflow, UI customization, tabbed playlists, Title Formatting scripting, and album art cover most needs. Format and tag coverage is broad, so these features are usable across a wide range of audio files rather than being limited to one codec.

For setup details — such as enabling album art — the player's built-in Help page is the authoritative in-app reference.