Fingerprint Customization
Advanced guide to customizing browser fingerprints. Manual Canvas, WebGL, font configuration, navigator spoofing, and timezone manipulation for maximum control.
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:
- Canvas & WebGL
- Fonts & Text Rendering
- Navigator Object
- Screen & Display
- Audio Context
- WebRTC & Media Devices
- Hardware & Sensors
- 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:
| Vendor | Market Share | Best For | Detection Risk |
|---|---|---|---|
| Intel HD Graphics | 42% | Laptops, budget desktops | Low |
| NVIDIA GeForce | 31% | Gaming, high-end workstations | Low |
| AMD Radeon | 18% | Budget gaming, general use | Medium |
| Apple Silicon | 6% | M1/M2/M3 Macs only | Low (Mac only) |
| Other/Custom | 3% | Advanced users | High |
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:
- Template-Based: Uses fonts from your chosen OS template (Windows, Mac, Linux)
- Custom List: You provide exact font names
- 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.36Components 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 Type | Common Values | Notes |
|---|---|---|
| Budget Laptop | 2, 4 | Dual-core with hyperthreading |
| Standard Laptop/Desktop | 4, 6, 8 | Most common |
| High-End Desktop | 12, 16 | Gaming or workstation |
| Workstation | 24, 32 | Professional 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:
| Resolution | Market Share | Device Type | Pixel Ratio |
|---|---|---|---|
| 1920x1080 | 35% | Desktop, laptop | 1x |
| 1366x768 | 22% | Budget laptop | 1x |
| 2560x1440 | 12% | High-end desktop | 1x |
| 1536x864 | 8% | Laptop | 1x |
| 2880x1800 | 4% | MacBook Pro | 2x (Retina) |
| 3840x2160 | 3% | 4K desktop | 1x 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:
- IP geolocation from your proxy
- Browser timezone from Intl.DateTimeFormat
- 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:
- pixelscan.net: Comprehensive fingerprint analysis
- browserleaks.com: Canvas, WebGL, WebRTC leak tests
- 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.
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.