Free tool
SHA-256 Hash Generator For Meta And Google Ads
Paste your email addresses or phone numbers: the tool puts them in the format Meta or Google Ads requires, then computes their SHA-256 hash, the one Customer Match and enhanced conversions expect. Everything happens in your browser.
Meta and Google Ads only accept values hashed with SHA-256, after a precise normalization. In Google Ads, a badly normalized value is still accepted, but it never matches a customer.
Meta: email trimmed and lowercased; phone reduced to its digits, with the country code and no “+”.
Paste one value per line to see its hash.
Sources read on November 6, 2026: Meta, Customer File Custom Audiences, Meta, Customer Information Parameters and Google Ads API, Customer Match.
Your Lists Are Ready. Is Your Conversion Tracking?
A correct hash is useless if conversions do not come through: I check what your site sends to Google Ads and Meta, and fix what gets lost.
20 minutes · No commitment · 100% confidential
How the tool normalizes and hashes your data
Hash = SHA-256(normalized value), as 64 lowercase hexadecimal characters
An email address loses any spaces at the start and end, then goes to lowercase. For Google Ads, the Gmail rule also removes the periods and the “+” suffix from the part before the @, on gmail.com and googlemail.com only: Jane.Doe+Shopping@googlemail.com becomes janedoe@googlemail.com.
A phone number keeps only its digits, with the country code. Meta expects it without a “+”, 16505551212, and Google Ads in E.164 format, +16505551212. With country code 44, a UK number written 07700 900123 becomes 447700900123: the leading zero makes way for the country code.
The normalized value then goes through SHA-256, using the hashing function built into your browser. The result is always 64 characters long, and the slightest difference in the starting value gives a completely different hash.
When to hash your lists yourself
- A customer list for Meta: prepare a file that is already hashed before you upload it, when you do not want it to leave your system in plain text.
- A list for Google Ads: phone numbers must be in E.164 format before hashing, or they match no one.
- A check on your tracking: compare the hash your site sends with the one the tool computes for the same address. If they differ, your site’s normalization is the problem.
Frequently asked questions
Why normalize before hashing?
Because SHA-256 changes completely with the slightest difference: “Mary@Example.com” and “mary@example.com” give two unrelated hashes. Meta and Google Ads normalize their own data the same way, so only values prepared alike can match.
Should I apply the Gmail rule?
For Google Ads enhanced conversions, yes: Google asks you to remove the periods and the “+” suffix from gmail.com and googlemail.com addresses before hashing them. For Customer Match, Google says it handles the variations itself. The Meta pages the tool relies on do not mention it.
How do I check that the hash is right?
With the example Meta publishes: in Meta mode, mary@example.com gives a hash that starts with f1904cf1 and ends with 6552bb79. If you get the same one, the calculation is correct.
Is my data sent anywhere?
No. Normalization and hashing happen in your browser: no address or phone number leaves your device.


