Organize Browser Profiles with Tags

As your browser profile list grows, establish consistent names and tags before relying on search, status filters, and bulk actions. MaskPilot tags organize and filter profiles and can be reused by extension scope rules. A tag does not change a profile’s cookies, fingerprint, proxy, or website sign-in state. One profile can have several tags.

Start with a small tag system

Tags work best for dimensions you filter repeatedly, such as:

• Client or project: Client A, Brand site, Test project.
• Workflow stage: Preparing, Active, Needs review.
• Region or purpose: North America, Support, Publishing.

Use a small, fixed vocabulary for each dimension. Avoid near-duplicates such as “Check,” “Needs check,” and “Checking.” Give every profile a recognizable name, use tags for grouping, and keep temporary context in the note.

Do not put website passwords, proxy passwords, cookies, tokens, or recovery codes in names, tags, or notes. Store credentials in a team-approved credential manager.

Create and assign tags

Create a tag

1. Open the Browser profiles list.
2. Select “More actions” in the upper-right corner.
3. Select “Manage tags.”
4. Enter a name and select “Create.”

Select tags for one profile

1. Create or edit a browser profile.
2. Expand “Classification and browser version.”
3. Under “Profile tags,” select one or more tags.
4. Save the profile.

A tag changes only the profile’s classification. Adding or removing one does not restart a running browser. If an extension scope rule uses that tag, the updated rule takes effect on the profile’s next full launch.

Search and filter profiles

The profile list provides three filters that can be combined:

1. Search by profile name.
2. Filter by All, Running, or Stopped status.
3. Select one tag from the All tags menu.

The page shows the current result count. If nothing is found, select “Clear filters” before concluding that a profile is missing. Bulk selection covers the results currently displayed and loaded. If filtered results have another page, select “Load more” or narrow the filter, then verify the selected count.

Add or remove tags in bulk

1. Select “Bulk manage” under “More actions.”
2. Select the required profiles, or use the top checkbox for the results currently displayed.
3. Select “Tag.”
4. Choose “Add tags” or “Remove tags.”
5. Select at least one tag and save.

Adding or removing tags affects only the tags selected for this operation; it does not clear unrelated tags already on a profile. Check the operation mode before saving. A sub-account can act only on profiles assigned to it and needs permission to modify profiles. Profiles it cannot access never enter the batch.

Use bulk start, stop, and delete safely

Bulk manage also provides start, stop, and delete actions:

• Start: processes stopped profiles; already running profiles can be skipped. The client starts at most three profiles concurrently and queues the remainder.
• Stop: processes running profiles. Profile data continues saving after the browser window closes.
• Delete: available only to the main account and processes stopped profiles. Recheck the filter, profile names, and selected count before confirming.

The batch panel reports completed, failed, skipped, and cancelled items separately. Do not rerun an entire batch because a few items failed. Retry one item, or select “Retry failed items” after the job ends. See How can I recover a deleted browser profile? for the recovery boundary.

Use tags in extension scope rules

After installing or importing an extension, its detail page offers three scope modes:

• All profiles: existing and future profiles load it by default.
• Profile tags: profiles matching the selected tags load it by default.
• Disabled by default: only profiles with an explicit enable override load it.

The profile editor can then inherit the default, enable the extension, or disable it for one profile. Tag rules and profile overrides jointly determine what loads on the next launch. See Use an Extension in One Profile Only for the complete flow.

Review extension rules before deleting a tag. Deletion removes that tag from every profile and extension policy. An extension that depended only on the deleted tag becomes disabled by default. Deleting a tag does not delete profiles, but there is no per-profile restore for the removed tag relationships, so verify filters and policies first.

A repeatable daily workflow

1. Give each new profile a clear name and select existing tags.
2. Narrow the list by tag and status before starting work.
3. Verify the selected count before every bulk action, and review names again before deletion.
4. After a bulk job, handle failed items instead of repeating completed work.
5. After changing an extension tag rule, fully launch one stopped test profile to verify it.

Start with Create and Launch Your First Browser Profile when setting up a new profile. If bulk start reports that a profile is already in use, follow What should I do when a profile shows “in use”? to distinguish a local process from a recent run record. See Add Team Members and Configure Permissions for team access rules.

References

• Google Chrome’s official profile guide explains that bookmarks, history, passwords, and settings remain separate between profiles.
• Mozilla’s official profile guide recommends recognizable names and visual cues when managing several profiles.