Browser Profiles and Fingerprint Settings Accounts · Q&A
Why Didn’t My Profile Settings Apply?
Confirm a complete shutdown, the correct profile, and which fingerprint, proxy, or extension changes require a relaunch.
Updated Aug 24, 2026Most browser-environment settings are applied on the next profile launch. Saving a setting while the profile is running does not rewrite the current browser process.
Fully close the profile
- Save the work in the browser.
- Close the profile normally from MaskPilot.
- Wait until its status changes from in use to available.
- Confirm that no browser window remains, then launch it again.
Confirm the profile you edited
Make sure you changed the profile that you actually launched, not a similarly named copy. After a profile is shared or cloned, each copy has independent settings; editing the original does not update the copy.
Check the setting type
- Fingerprint or browser version: requires a full relaunch to read the new configuration.
- Proxy: check the node again; launch must also obtain the current exit and time zone through the actual route.
- Extension: confirm that it is installed, selected for the target profile, and compatible with the browser version.
- Local extension: confirm that a valid copy remains on this device; it is not automatically available on another device.
If the issue remains
Restore or change one item at a time, then relaunch and verify. Record the profile name, client version, changed field, time, and visible message, but remove sign-in credentials, proxy passwords, and bearer tokens from logs or screenshots.