French phone number format: +33, 06 and 07 mobiles, validation and rules

French phone numbers use the country code +33 and have 10 digits when written at home, always starting with 0. A mobile number starts with 06 or 07, so 06 XX XX XX XX in France becomes +33 6 XX XX XX XX from abroad (E.164: +336XXXXXXXX), with nine digits after +33. Landlines start 01 to 05, VoIP and other non-geographic numbers 09, and special-rate numbers 08. The prefix shows which operator received the block, but numbers have been portable since 2003, so it doesn't prove the current network.

This guide is part of our phone numbers by country series. The tables come from libphonenumber's metadata, the numbering plan and number-block list published by Arcep (France's telecoms regulator), our MNP atlas and our public catalog. Example numbers are masked with X, taken from the ranges Arcep reserves for fiction, or are libphonenumber's own example number. We read the Arcep decisions, the laws on Légifrance and the CNIL's guidance on 2026-11-03; most are in French only. This is a summary, not legal advice.

What does a French phone number look like?

A French number is 10 digits written in five pairs: 0Z AB PQ MC DU. The first 0 is the trunk prefix you dial inside France. The next digit, Z, tells you the kind of number:

From abroad, drop the 0 and add +33. People write +33 (0)6 XX XX XX XX as a reminder to dial the 0 at home; strip the bracket and the 0 before you store it. Dots are a common separator too (06.XX.XX.XX.XX).

Every type has nine digits after +33, so length alone can't tell a mobile from a landline; the first digit does. The only long numbers are the machine-to-machine (M2M) range 0700, which has 14 digits in mainland France (Arcep numbering plan, section 2.3.5). They are for devices, not people, and libphonenumber doesn't accept them as French mobiles.

Is Guadeloupe or Réunion +33?

No. The overseas departments use the French numbering plan but have their own country codes (Arcep numbering plan, section 2.3.4):

A customer in Guadeloupe writes 0690 XX XX XX, which looks French. In E.164 it is +590 690 XX XX XX, not +33 690 …. If you serve overseas customers, ask for the territory, or parse with its region code (GP, GF, MQ, RE, YT, PM).

Which prefixes are mobile numbers?

In mainland France, Arcep's plan lists these mobile roots: 061, 062, 064, 066 to 068, 073 to 078, plus 0601 to 0609, 0630 to 0638, 0650 to 0652, 0656 to 0659, 0695, 0698 and 0699. The 079 range is reserved for future overseas needs. For each two-digit block, the generator counted every nine-digit number that libphonenumber's mobile pattern for FR accepts:

The gaps are the overseas blocks from the table above: 0639 is Mayotte, and 0690 to 0694, 0696 and 0697 belong to the Caribbean departments and French Guiana. 070, 071 and 072 are not mobile at all (0700 is the M2M range). Arcep's plan reserves 06 and 07 for interpersonal services: the number must belong to one person who can make and receive calls and messages (Arcep, 5 September 2022). Machines, alarms and platforms have to use other ranges.

Which operator holds a 06 or 07 block?

Arcep allocates numbers in blocks and publishes every allocation as open data (MAJNUM file, matched to operator names with the operator code list). We summed the ten-digit 06 and 07 blocks allocated in mainland France in the file we downloaded on 2026-11-03 (latest allocation dated 2026-10-16). In total, 135.6 million mobile numbers are allocated:

073 and 079 have no mainland allocations in the file. Two things follow. First, the "valid" mobile pattern in libphonenumber is wider than what is in use, so a valid 073 number is possible under the plan but not yet issued. Second, the block holder is only a starting point: blocks range from 1 million numbers down to 10,000 or even 1,000, so newer ranges are split between many operators, and any number can be ported. Arcep's own lookup tool (identify an operator by its number) answers the same question one number at a time and doesn't follow porting either.

What do 01 to 05, 09 and 08 numbers mean today?

