Parameter Guide (User View)

A clear, section-based filling guide for normal users. No code or commands, only field and operation descriptions.

📌 Key Highlights

• Prioritize three areas: Basic Info → Proxy Settings → Browser & UA.
• For language/time zone/location: prefer “Based on IP / Smart fetch from IP” to reduce manual mistakes.
• Most fingerprint items (GPU, media, fonts, etc.) should stay default or use “Smart generate”. Only change them when you clearly know why.
• Before saving, double-check that language, time zone, location, and proxy region are consistent to avoid being flagged as an abnormal environment.

🧩 Progression (from basic to advanced)

• Beginner: Fill basic info, proxy, UA, and common fingerprint items (screen, language, time zone) section by section.
• Intermediate: Configure WebRTC, geolocation, fonts, and media policies to match network origin.
• Advanced: Understand and configure GPU fingerprint (vendor/renderer/architecture), mobile traits (touch, battery, Bluetooth), automation bypass, and browser features.
• Automation helpers: Use “Smart fetch IP info” and “Platform-optimized GPU fingerprints” to reduce manual work and errors.

The parameters and options here come from real system components (UA database, IP geolocation, WebGL fingerprint library, etc.). This document explains them in human-friendly language.

🧭 How to use

• Fill section by section; when unsure, choose “Auto / Smart”.
• Any item that contains accounts or passwords is sensitive. Keep it safe and use it only in trusted contexts.
• Before saving, ensure language, time zone, UA, and proxy origin are consistent to avoid abnormal detection.

📦 Basic Info

• Instance name: A label to distinguish and identify this environment.
• Note: Description or purpose of this instance.
• Group and account platform: For classification and later management (when applicable).

💡 Suggestion: Include platform/region/purpose in the name to make later search and maintenance easier.

🔌 Proxy Settings

• Proxy mode: Custom or system proxy.
• Proxy type: No proxy, HTTP, HTTPS, SOCKS5, etc.
• Host and port: Proxy server address and port.
• Username and password: Fill if the proxy requires authentication (sensitive).
• IP query service: Used to detect geolocation and language for the current proxy.

💡 Tip: Proxy affects auto-detected language, time zone, and geolocation. You can run “Smart fetch IP info” in the form to update them.

🌐 Browser & UA

• OS and version: Decide overall look and compatibility.
• Browser core and version: Choose an available core version for site compatibility.
• User-Agent: String used by sites to identify the browser. Usually auto-generated from OS and version; only override when needed.
• Cookie: Optional. Used to log in or keep sessions. Follow UI instructions and valid formats.

💡 Suggestion: Prefer auto-generated UA to avoid inconsistencies between UA and actual system.

🛡️ Fingerprint Info (by section)

🖥️ Device & Display

• Browser label: A short label for recognizing this environment.
• Screen: Width, height, color depth, taskbar height (simulated display parameters).
• CPU cores and memory: Display/dispatch info. It’s best to stay close to your real device.

🎨 Canvas & Graphics

• Canvas noise: Adds noise to reduce fixed canvas fingerprint features. Keep default or use random safe values.
• GPU info: Vendor, renderer, vendor string, architecture (recommended: use “Smart generate”).

🎧 Media & Audio

• Audio noise: Usually keep default.
• Input/output device counts: Keep consistent with the underlying system.
• Media load limits: Policies for video/image loading; choose “Off” for no restriction.

📍 Network & Location

• WebRTC: Whether it’s enabled and what IP it reports. Disabling reduces real IP exposure; when using audio/video, turn it on and spoof properly.
• Geolocation: Longitude and latitude; should match proxy location where possible.
• Port scanning: Off by default; only fill when you really need specific port checks (diagnostics).

🗣️ Language & Time Zone

• Language: JS-level language and Accept-Language header. Supports IP-based auto or custom mode.
• UI language mode: How the UI language is chosen (based on language or custom).
• Time zone: Should match language and geolocation for a natural footprint.

🔤 Fonts

• Font removal: Remove uncommon fonts to reduce fingerprint uniqueness.
  💡 Suggestion: Before changing, check available fonts on this platform so you don’t break page rendering.

🧩 Browser Features

• Client rectangles: For layout-based fingerprinting; introducing moderate noise helps reduce fixed patterns.
• Speech synthesis list: Platform-specific ranges; keep default if you don’t need TTS.
• Battery: Spoof battery status and level to match device scenario (desktop vs mobile).
• Bluetooth and network type: Whether Bluetooth is enabled; network type can be set to 2G/3G/4G, etc.

🔒 Automation & Privacy

• Browser traits: Do Not Track, touch support count, and other flags; adjust by scenario.
• Automation bypass: Toggles for common detection points (webdriver, debugger, iframe, etc.).

🔑 Password & Autofill

• Password autofill: Configure websites, usernames, and passwords for automatic login.
  ⚠️ Note: Only use this in trusted environments to avoid credential leaks.

🧠 Advanced: Modes & linking of Language / Time Zone / Location

