Keep File Locations Unchanged in MusicBrainz Picard

MusicBrainz Picard makes it possible to update your audio file tags in place—without moving your files from their current folders. By configuring its file moving and renaming settings with care, you can safely refresh metadata while ensuring the integrity of your library paths. This is especially important if you rely on playlists or external links that expect files to be found in specific locations.

Quick facts from the official docs

Picard treats moving and renaming as entirely separate actions. When you save, enabling "Move files when saving" will relocate your songs into a new directory as defined by your destination path setting. In contrast, "Rename files when saving" only affects names—adjusting the filename (or subdirectories as defined in your naming string) but leaving files in their existing parent directory if moving is disabled. Both options draw on Picard’s file naming string, with the portion before the last slash (/) treated as the potential target folder and everything after as the new filename. From Picard 2.7 onward, you can manage multiple renaming scripts and select among them using the File naming script editor. Picard also allows for patterns such as Folder.jpg or *.cue to be listed alongside music files for moving, though this has no effect if file moving is left disabled.

Set Picard to tag in place

1. Open Picard and go to Options > File Naming.
2. Ensure Move files when saving is unchecked. This keeps all music files in their current folders during tag updates.
3. Decide whether you want Rename files when saving enabled. Turning this on lets Picard adjust filenames or the subdirectory structure as defined by your naming template, but will not change the parent directory if moving is unchecked. Assess the preview output in the options to confirm the effect of your choices.
4. If supported by your Picard version (2.7+), select or customize your file naming script using the Active file naming script selector, and review the Before/After examples visible in the dialog.

Retain playlist and external links

Playlists and media managers reference files by their full path. To ensure these links do not break:

• Avoid altering directory structures or parent folder names that your playlists or applications depend on.
• If you want only filenames to change, configure your naming script to affect only the portion of the path after the final /. Picard interprets anything before the last slash as a move target; so with file moving off, changes before the slash are ignored.
• For maximum assurance, record or export a list of original file paths for comparison. After tagging, compare to verify that paths remain unchanged.

Test on a small copy first

Before processing your entire music collection, verify on a representative sample:

1. Copy a handful (5–20) of audio files—including different albums and any important non-music files (for example, cover.jpg, cue sheets)—into a temporary folder.
2. Open these files in Picard, confirm Move files when saving is unchecked, and save the changes. Examine the changes on these copies, not the originals.
3. Check metadata for updates, confirm file paths are unchanged (crucial for playlist reliability), and verify the filename outcome if renaming is enabled. If you defined additional file patterns, observe whether those files stayed put as intended.

Handle additional files and empty folders

Options for moving supplementary files—such as *.jpg, *.png, or named subdirectories—will only have an effect if "Move files when saving" is enabled. When keeping files in place, these patterns are ignored and all associated files remain where they are. The "Delete empty directories" option only comes into play after a completed file move; if moving is turned off, no directories are deleted, preserving your existing folder structure entirely.

Verify and reconcile after saving

1. Use your file manager or a script to compare the full file paths before and after tagging. This step is for verification and does not alter your audio files.
2. Test at least one playlist that should reference altered files. If playback fails, compare the playlist file path to the actual new file path to spot differences.
3. If only filenames changed and playlist referencing matters, use a batch editor to revise affected playlist entries or regenerate playlists to reflect your new naming convention.

Example: test run

Imagine you copy five MP3s from two separate album folders into C:\temp\picard-test. Inside Picard, you make sure Move files when saving is unchecked but enable Rename files when saving with a script like %artist% - %title%. After saving, all files in C:\temp\picard-test have refreshed metadata and their directory path is unchanged; a playlist referencing their original location continues to work since the parent folders were not touched.

For managing composer, performer, or original release date details later, refer to these guides: Composer, Performer and Conductor Tags in Music Files and Original Release Dates and Reissue Dates in Music Tags.

Best practice: Always test your settings on a small sample first, confirm results carefully, and proceed to batch processing only once you are confident paths and playlists are unaffected.