Landline numbers kept their regional first digit: 01 Île-de-France, 02 north-west, 03 north-east, 04 south-east and 05 south-west, plus 0262, 0590, 0594 and 0596 overseas. But since 1 January 2023 the "geographic" category no longer exists in Arcep's plan. Most 01 to 05 numbers became polyvalent numbers that can be given to a subscriber anywhere in mainland France, and a customer who moves can keep the number (Arcep decision 2022-1583, sections 2.3.3 and 2.3.6; Arcep portability page). A 04 number is no longer proof that someone lives in the south-east.

09 numbers are polyvalent too, and libphonenumber types most of them as VOIP: they are the numbers that come with internet boxes and IP phone services. Two sub-ranges are special:

• 0937 and 0938 are for conversations between a mobile user and a "technical platform", such as a shop chatting with a customer or a delivery driver or ride-hailing app masking both parties' numbers.
• 0948 and 0949 are verified polyvalent numbers (see below).

08 numbers are special services: freephone numbers start 0800 to 0805, and the rest of 08 carries shared or premium rates. None of these should be accepted as a personal sign-up number.

What are 0162, 0163, 0270 and 0271 numbers?

They are verified polyvalent numbers (numéros polyvalents vérifiés), the ranges that automated calling and messaging systems may show as caller ID. Arcep's plan reserves 12 of them in mainland France: 0162, 0163, 0270, 0271, 0377, 0378, 0424, 0425, 0568, 0569, 0948 and 0949. Overseas, the ranges are 09475 and 05987 (Guadeloupe, Saint-Martin, Saint-Barthélemy), 09476 and 05988 (French Guiana), 09477 and 05989 (Martinique), and 09478 and 09479 (Mayotte and Réunion) (Arcep numbering plan, section 2.3.7).

The rule, in force since 1 January 2023, works in two parts (Arcep decision 2022-1583, sections 2.3.2 f, 2.3.4 f and 2.3.7):

• Automated systems can't use mobile or most landline numbers as caller ID. Mobile numbers have no exception at all. Other landline-style numbers have narrow exceptions for low-volume systems, such as one that calls five numbers or fewer in 30 days.
• Verified numbers must be authorised. The operator running a 0162-type number must be able to show that the number's holder explicitly agreed to its use as caller ID in each call or message. If it can't, the call or message is not allowed, even with the caller ID hidden.

In practice, a French call centre's dialler, an automated reminder line or a robocall shows one of these 12 prefixes. People in France have learned to recognise them as sales or automated calls. For you, the useful consequences are: don't send automated SMS or calls from a 06 or 07 number, and don't treat a 0162 number as a customer's personal line.

Since 1 January 2026, the plan also has a category of numbers for automated calls and messages of general interest, such as public alerts. They can only be given to bodies named in a joint ministerial order (Arcep, 2 December 2025).

How do I validate a French number in code?

Use a libphonenumber port with full metadata and the default region FR, and keep only numbers typed as mobile. Pass the region of an overseas department when you expect one.

Python (pip install phonenumbers):

import phonenumbers
from phonenumbers import PhoneNumberType


def normalize_fr(raw: str, region: str = "FR") -> str | None:
    """E.164 for a French mobile number (06, 07), or None.
    For an overseas department pass its own region code, e.g. "GP" or "RE"."""
    try:
        n = phonenumbers.parse(raw, region)
    except phonenumbers.NumberParseException:
        return None
    if (not phonenumbers.is_valid_number(n) or phonenumbers.region_code_for_number(n) != region
            or phonenumbers.number_type(n) != PhoneNumberType.MOBILE):
        return None
    return phonenumbers.format_number(n, phonenumbers.PhoneNumberFormat.E164)


for raw in ["06 12 34 56 78", "+33 (0)6 12 34 56 78", "0033 6 12 34 56 78", "06.12.34.56.78",
            "01 99 00 12 34", "06 39 98 12 34", "0690 12 34 56"]:
    print(f"{raw!r:24} -> {normalize_fr(raw)}")
print(f"{'0690 12 34 56 (GP)':24} -> {normalize_fr('0690 12 34 56', 'GP')}")

JavaScript (npm install libphonenumber-js):

import { parsePhoneNumberFromString } from "libphonenumber-js/max";