• Language mode
  • Based on IP: Auto-set page language and Accept-Language based on network origin.
  • Predefined/custom: Manually specify page and header languages.
• UI language mode
  • Based on language: UI follows the page language.
  • Custom: Choose UI language independently.
• Time zone mode
  • Based on IP: Auto-use the time zone that matches network origin.
  • Actual/custom: Use local time zone or manual value.
• Smart IP info fetching
  • Fetch IP, country/city, longitude/latitude, time zone, and language from current network (including proxy).
  • Automatically update: time zone, location (lat/lon), UI language, page language, and Accept-Language.
  • Goal: Keep “language / time zone / location” aligned with proxy region to reduce abnormal detection.

💡 Suggestion: For cross-border or multi-region operations, prefer “Based on IP” and use smart IP fetching to synchronize settings.

🧠 Advanced: Media & Network Policies

• Image load limit (abort_image)
  • No limit: Leave empty or choose “Off”.
  • Fully block: Set to 0.
  • Limit by size: Set to a value > 0 to block images larger than that size (unit KB, for example 10 means block big images).
• Video load limit (abort_video)
  • No limit: Use -1 or Off.
• WebRTC
  • Off: Reduce real IP leaks.
  • On with spoofing: For audio/video sites, spoof IP to balance functionality and privacy.
• Port scanning
  • Off by default. Only enable and configure ports when truly needed.

💡 Suggestion: Media limits should be used carefully to avoid breaking site rendering and UX.

🧠 Advanced: GPU Fingerprint (Vendor / Renderer / Architecture)

• Vendor vs OS tendencies
  • Windows/Linux: NVIDIA, AMD, Intel are common.
  • macOS: Apple (M1/M2/M3) and some Intel.
  • Android: ARM (Mali) and Qualcomm (Adreno).
  • iOS: Apple.
• Renderer string
  • Built from platform, vendor, and graphics backend (D3D11, OpenGL, Metal, etc.).
  • Different platforms naturally produce different renderer strings.
• Architecture mapping (concept examples)
  • Intel: Gen9, Gen11, Xe-LP, Xe-HPG (Arc).
  • AMD: GCN, RDNA, RDNA2, RDNA3.
  • NVIDIA: Turing, Ampere, Ada, etc.
• Platform-optimized GPU fingerprints
  • The system chooses realistic vendor/renderer combos based on OS and assigns weights to common ones to increase realism and stability.
• Practical tips
  • On desktop, use vendor/renderer combos that match the platform; on mobile, prefer ARM/Qualcomm (Android) and Apple (iOS).
  • When unsure, rely on “Smart generate” or platform-optimized presets for stable and common combinations.

⚠️ Note: Overly exotic or inconsistent GPU fingerprints may trigger anomalies on some sites. Stick to realistic combinations.

📱 Advanced: Mobile Fingerprint Essentials

• Touch support: Number of touch points (3/5/10, etc.), matching the device type.
• Bluetooth: Enable/disable to reflect device capability and privacy needs.
• Battery info:
  • Optionally spoof charging state, remaining/charging time, and battery level.
  • Makes mobile scenarios more realistic.
• Network type: 2G/3G/4G/5G/WiFi, choose per scenario.
• Phone brand and OS version: Keep them consistent with mobile UA and device fingerprint.

💡 Suggestion: Only set these for mobile emulation scenarios; keep defaults for desktop-type environments.

🎙️ Voice & Audio

• Speech synthesis list: Platform-specific ID ranges (Windows/Mac) used for TTS.
• Audio noise: Used to reduce fixed audio fingerprints; usually keep default.

🧱 Client Rectangles & Canvas

• Client rectangles: Layout and element rectangular info used for fingerprinting; moderate randomness reduces fixed layout fingerprints.
• Canvas noise: Adds subtle variation to drawing output to reduce fixed canvas fingerprints.

💡 Suggestion: Use values within normal ranges to avoid rendering issues.

⚙️ Parameter Fields (Conceptual)

• Command-line parameters (concept)
  • User data dir: Separate browser data directory per instance.
  • UI language and header language: Sync between interface and page language.
  • Devtools: Can be auto-opened in mobile scenarios for debugging.
• Browser features
  • Do Not Track: Enable as needed.
  • Touch support: Match device type.
• Automation bypass
  • Common detection points (webdriver, debugger, iframe, etc.) can be toggled; keep them aligned with actual usage.

⚠️ Note: These are conceptual descriptions of “fields and features”. Regular users do not need—and are not encouraged—to modify low-level flags directly.

🎯 Scenario-based Suggestions

• Desktop work sites: Keep language/time zone aligned with proxy region; turn WebRTC off or spoof; use typical font sets.
• Mobile emulation: Use mobile OS and UA, set touch support, and reasonably configure phone brand and OS version.
• Cross-border access: Use proxies to get localized language/time zone; avoid language–IP mismatches.
• Compatibility first: Pick verified browser core versions; let GPU info be smart-generated; avoid over-pretending.
• Privacy & security: Handle account/password fields carefully and avoid long-term storage of sensitive data.

📖 Term Glossary

