🎵 Music Tagger

A minimal VS Code extension to edit audio tags directly from the Explorer. Supports MP3, MP4/M4A, Opus, OGG, FLAC, WAV, and AIFF — using ID3v2, MP4 atoms, or Vorbis Comments as appropriate for each format.

Install from Visual Studio Marketplace Install from Open VSX Registry

✨ Features

• Works across MP3, MP4/M4A/M4B, Opus, OGG, FLAC, WAV, and AIFF, using one consistent set of fields regardless of the underlying tagging format
• Edit common fields — Title, Artist, Album, Album Artist, Genre, Year, Track/Disc Number, Composer, Comment, Lyrics, Publisher, Copyright, BPM, ISRC, and more
• Built-in audio player so you can listen while you tag; in folder mode it follows whichever file is selected
• Select a folder to load every supported audio file recursively
• Folder mode includes:
  • A summary section that shows Multiple values when tags differ across files
  • A per-file editable view so each track can be adjusted individually
  • Editing a field in the summary immediately applies that value across all loaded files
  • A file filter input for quickly narrowing large folders
• Embedded artwork preview, including a fanned cover-art stack when files in a folder carry different covers
• Long-form fields (lyrics, comments) shown as full auto-growing text areas instead of single-line inputs
• Multi-value fields (Artist, Genre, Composer, Album Artist) accept several values separated by ;

🚀 Usage

1. In the Explorer, right-click a supported audio file (.mp3, .mp4, .m4a, .m4b, .m4p, .opus, .ogg, .oga, .flac, .wav, .aiff, .aif) or a folder
2. Choose Music Tagger: Edit Tags
3. Edit values in the tag editor
4. Click Save

You can also run Music Tagger: Edit Tags from the Command Palette.

Music Tagger also registers as an alternate editor for these file types. Right-click a file and choose Open With... → Music Tagger to open it directly without going through the context menu command.

Opening files directly by default

By default, double-clicking a supported audio file still opens VS Code's built-in audio player, and Music Tagger is only available via "Open With...". To make Music Tagger the default editor for a given extension instead, add this to your user or workspace settings.json:

"workbench.editorAssociations": {
  "*.mp3": "music-tagger.tagEditor",
  "*.flac": "music-tagger.tagEditor"
}

With this set, double-clicking a matching file opens the tag editor directly instead of the audio player tab. You don't lose playback either way — Music Tagger has its own built-in player. Note this only opens a single file at a time — folder-wide bulk tagging still requires the context menu command.

🔧 Extension Settings

This extension contributes no settings of its own, but honors VS Code's built-in workbench.editorAssociations setting described above.

⚠️ Known Issues

• Embedded artwork is read-only; it isn't editable from the UI
• Format-specific or non-standard fields (e.g. custom TXXX frames) aren't exposed — only the common fields shared across formats are editable
• WAV files can carry both a RIFF INFO tag and an ID3v2 tag; some fields are written to both for maximum compatibility with other tools, which may show up as duplicated values in tools that read both

None currently beyond the above. If you encounter any issues, please report them on GitHub.

📝 Notes

• Empty fields are written as empty tag values
• Multi-value fields (Artist, Genre, Composer, Album Artist) are edited as a single ;-separated string and split into individual values on save

Enjoy! 🎵