/** "06 …", "+33 (0)6 …", "0033 …" → E.164 for a French mobile number, or null.
 *  For an overseas department pass its own region code, e.g. "GP" or "RE". */
export function normalizeFr(raw, region = "FR") {
  const phone = parsePhoneNumberFromString(String(raw), region);
  return phone?.isValid() && phone.country === region && phone.getType() === "MOBILE" ? phone.number : null;
}

for (const raw of ["06 12 34 56 78", "+33 (0)6 12 34 56 78", "0033 6 12 34 56 78", "06.12.34.56.78",
                   "01 99 00 12 34", "06 39 98 12 34", "0690 12 34 56"]) {
  console.log(JSON.stringify(raw).padEnd(24), "->", normalizeFr(raw));
}
console.log("0690 12 34 56 (GP)".padEnd(24), "->", normalizeFr("0690 12 34 56", "GP"));

We ran both on 2026-11-03 (Python 3.12 with phonenumbers 9.0.40, Node.js 24 with libphonenumber-js 1.13.13). 06 12 34 56 78 is libphonenumber's own example number; the others come from Arcep's fiction ranges or are overseas test inputs. Both printed the same results; Python prints single quotes and None, JavaScript double quotes and null:

'06 12 34 56 78'         -> +33612345678
'+33 (0)6 12 34 56 78'   -> +33612345678
'0033 6 12 34 56 78'     -> +33612345678
'06.12.34.56.78'         -> +33612345678
'01 99 00 12 34'         -> None
'06 39 98 12 34'         -> None
'0690 12 34 56'          -> None
0690 12 34 56 (GP)       -> +590690123456

The +33 (0) form and the dots parse correctly in both libraries. The Paris fiction number is a valid landline, so it's dropped. The mobile-looking fiction number 06 39 98 … is rejected, because 0639 is Mayotte's block under +262 and the fiction block is never assigned. 0690 … fails as a mainland number and passes as +590 when you parse it for Guadeloupe.

The generated test table runs the same idea over masked inputs. The shape regex column tests the pattern most tutorials give, after spaces, dots, dashes and brackets are removed:

Row 8 is the French trap: 070 has the shape of a mobile number and passes the regex, but it isn't a mobile range. The regex also passes 0690 and 0639 numbers as mainland mobiles. Our E.164 developer guide and the post on why an E.164 regex is not enough cover the general problem.

Which numbers can I use in tests and examples?

Use the fiction ranges in Arcep's numbering plan ("numbers for audiovisual works"). Each is a block of 10,000 numbers that Arcep never allocates to an operator; the 2022 version of the plan added that they can't be given to a subscriber, called or shown as a caller ID:

The five landline blocks pass libphonenumber as FIXED_LINE, which makes them good parser test data. The mobile-style block fails validation for both FR and Mayotte (YT), so it can't stand in for a valid mobile in a unit test. Use the library's example number for that, and never a real customer's number. None of these numbers answer a live lookup.

Does number portability change the carrier?

Yes. Mobile number portability (MNP) opened in France on 1 July 2003. Porting within 10 days began in mainland France on 21 May 2007, and a simpler, faster procedure followed on 7 November 2011 (Arcep portability page). How it works today:

• Get the RIO. The relevé d'identité opérateur is a unique 12-character code. Call 3179 from the mobile: the call is free, the number is the same on every network, it works around the clock, and the code arrives by voice and then by SMS (Service-Public.fr). Since 1 December 2023, every end user can get a RIO free of charge, for any type of number.
• One working day. The porting delay set by law is one working day, subject to the line being available, unless the subscriber asks for a later date (Arcep).
• The new operator does the work. You give it your number and RIO; it asks the old operator to port. The port ends the old contract at the same time, but early-termination fees in that contract still apply. You can still port up to 40 days after cancelling a line.
• Compensation. If the port goes wrong or is late, the subscriber can ask the operator for compensation (Service-Public.fr).

The France row of our MNP atlas:

