Seeing the same font hash in two Multilogin profiles – or even in Multilogin and your regular browser – can be completely normal. A font hash doesn’t need to be unique for every profile.

➡️ If the only issue is a matching font hash, you usually don’t need to change anything. “Masked” doesn’t mean every profile must return a different hash.

What is a font hash?

A font hash is a short value created by a fingerprint checker from the font information it decides to test.

For example, a checker might look at:

• Which fonts are available
• How certain letters or symbols are rendered
• The measurements produced by those tests

It then combines the results into a hash.

Think of it like a score from one test, not a permanent ID built into your browser.

Different websites and checkers can use different font tests. 

Why can two profiles get the same hash?

Because they can give the checker the same answers.

Imagine a checker only tests:

Arial, Georgia, Verdana, and Times New Roman

If two profiles return the same result for those fonts, the checker can give them the same hash.

That doesn’t mean the profiles are the same or linked. Font data is only one part of a browser fingerprint. Websites can combine it with many other browser and device signals. 

The same thing can happen between Multilogin and your regular browser.

What do “Masked” and “Real” mean?

Go to “Edit” → “Fingerprint” → “Font data”.

You’ll see two options:

• “Masked”: the default – Multilogin controls the font data exposed by the browser profile
• “Real”: exposes the real font data from the device running the profile

You don’t manually select individual fonts in Multilogin.

And one important point: “Masked” does not mean “unique”.

Two profiles can still return the same font hash, and that alone is not a problem.

Why not make every font hash different?

Because different isn’t automatically better.

Think of 20 students wearing the same popular sneakers. The shoes match, but that doesn’t make them the same person.

Browsers work the same way. Lots of real users share individual fingerprint characteristics.

Trying to force every profile to produce a different font result just to satisfy a checker can create unnecessary differences in the overall setup.

Should I switch “Font data” to “Real”?

Usually, no.

If you haven’t intentionally customized the profile, there’s no reason to switch settings just because two hashes match.

If a checker reports an actual inconsistency rather than just a shared value, see How to fix browser fingerprint inconsistencies.