Use Option Profiles for Different Music Tasks in Picard

At a glance

Option profiles in MusicBrainz Picard 2.7+ let users switch between sets of option settings tied to repeatable music tagging workflows. Profiles manage selected settings without altering saved tags or creating separate libraries. Users should keep profiles narrow, task-focused, and verify active settings before batch processing to avoid mistakes.

In this guide

1. What profiles change
2. Plan task profiles
3. Create and order profiles
4. Check active settings
5. Example weekend workflows
6. Avoid common mistakes
7. Profile checklist

Option profiles in MusicBrainz Picard 2.7 and later are for switching selected option settings between repeatable workflows. They are not separate music libraries, and they do not undo tag edits after files have been saved. Treat a profile as a reusable layer of Picard options: check which profile is active, check which settings it controls, and test on copied files before using it on a large batch.

What profiles change

An option profile changes only the settings attached to that profile. Picard evaluates enabled profiles in stack order and uses the first enabled profile that manages the requested option. If no enabled user profile manages that option, Picard falls back to the normal user settings profile.

That makes profiles useful for tasks you repeat but do not want to reconfigure by hand each time. For example, one task might use a particular destination and file naming setup. Another might use different values for the same managed options. A third might leave those options to user settings and manage only a small, separate set of choices.

The profile does not store your loaded albums, your file list, or a private copy of your collection. It stores option values for the options you assign to it. If you load files, change tags, and save them, disabling the profile afterward changes future settings, not the saved files. Use duplicates when comparing outcomes.

Plan task profiles

Before creating profiles, list the tasks you actually repeat. Avoid making a profile for every album type if the option values are the same. A small profile set is easier to inspect and less likely to cause confusion when profiles overlap.

Useful task-based profiles might include:

• Main output: a workflow for the destination and naming settings you use most often, if those differ from your base user settings.
• Temporary test output: a workflow that sends processed copies somewhere easy to inspect before you touch a larger folder.
• Portable copy output: a workflow for duplicate files intended for another folder structure.
• Special project: a workflow for a recurring project where only a few Picard options need different values.

Keep profiles narrow where possible. If a profile is meant to change only output location and naming, attach only the relevant options rather than unrelated groups. Narrow profiles make highlighted settings easier to understand and reduce accidental overrides.

Give profiles task names, not mood names. Portable copy output or Test destination is more useful than New profile when you return to Picard months later. Also write down why the profile exists, which options it manages, and what evidence would show that it is working correctly.

Create and order profiles

Picard manages profiles from Options ‣ Options… on the Option Profiles page. There you can create profiles, select the options they manage, enable or disable them, and set their stack order. The normal user settings profile is always underneath and remains enabled.

Use this setup sequence for a new workflow profile:

1. Open the profile page: go to Options ‣ Options… and select Option Profiles.
2. Create a profile: use New, then rename it with a clear task name.
3. Select managed options: choose only the option groups or individual options that this workflow should control.
4. Place it in the stack: put the profile above any lower-priority enabled profile that manages the same options.
5. Enable intentionally: enable the profile you want for the current task and disable profiles that should not affect it.
6. Set values carefully: open the relevant option pages, confirm that controlled settings are highlighted, make the changes, and save with Make It So!.

You can quickly enable or disable profiles from Options ‣ Enable/disable profiles on Picard’s main screen. Use the full Option Profiles page when you need to change which options a profile manages or where it sits in the stack.

Check active settings

The most important habit is to verify the active settings before processing files. Profiles are stacked, so two enabled profiles can manage the same option. In that case, the enabled profile higher in the stack supplies the value.

Use these checks before a serious batch:

1. Look for highlighted options: highlighted settings on option pages are controlled by enabled profiles.
2. Hover for control details: hovering over a highlighted option identifies which profile currently controls it.
3. Check assigned values: on the profile page, hover over a profile option setting to see the value assigned there.
4. Use Attached Profiles: where available, click Attached Profiles to see which profiles manage options on that page and whether they are enabled.
5. Review stack order: if a value is unexpected, check whether another enabled profile above the intended one manages the same option.
6. Save deliberately: Make It So! saves option settings from all pages. Highlighted options go to the first enabled profile that controls them. Other options go to user settings.

This checking process does not change audio files by itself. It is a way to diagnose profile behavior before saving tag changes. If you are also reviewing album matches, combine this habit with a careful matching pass such as matching music files to album tracks in Picard.

Example weekend workflows

Example, fictional: Nora keeps one main folder for carefully tagged albums and a duplicate folder for music copied elsewhere. She does not want two Picard libraries. She wants two repeatable Picard tasks.

For normal work, Nora relies mostly on user settings and one narrow profile called Main output. That profile manages only the settings she deliberately wants separated from the base configuration. For copies, she creates Copy output, which manages the destination and related naming choices she needs for the duplicate folder. She keeps Copy output disabled unless she is working on copied files.

On Saturday, Nora wants to process five copied albums. She first creates a small test folder containing one copied album. In Picard, she enables Copy output and checks the relevant option pages. The settings she expects to be profile controlled are highlighted, and hovering confirms that Copy output controls them. She loads only the copied album, reviews the match, records the destination and resulting names she expects, and saves only after the test is acceptable.

On Sunday, she returns to her main collection. Before loading files, she disables Copy output and checks the active settings again. She does not assume that disabling the copy profile will reverse Saturday’s saved edits. It only changes which option values Picard will use next.

Avoid common mistakes

Do not treat profiles as undo. A profile controls option values during processing. It is not version history for files you have already saved.

Do not overload every profile. If every profile manages every option, you must constantly reason about the stack. Smaller profiles reduce accidental overrides.

Do not forget user settings. The user settings profile remains underneath the stack, contains the ordinary settings, and is always enabled. If no enabled user-created profile controls an option, user settings supply the value.

Do not save settings casually. When you click Make It So!, Picard saves option settings from all pages. Highlighted options are saved to the first enabled profile that controls them. Unhighlighted options are saved to user settings.

Do not batch first. Use a small copied folder when changing profile behavior. Check the active profile, the highlighted settings, the expected destination, and the output names before applying the workflow to more files.

Do not ignore tag preservation needs. If a workflow involves fields you want to keep, review your tag-handling choices separately. For a focused guide, see how to preserve selected music tags in Picard.

Profile checklist

Use this checklist whenever you switch tasks:

1. Name the task you are about to perform, such as main output, test output, or portable copy output.
2. Enable only the profiles needed for that task.
3. Check stack order if more than one enabled profile may manage the same setting.
4. Open the relevant option pages and look for highlighted settings.
5. Hover over highlighted options to confirm which profile controls them.
6. Record the expected destination, naming outcome, and any settings you deliberately changed.
7. Use copied files for the first run after creating or changing a profile.
8. Review matches and visible changes before saving tags or applying the workflow to more files.

Your next practical step is to create one narrow profile for a recurring task, attach only the options that must differ, and test it on a copied album before trusting it with a larger batch.

For your next library addition, search its song title and artist on Mp3Juice. Select the appropriate Picard profile before tagging the permitted file, then inspect the proposed changes.