The atlas row gives the launch year only. Arcep's page dates it to 1 July 2003. Our MNP atlas compares France with other countries. With four network operators (Orange, SFR, Bouygues Telecom and Free Mobile) and dozens of virtual operators on their networks, the block holder is a weak guess. For SMS routing, pricing or fraud rules, look up the current network per number.

Arcep also tightened the rules for reused numbers. Since 1 January 2026, a number whose line was cancelled by the operator, for example when a copper line closes, can't be reassigned for at least 45 days, so the former user has time to recover it (Arcep, 2 December 2025). For a business, that is a reminder that a number can change hands: check numbers again before you reuse an old list.

What are the rules for sales calls, SMS and caller ID?

These summarise the laws, decisions and guidance as we read them on 2026-11-03. Not legal advice; ask counsel how they apply to you.

Sales calls to consumers need consent (since 11 August 2026)

France switched from opt-out to opt-in for telephone prospecting. Article 13 of Law no. 2025-594 of 30 June 2025 rewrote article L223-1 of the Consumer Code, with effect from 11 August 2026 (Law 2025-594, art. 13; L223-1):

• Prior consent. It is forbidden to canvass by phone a consumer who has not consented beforehand. Consent means a free, specific, informed, unambiguous and revocable expression of will, and the business must prove it.
• Existing contracts. The ban doesn't apply to calls about a contract in progress and its subject. A call about a different product is not covered by that exception.
• Banned sectors. Phone canvassing for home renovation for energy savings, renewable energy or adapting homes for older or disabled people is banned outright, except within a contract in progress.
• Void contracts. A contract concluded after an unlawful call is void, and a business that benefits from unlawful calls is presumed responsible.

Decree no. 2026-662 of 23 July 2026 sets the details, also from 11 August 2026 (Decree 2026-662):

• Consent needs a clear positive act. A pre-written statement or simply continuing to browse a website doesn't count.
• The request must name the business, the goods or services, the period of consent and how to withdraw. Consent lasts at most one year and can't renew tacitly.
• The business keeps a digital record of the consent, with its date and time, for three years, and gives the consumer a free copy on request.
• Withdrawal must be no harder than giving consent, and can be oral.

The days and hours from the 2022 rules still apply: calls only on weekdays that aren't public holidays, from 10:00 to 13:00 and 14:00 to 20:00 in the consumer's time zone, and no more than four calls to the same consumer in 30 days (article D223-9 of the Consumer Code, in its version in force since 11 August 2026; French Business Law translation).

What happened to Bloctel?

Bloctel was France's opposition list: since 2016, consumers could register their numbers, and businesses had to remove registered numbers from their call lists. Under opt-in, a list of people who refuse calls has no role, and the service stopped applying on 11 August 2026 (Blog du Modérateur, 2026; bloctel.gouv.fr). If your process still "cleans against Bloctel", replace that step with a consent record per number.

Marketing SMS need consent too (CPCE L34-5)

SMS follows a different law. Article L34-5 of the Postal and Electronic Communications Code (CPCE) bans direct marketing by automated systems, fax and electronic mail to a natural person who has not consented beforehand (L34-5). The ePrivacy Directive defines electronic mail broadly enough to cover SMS (Directive 2002/58/EC, Art. 2(h)). The CNIL's guidance, dated 10 June 2026, explains how it applies (CNIL):

• Individuals (B2C): consent before the first message. It must be free, specific, informed and unambiguous, given by a positive action: a pre-ticked box or accepting general terms is not enough.
• Existing customers: you may market your own similar products or services to a customer who bought from you and was able to refuse when the number was collected. Creating an online account without a purchase doesn't qualify.
• Professionals (B2B): marketing related to the person's job can rely on legitimate interest, if they are informed and can object.
• Every message must identify the sender and give a simple, free way to refuse further messages.

The CNIL tells consumers that replying "STOP" works for sender numbers of five digits starting with 3, 4, 5, 6, 7 or 8, and that unwanted SMS can be reported to the 33700 service (CNIL). If you send from a short code, process STOP replies; if you send from an alphanumeric sender ID, put a working opt-out in the text.

