Topic
Browser Profiles and Fingerprint Settings
Learn how MaskPilot isolates cookies and site data, keeps browser fingerprints stable, assigns proxies and extensions, and applies profile changes after a full restart.
15 articlesMaskPilot treats every browser profile as a separate workspace. Cookies, site data, fingerprint settings, proxies, and extensions stay attached to that profile, keeping the account purpose, network exit, and browser configuration within one clear boundary.
As the list grows, use the profile tags and bulk management guide to establish names and categories, then narrow the list by name, status, or tag. Tags organize profiles and can define extension scope; they do not change cookies, fingerprints, or proxies.
Build a stable profile first
Choose the browser version and core fingerprint settings before assigning a checked proxy and the extensions you need. Complete sign-in, browsing, and shutdown with a test profile before repeating the workflow at a larger scale. If websites still request a sign-in after reopening the same profile, follow the login-state troubleshooting steps to separate site sessions, cookie clearing, and profile-data recovery.
Handle a failed preflight check
Before launch, the client checks sign-in, the browser, fingerprint, extensions, proxy, and local data. If “Preflight check failed” appears, use the preflight troubleshooting checklist to address each failed item instead of repeatedly changing proxies, extensions, local-process state, and browser downloads together.
Prefer consistency over constant change
Fingerprint settings create a reusable browser environment. After changing the browser version or a core fingerprint value, fully close the current profile and launch it again so the next session uses the new configuration. Frequent random changes are not a substitute for a stable setup.
Prevent concurrent writes
An existing local process or launch operation prevents a duplicate launch on this device. A session on another device no longer blocks launch here, and the latest team run record is not a real-time online status. Before handing work to another device, prefer a normal close and check the sync result. Version checks protect uploads from conflicting overwrites; they do not automatically merge edits from two devices.
Topic
In this topic
Guides
Configure the browser version, core fingerprint settings, proxy, and extensions for an isolated browser profile.
Choose fingerprint settings for the profile, keep them stable, and fully restart the browser so saved changes take effect.
Use MaskPilot profile tags, name search, and status filters to organize browser profiles, then safely start, stop, retag, or delete selected profiles in bulk.
Q&A
Distinguish local running processes, remote run records, and data-version conflicts when launching or switching devices.
Confirm a complete shutdown, the correct profile, and which fingerprint, proxy, or extension changes require a relaunch.
Keep WebRTC traffic on the assigned proxy route, understand MaskPilot's recommended network policy, restart the profile, and verify the result safely.
Learn how MaskPilot selects the browser time zone from the current proxy exit and troubleshoot overridden settings, route changes, or failed detection.
Troubleshoot differences between browser locale, request language order, and saved site preferences when a website keeps selecting the wrong language.
Separate public-IP location, browser geolocation, and saved site preferences when a proxy exit is correct but a webpage still shows another place.
Separate CSS screen size, device pixel ratio, available area, and browser viewport when a website reports a resolution that differs from the display.
Understand the stability boundaries of profile-level canvas protection, then check the browser version, profile, test method, and launch state when results differ.
Understand font detection, profile-stable protection, and the visible-font allowlist when test hashes change, characters disappear, or webpages use fallback fonts.
Separate site session expiry, cookie clearing, profile recovery, and the wrong browser profile when websites ask you to sign in again after a relaunch.
Identify the preparation, download, verification, installation, or launch stage that failed, then retry the browser version safely in MaskPilot.
Use the sign-in, browser, fingerprint, extension, proxy, and local-data results to fix a profile that MaskPilot blocks before launch.