• Canvas noise: Small random differences added during drawing to reduce static fingerprint features.
• Client rectangles: Collections of page element rectangles that can be used for layout-based fingerprinting.
• WebRTC: Real-time communication capability that may expose real network info.
• Accept-Language: HTTP header used by servers to localize content.

✅ Fill & Verify

• Prefer auto or smart-generated options to reduce manual mistakes.
• Review the “Overview” and “Fingerprint Info” sections to ensure language, time zone, UA, and proxy are consistent.
• After “Smart fetch IP info”, location and language will update based on the proxy.
• Before saving, confirm all required fields are filled to avoid runtime errors.

---

This guide is for quick onboarding. For detailed field ranges, required/optional flags, and platform-specific notes, contact the maintainer for a full configuration spec.

---

📋 Field Reference (Quick View)

Field	Meaning	Common values	Required	Platforms
Instance name	Environment identifier	Custom name	Yes	All
Proxy mode	System vs custom proxy	Custom/System	No	All
Proxy type	Proxy protocol	None/HTTP/HTTPS/SOCKS5	No	All
Proxy host/port	Proxy server info	Example: 127.0.0.1:1080	No	All
Proxy username/password	Proxy credentials	As needed	No (sensitive)	All
OS	Runtime OS type	Windows/macOS/Linux/Android/iOS	Yes	All
OS version	OS version	Example: Windows 10, macOS 14	No (auto)	All
Browser core version	Core (Chromium) version	Example: 130/132	No (recommend fixed)	All
User-Agent	Browser ID string	Auto/custom	No (auto)	All
Screen width/height	Display resolution	1920x1080, 1366x768	No	All
Color depth	Color bit depth	16/24/32	No	All
Taskbar height	Taskbar occupied height	48 (example)	No	All
CPU cores	CPU core count	4/8/16	No	All
Memory size	RAM in GB	4/8/16	No	All
Canvas noise	Canvas fingerprint noise	Random int (safe range)	No	All
Audio noise	Audio fingerprint noise	0.0–0.5	No	All
Image limit	Image loading policy	Off/0/size in KB	No	All
Video limit	Video loading policy	Off/-1 (no limit)	No	All
GPU vendor	GPU vendor	NVIDIA/AMD/Intel/Apple/ARM/Qualcomm	No	Desktop/Mobile
GPU renderer	GPU renderer string	Platform-specific	No	Desktop/Mobile
GPU architecture	GPU architecture	Turing/RDNA/Xe-LP, etc.	No	Desktop
WebRTC	RTC capability	Off/Mask	No	All
Spoofed IP	WebRTC IP	Example: 120.x.x.x	No	All
Latitude/longitude	Geolocation	Reasonable values	No (auto)	All
Time zone	Time zone ID	Example: Asia/Shanghai	No (auto)	All
JS language	Page language	Example: zh-CN	No (auto/custom)	All
Accept-Language	Request language	Example: zh-CN,zh;q=0.9,en;q=0.8	No (auto/custom)	All
UI language mode	UI language source	Based-on-language/Custom	No	All
Font removal	Fonts to remove	Lists of common/uncommon fonts	No	All
Client rectangles	Layout noise	Random safe values	No	All
Port scanning	Port probing	Off/specific ports	No	All
TTS list	TTS voice set	Platform-specific ranges	No	All
Bluetooth	Bluetooth toggle	On/Off	No	All
Network type	Connection type	2G/3G/4G/5G/WiFi	No	All
Touch support	Touch point count	3/5/10	No	Mobile
Phone brand/OS	Mobile identifiers	Example: JLN_AL00, Android 10	No	Mobile
Password autofill	Autofill settings	List (site/user/password)	No (sensitive)	All

---

❓ FAQ

• Do language and time zone have to match?
  • It’s recommended to match the proxy’s region to avoid anomalies. Use “Smart fetch IP info” to sync them.
• Will disabling WebRTC break sites?
  • Disabling reduces real IP leaks; for A/V sites, enable with spoofed IP.
• GPU renderer looks different across devices—is that normal?
  • Yes. Different platforms/drivers produce different strings. Use “Smart generate / platform optimized” for common combinations.
• Images suddenly stop loading?
  • Check whether abort_image is 0 or set to a too-small size limit; revert to “No limit”.
• How should I fill cookies?
  • Follow the format hints in the UI. If unsure, log in via normal flow or use a “Set Cookies” tool instead of manual editing.
• Is password autofill safe?
  • Only use on trusted machines. Avoid long-term storage of sensitive credentials.
• “Smart fetch IP info” fails—what now?
  • Check whether proxy is working. On failure, the system falls back to local network info; try another network or proxy.
• How to choose UA for mobile vs desktop?
  • Use desktop UA for desktop; for mobile emulation, use mobile UA plus matching touch/network/brand/version.
• Does enabling port scan affect browsing?
  • It’s off by default. Only activate it in specific diagnostic/test scenarios and choose ports carefully.
• How much canvas/audio noise should I set?
  • Use default or reasonable random ranges to avoid rendering or playback issues.