One court ruling to note: on 25 June 2026 the Conseil constitutionnel found that L34-5 let three authorities (the CNIL, the consumer authority and Arcep) punish the same breach, which breaches the principle that penalties must be necessary. It struck the three enforcement paragraphs, with effect from 31 October 2027; until then, no authority may pursue facts another one is already handling or has already sanctioned (Decision 2026-1210 QPC). The consent rule itself is unchanged.

Caller authentication (MAN) and masked calls from abroad

France's number authentication mechanism (mécanisme d'authentification des numéros, MAN) is its version of STIR/SHAKEN. The 2020 "Naegelen" law on telephone canvassing added it to article L44 of the CPCE, and the obligations took effect on 25 July 2023. Arcep says the progressive rollout began in October 2024 (Arcep, 29 January 2026). How it works (Arcep operator guide):

• The originating operator signs each call and message with a French number and vouches for the caller's right to use it. Attestation level A means the number was verified; B and C don't meet the legal requirement.
• Transit and terminating operators must pass the signature on unchanged and cut off calls whose number can't be authenticated, unless the caller ID is hidden.
• Since 1 January 2026, a call arriving from abroad with a French mobile number (06 or 07) that can't be authenticated is masked instead of cut off (Saint-Martin: from 1 January 2028). Calls from abroad showing a French landline number (01 to 05, 09) without authentication are still cut off.
• Also since 1 January 2026, operators must list in each contract the numbers a customer may show as caller ID, and technically limit calls to that list (Arcep decision 2025-2215).

Spoofing hasn't stopped: Arcep counted more than 19,000 identity-spoofing reports on its "J'alerte l'Arcep" platform in 2025, up from 531 in 2023, and opened an investigation into call routes on 29 January 2026. For a voice OTP placed from outside France, expect the French number you show to be masked or the call blocked. Use a number your provider can authenticate in France, or send the code by SMS. Our guide to STIR/SHAKEN attestation levels explains the A, B and C levels.

Personal data (GDPR)

A phone number linked to a person is personal data under the GDPR (Regulation (EU) 2016/679). Checking a customer's number, for reachability or WhatsApp registration, needs a lawful basis under Art. 6, such as a contract or a legitimate interest you have weighed, and people can object to direct marketing at any time under Art. 21. Our posts on whether a phone number is personal data and on consent for WhatsApp checks give the baseline: your own customers, a stated purpose, minimal data and honoured objections.

Which messaging apps and channels reach people?

SMS reaches every active French mobile. We didn't find a primary source that measures messaging-app use in France in a way we can verify for this guide, so we don't quote shares. The practical answer is to measure your own opted-in customers: check which apps they are registered on, route each person to the channel they use, and keep SMS as the fallback.

How do I check WhatsApp registration for a French customer list?

Normalise every row first, then run one check per number. A check tells you whether a number is registered at the time of the check. It can't tell you whether the person wants your messages:

For lists, use a bulk job. Upload a CSV with numbers written the French way (06 XX XX XX XX, +33 (0)6 … and dots also work) and default_country=FR:

curl https://api.mobilevalidate.com/v1/jobs \
  -H "Authorization: Bearer $MOBILEVALIDATE_API_KEY" \
  -F file=@customers.csv -F checks=whatsapp,hlr -F default_country=FR

Send the same body to POST /v1/jobs/estimate first: it is free and shows the maximum cost before anything runs. Rows from overseas departments need their own country code in the file, or a separate job with default_country=GP, RE and so on.

What changed recently?

The rows for FR and +33 in our numbering-plan changes dataset, built from libphonenumber's release notes:

Latest numbering-plan updates for FR: 2024-08-07 (v8.13.43), 2024-01-10 (v8.13.28), 2023-07-19 (v8.13.17), 2023-02-23 (v8.13.7), 2022-04-19 (v8.12.47).

France's validation metadata has been stable since August 2024; most library releases touched carrier names, not number rules. The regulatory changes matter more:

What can MobileValidate check for French numbers?

Generated from our public catalog:

Catalog data as of 2026-11-03.

* bulk jobs only. The live list is at GET /v1/services.

A lookup returns network and registration facts. It never returns a subscriber's name or address, and we don't offer "number details" searches.

