Brazil phone number format
Country code +55, 11 digits after it. Below is the same example written every way you are likely to need it.
Convert your own Brazil number
Paste it however you have it — you get it back in every notation below, plus whether that number is really allocated.
Paste the number however you have it — national digits are fine, the country is already set. Change the picker if the number is from somewhere else.
Example mobile number
This is a numbering-plan example, not a real subscriber’s line. It is generated from the same data the validator uses, so it always matches what the API accepts.
Why your form rejects valid Brazil numbers
Nearly every wrongly-rejected Brazil number on a signup form comes down to one of three things.
The country code is being added twice, or not at all
Brazil numbers carry no trunk prefix, so the national digits and the international ones are the same after +55. The usual failure is the opposite one — storing (11) 96123-4567 with no country code at all, which is ambiguous the moment a second country is supported.
A length check borrowed from another country
Brazil runs 11 digits after +55. A hand-written \d{10} was almost certainly correct for whichever country the form was built in, and is wrong here. Length rules are per-country and several countries use more than one.
A regex cannot know what was ever issued
Right country code and right length still passes numbers no carrier was ever assigned — which is exactly what someone inventing a number at signup produces. Pattern matching answers “could this exist”, never “does it”.
For the first two, use a numbering-plan library rather than a pattern. This is the same call the examples on this page are generated from:
import { parsePhoneNumberFromString } from "libphonenumber-js"; // what a Brazil user types into your form const typed = "(11) 96123-4567"; const n = parsePhoneNumberFromString(typed, "BR"); n?.isValid(); // true n?.format("E.164"); // "+5511961234567" <- store THIS
What parsing still cannot tell you
The third one has no offline answer. Whether the range was allocated, whether it is mobile, fixed line or VoIP, and whether the number has been reported for abuse are all lookups, not patterns — and on a signup form they are the half that decides anything.
curl "https://www.layercall.com/v1/lookup/phone?phone=%2B5511961234567" \ -H "X-Api-Key: YOUR_KEY"
1,000 lookups a month free, no card. Get an API key.
Got a column of them?
One number is a demo. If what you actually have is a CRM export, a signup dump or a list you inherited, paste the whole thing — every row gets parsed and scored, Brazil numbers alongside any other country, with duplicates removed and counted first.
Check a whole list — free, no signup →Questions
Why does my signup form say a valid Brazil number is invalid?
Usually a length rule copied from another country, or a number stored with no country code at all. Brazil numbers carry no trunk prefix, so (11) 96123-4567 and +5511961234567 hold the same digits after +55 — but a bare national number is ambiguous the moment your form accepts a second country.
How do I convert a Brazil number to E.164?
Drop any spaces, brackets and dashes, and put +55 in front — (11) 96123-4567 becomes +5511961234567. Do it with a numbering-plan library rather than string surgery: the rules differ per country and several countries have more than one valid length. The converter at the top of this page does exactly this and shows the result.
What is the country code for Brazil?
Brazil's country calling code is +55. In E.164 — the format almost every API, SMS gateway and CRM expects — it is written with no spaces, brackets or dashes, like +5511961234567.
How many digits is a Brazil phone number?
11 digits after the +55 country code. Written nationally it may show no trunk prefix.
Does the leading 0 get included when dialling Brazil from abroad?
Brazil numbers do not use a national trunk prefix, so the national and international digits are the same after the +55 country code.
Is a correctly formatted number the same as a real one?
No, and conflating the two is the usual mistake. Formatting only says a number could exist. It does not say whether the range was ever allocated, whether it is mobile, fixed line or VoIP, or whether it is worth trusting on a signup — those need a lookup against numbering-plan data.