Browser Profiles

Fingerprint Customization

Advanced guide to customizing browser fingerprints. Manual Canvas, WebGL, font configuration, navigator spoofing, and timezone manipulation for maximum control.

Elena Volkov
8 min read

Templates work for 95% of users. But if you need ultimate control or are bypassing advanced detection, manual customization gives you precision control over all 47 fingerprint parameters.

Advanced Users Only

Incorrect customization creates detectable inconsistencies. Only modify parameters if you understand fingerprinting deeply. Bad custom fingerprints perform worse than templates.

Accessing Advanced Settings

In your profile editor, click "Advanced Fingerprint Settings" at the bottom. This unlocks manual control over all parameters.

You'll see eight customization sections:

  1. Canvas & WebGL
  2. Fonts & Text Rendering
  3. Navigator Object
  4. Screen & Display
  5. Audio Context
  6. WebRTC & Media Devices
  7. Hardware & Sensors
  8. Browser Behavior

Canvas Fingerprint Customization

Canvas is your most important fingerprint. Get this wrong and you're flagged immediately.

Noise Level: Controls pixel variation in Canvas rendering. Options:

  • Off: No spoofing. Uses your real GPU signature (not recommended)
  • Low (1-2%): Subtle noise. Sites rarely detect differences
  • Medium (3-5%): Default. Good balance of uniqueness and stability
  • High (6-10%): Aggressive. May break some Canvas-dependent sites

Use Medium for most cases. Use High only if you're getting Canvas-based detection.

Hash Consistency: Canvas hash should stay constant within a profile but differ between profiles. Our system ensures this automatically, but you can:

  • Randomize on Each Session: New Canvas hash every browser restart. Good for scraping. Bad for accounts that track device persistence.
  • Fixed Hash: Same Canvas hash forever. Required for e-commerce and social media.

Pick Fixed Hash unless you're specifically testing Canvas detection systems.

WebGL Configuration

WebGL exposes your GPU. Sites use it to fingerprint hardware and validate Canvas consistency.

GPU Vendor Selection:

VendorMarket ShareBest ForDetection Risk
Intel HD Graphics42%Laptops, budget desktopsLow
NVIDIA GeForce31%Gaming, high-end workstationsLow
AMD Radeon18%Budget gaming, general useMedium
Apple Silicon6%M1/M2/M3 Macs onlyLow (Mac only)
Other/Custom3%Advanced usersHigh

Match your GPU to your claimed OS and device type. Don't claim Intel HD Graphics if you're using a high-end datacenter proxy. That screams bot.

Renderer String: Specific GPU model. Examples:

  • "ANGLE (Intel, Intel(R) UHD Graphics 620 Direct3D11 vs_5_0 ps_5_0)"
  • "NVIDIA Corporation - NVIDIA GeForce RTX 3060/PCIe/SSE2"
  • "Apple M1"

Use realistic strings from our database dropdown. Don't make up custom strings. Sites validate against known GPU models.

Shader Precision: High, medium, or low. Desktop GPUs report "high" for everything. Mobile GPUs report "medium" for some shaders. Match your device type.

Font List Customization

Your font list must match your OS and software. Mismatches are instant red flags.

We provide three modes:

  1. Template-Based: Uses fonts from your chosen OS template (Windows, Mac, Linux)
  2. Custom List: You provide exact font names
  3. Real System: Reports your actual installed fonts (least private)

Stick with Template-Based. It includes the right fonts for your OS and common software.

If you use Custom List, follow these rules:

  • Include system defaults: Arial, Times New Roman, Verdana
  • Match OS signatures (Segoe UI for Windows, San Francisco for Mac)
  • Add office suite fonts if claiming Microsoft Office: Calibri, Cambria, Candara
  • Don't mix OS-specific fonts (don't include both Segoe UI and San Francisco)

Navigator Object Spoofing

The Navigator object exposes browser and system info. Every value must be consistent.

Key parameters:

User Agent: Your browser's identity string. Format:

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36

Components must match:

  • Windows NT 10.0 = Windows 10
  • Win64; x64 = 64-bit architecture
  • Chrome/120.0.0.0 = Browser version

Don't use outdated User Agents. Chrome 120+ is current as of January 2024. Chrome 90 would flag you as a bot.

Platform: Must match User Agent:

  • "Win32" for all Windows (even 64-bit reports Win32)
  • "MacIntel" for all Intel and Apple Silicon Macs
  • "Linux x86_64" for 64-bit Linux

Hardware Concurrency: CPU core count. Common values:

Device TypeCommon ValuesNotes
Budget Laptop2, 4Dual-core with hyperthreading
Standard Laptop/Desktop4, 6, 8Most common
High-End Desktop12, 16Gaming or workstation
Workstation24, 32Professional use only

Don't claim 64 cores. That's server hardware. You'll get flagged.

Device Memory: RAM in GB. Common: 4, 8, 16, 32. Match your device type. Budget devices report 4GB. High-end reports 16-32GB.

Screen Resolution and Display Settings

Screen parameters must be consistent and common.

Safe Resolutions by Device:

ResolutionMarket ShareDevice TypePixel Ratio
1920x108035%Desktop, laptop1x
1366x76822%Budget laptop1x
2560x144012%High-end desktop1x
1536x8648%Laptop1x
2880x18004%MacBook Pro2x (Retina)
3840x21603%4K desktop1x or 1.5x

Available Screen Size: Resolution minus taskbar/dock height. If screen is 1920x1080 and taskbar is 40px, available height is 1040px.

Color Depth: Almost always 24 bits. Some high-end displays report 30 or 48. Use 24 unless you know what you're doing.

Timezone and Geolocation Alignment

Timezone must match your proxy location. This is critical.

Sites compare:

  1. IP geolocation from your proxy
  2. Browser timezone from Intl.DateTimeFormat
  3. Timezone offset from getTimezoneOffset()

All three must align. Proxy in Dallas, Texas? Use America/Chicago (UTC-6). Proxy in London? Use Europe/London (UTC+0).

Don't forget daylight saving time. America/Chicago is UTC-6 in winter, UTC-5 in summer.

Audio Context Fingerprinting

Audio Context generates a signature from your audio processing stack. Most users should use "Noise" mode which adds subtle randomization.

Options:

  • Off: Real audio signature (not recommended)
  • Noise: Add randomization to audio output
  • Block: Disable Audio Context API entirely (breaks some sites)

Use Noise unless a specific site breaks.

Validation and Testing

After customization, test your fingerprint:

  1. pixelscan.net: Comprehensive fingerprint analysis
  2. browserleaks.com: Canvas, WebGL, WebRTC leak tests
  3. amiunique.org: Uniqueness score (aim for 1 in 1000+)

Look for consistency errors:

  • Canvas and WebGL GPU must match
  • User Agent OS must match Platform and fonts
  • Screen resolution should match common values
  • Timezone must match geolocation

If you see warnings about inconsistencies, fix them immediately.

Master Session Management

Your custom fingerprint is perfect. Now learn how to manage browser sessions, persist data, and handle cookies across profile restarts.

Elena Volkov

Senior Detection Engineer

Elena Volkov reverse-engineers detection systems for Multilogin.io. She's bypassed fingerprinting on 100+ platforms and discovered 23 novel detection methods used by major sites.