How to start without paying:

• Free test key. Get a test key: it never touches a real network and returns fixed answers for reserved test numbers, so you can build every branch first (test mode).
• Five real checks. Every live account can run 5 phone numbers and 5 e-mail addresses through the real-time checks for free on the dashboard's Try it page.
• Free estimate. POST /v1/jobs/estimate shows the maximum cost of a bulk file before anything runs.

To get a live account, request access. Viber and Zalo checks are bulk-only for now, as the asterisks in the table show. Prices are on the pricing page, which also lists the bonus on larger top-ups.

Because the 06 or 07 prefix shows only the block holder, the useful French lookup is the current network. An HLR lookup gives live reachability, porting and the current network code in one call; an MNP lookup gives ported or not ported and the current network. Here is a small flow for a customer list that adds WhatsApp registration. It uses the public sandbox key mv_test_publicSandboxn9ZgneuhR1B9CRfKG3fulym and our test values. The sandbox accepts only those UK drama numbers, so the example uses them. With a live key, pass the output of normalize_fr().

import os

import requests  # pip install requests

API = "https://api.mobilevalidate.com/v1/lookup"
KEY = os.environ["MOBILEVALIDATE_API_KEY"]


def reach(numbers: list[str]) -> dict[str, dict]:
    """Live status, porting, current network and WhatsApp registration. None means we don't know."""
    r = requests.post(API, headers={"Authorization": f"Bearer {KEY}"}, timeout=15,
                      json={"numbers": numbers, "checks": ["hlr", "whatsapp"], "wait": 5})
    r.raise_for_status()
    out = {}
    for row in r.json()["results"]:
        hlr, wa = row["checks"]["number.hlr"], row["checks"]["whatsapp.registered"]
        attrs = (hlr["attributes"] or {}) if hlr["status"] == "completed" else {}
        out[row["e164"]] = {
            "status": attrs.get("status"),
            "ported": attrs.get("ported"),
            "mcc_mnc": attrs.get("mcc_mnc"),
            "whatsapp": wa["registered"] if wa["status"] == "completed" else None,
        }
    return out


for number, info in reach(["+447700900001", "+447700900002", "+447700900005"]).items():
    print(number, info)

What it printed with the sandbox key on 2026-11-03:

+447700900001 {'status': 'reachable', 'ported': False, 'mcc_mnc': '23415', 'whatsapp': True}
+447700900002 {'status': 'unreachable', 'ported': False, 'mcc_mnc': '23415', 'whatsapp': False}
+447700900005 {'status': None, 'ported': None, 'mcc_mnc': None, 'whatsapp': None}

The last test value answers unsupported_country for both checks, so everything is None. Keep None apart from False: None means we don't know, and it's never billed. Requests with 20 or more consecutive numbers are refused (403 suspected_enumeration), and our acceptable use policy forbids finding recipients for unsolicited messages. People can object through our opt-out form. See WhatsApp number check and carrier lookup for the fields.

What are the key takeaways?

• French numbers are 10 digits at home and +33 plus 9 digits in E.164; mobiles start 06 or 07. Store +336XXXXXXXX, without the (0), spaces or dots.
• Overseas departments have their own codes: a 0690 number is +590, a 0692 number +262. Parse them with their own region.
• 01 to 05 no longer prove a location (since 2023), 09 is mostly VoIP, 08 is special-rate, and 0162, 0163, 0270 … 0949 are verified numbers used by automated callers.
• The prefix names the block holder in Arcep's list, not the current network: porting has run since 1 July 2003, with a RIO from 3179 and a one-working-day delay.
• Use Arcep's fiction ranges (01 99 00 XX XX and the others) in examples, never real numbers.
• Since 11 August 2026, sales calls to consumers need prior, recorded consent and Bloctel no longer applies; marketing SMS have needed prior consent under L34-5 for years.
• Calls from abroad with unauthenticated French mobile numbers are masked since 1 January 2026, so plan voice OTP accordingly.

Network, regulator and company names are used descriptively. MobileValidate is not affiliated with any of them.