This is the default.

Multilogin keeps the WebRTC IP information aligned with the profile’s proxy. If the proxy IP changes while the profile is running, the WebRTC value updates too.

Example: Your proxy shows a London IP. WebRTC shows the same proxy-side IP instead of exposing another connection address.

Enter the WebRTC IP yourself.

The value should normally match the profile’s proxy IP. Only use “Custom” when you know exactly which address the profile should show.

Websites see the WebRTC IP from the current network connection.

This can be useful when you aren’t using a proxy and intentionally want the profile to use the connection from your VPN, mobile network, or internet provider.

WebRTC is turned off inside the profile.

Websites can’t use WebRTC to read IP information, but browser calls, video meetings, screen sharing, and other WebRTC features may stop working.

Use “Disabled” only when you don’t need those features.

This is the default.

Multilogin matches the profile’s timezone to the proxy location automatically.

Example: A London proxy gets a timezone that makes sense for London.

Choose a timezone yourself.

Pick one that makes sense with the rest of the profile. For example, a New York proxy would normally use an Eastern US timezone.

Use “Custom” only when you have a clear reason to set the value manually.

Websites see the timezone of the computer running Multilogin.

Use “Real” when your computer’s timezone is the one you want the profile to show.

Example: Your computer is set to Paris time, but your proxy is in Los Angeles. A checker may notice the difference.

This is the default.

When a website asks for your location, the browser shows a pop-up. You can choose “Allow” or “Block”.

Example: A map asks to use your location. You decide whether to share it.

Websites can access the profile’s geolocation without showing the permission pop-up first.

This can be handy for trusted maps, local search, or delivery websites that you use often.

All geolocation requests are denied automatically.

Use this when you don’t want websites to receive location coordinates. Keep in mind that maps, nearby results, and delivery estimates may not work properly.

This is the default.

Multilogin creates coordinates near the proxy’s approximate location and adds a small offset.

Example: The proxy appears to be in central London. The shared coordinates point somewhere nearby instead of one exact fixed spot.

Use this option to enter your own latitude, longitude, and accuracy.

“Accuracy” tells the website how precise the coordinates are, in meters. A larger number means a wider, less precise area. 

Example: An accuracy of 100 reports the location as accurate to roughly 100 meters.

Make sure the coordinates make sense with the proxy. London coordinates paired with a Sydney proxy may look unusual unless that difference is intentional.

This is the default.

Multilogin controls the language values shared by the profile. English is used by default.

Choose one or more languages and arrange them in your preferred order.

You can:

• Visit BrowserLeaks IP in another browser and copy its Accept-Language value
• Click “Select value” and choose the languages yourself
• Change their order to set the main and backup preferences

Example:

1. English (US)
2. Spanish

A website that supports both may show English first and use Spanish as a backup.

Choose languages that make sense for the person using the profile – not simply the proxy location.

Websites see the real language and locale values from the computer running the profile.

Use “Real” when you intentionally want to share your current browser-language preferences.

This is the default.

Multilogin chooses a screen resolution for the profile automatically. It may be smaller than your actual display – and that’s fine.

Example:

Profile: 1920 × 1080
Screen: 2560 × 1440
✅ The profile fits the screen.

The browser may not fill your entire monitor, but nothing’s broken.

Choose the resolution yourself.

Check every computer where you’ll use the profile, then pick a size that fits them all.

Example:

Profile: 1920 × 1080
Screen: 1366 × 768
⚠️ The profile is larger than the available display.

Part of the browser window may sit outside the usable screen area.

For more examples, see How to adjust screen resolutions.

Websites see the real screen parameters from the computer running the profile.

If you open the profile on another computer with a different display, the reported values can change.

This is the default.

Multilogin exposes an optimized font setup based on the browser profile’s OS. Two profiles can still show the same font hash. That’s normal – a checker may test only a small group of fonts.

For more details, see How to understand matching font hashes.

Websites see the real font data from the computer running the profile.

Switching computers or installing new fonts may affect the result – but only when the website checks those particular fonts.

Multilogin shows generated media-device values instead of the computer’s real setup.

Use “Masked” when you don’t want websites to see the actual device combination.

Choose how many devices the profile reports:

• 📷 “Video inputs” – 0–1
• 🎤 “Audio inputs” – 1–4
• 🔊 “Audio outputs” – 1–4

Keep the setup believable.

Example: A regular laptop could report one camera, one microphone, and one audio output.

You don’t need to add extra devices just to make the profile look different.

This is the default.

Websites see the media devices available on the computer running the profile.

Example: Your laptop has a built-in camera and microphone. Your desktop has a USB webcam, headset, and external microphone.

The result can change when you switch computers – and that can be completely normal.

This is the default.

Multilogin provides WebGL vendor and device values that work together. It also masks supported WebGPU metadata.

Use “Custom” when you need to enter the graphics values yourself.

Only change these fields when you know which values belong together. Random combinations can describe a graphics setup that doesn’t make sense.

Websites see the real WebGL and WebGPU metadata from the computer running the profile.

If you move the profile to another computer with different graphics hardware, these values may change.

Websites see the real WebGL graphics result from the computer running the profile.

Use “Real” only when that’s the result you intentionally need.

Canvas is turned off inside the profile.

This may stop websites from reading Canvas data, but it can also break charts, games, image editors, animations, and other normal page features.

“Disabled” is a legacy option and isn’t recommended for everyday use.

Multilogin adds persistent noise to the AudioContext result.

The noise stays consistent, but the computer still performs the original audio processing. The final result may change when you run the profile on another device.

Example: Think of using the same voice effect on two different recordings – the effect stays the same, but the final audio still depends on the original recording.

This is the default.

Websites see the real AudioContext result from the computer running the profile.

Many devices can return the same or similar results, so a shared hash doesn’t automatically mean two profiles are connected.

Websites don’t see the actual supported port-check results from your computer. Multilogin provides masked values instead.

Keep “Masked” for most profiles.

Multilogin masks the supported ports except the ones you add to “Whitelisted ports (comma-separated)”.

Example: 80,443,5938

Only add ports you recognize and actually need. If you don’t know what a port is for, leave it out.

Websites see the real results of supported local port checks.

Use “Real” only when you intentionally need a website to communicate with a local app or service.

The result can change depending on which apps and services are running on the computer.