French National ID Card 2026: Your Complete Guide

A French national ID card looks simple until it lands on your desk in a KYC queue, a travel file, or an onboarding review. Then the questions start, is it the current format, does it still prove nationality, and what exactly should be extracted into your system without human rekeying? This guide breaks down the French national ID card from the ground up, so a compliance or operations team can handle the document, the digital layer, and the validation logic with less guesswork.

What the French National ID Card Is

A French national identity card, the Carte Nationale d'Identité or CNI, is an official document used to prove both identity and French nationality. It is not compulsory, which is where many non-French teams get confused, but it remains the standard document people often present in French administrative and identity-proofing processes. For KYC and onboarding work, that distinction matters because a card can carry legal weight even when it is not legally required to be held by every citizen.

The version most teams will encounter today is the ID-1 card under ISO/IEC 7810, with physical dimensions of 85.60 × 53.98 mm. France's official guidance describes the current card as the standard format for renewals and new identity cards France's official card guidance. In practical terms, staff should expect a wallet-size document, not the older paper-style format that may still appear in circulation.

Two generations still coexist

The historical path matters because both generations can appear in real review queues. France introduced the national identity card in 1940, and the modern document has evolved into the electronic ID-1 format used today historical rollout and 2021 launch details. On 16 March 2021, the French government launched the new digital ID card with an electronic chip, QR code, and fingerprints, with the first rollout in Oise and nationwide issuance beginning on 2 August 2021.

That leaves compliance teams with a transition issue, not a clean cutoff. The older adult validity period of 15 years, in force since 1 January 2014, was replaced by a 10-year validity for the new card, and the previous format remains valid until 2031. A reviewer should not assume that an older-looking card is invalid just because it does not match the newest template. The document family is still in migration, so both versions can still be relevant in the field.

Practical rule: treat the French national ID card as a living document family, not a single frozen template. That approach helps prevent false rejections when older cards are still legally in circulation.

Anatomy of the Card and Its Security Features

Start with the surface, then move to the verification layer underneath it. A French national ID card is built so a clerk can read it by eye, while a system can test the same identity through the MRZ and the embedded chip. For teams that have not handled a CNI before, that split is the first concept to get right.

What to look for on the front and back

On the front, the card typically shows the photo, surname, given names, date and place of birth, sex, height, nationality, and the card number. The back carries the address, issue date, validity date, issuing authority, and the Machine-Readable Zone, or MRZ. In a manual review queue, these are the first fields to compare, because they are the ones most often used for identity matching.

The security layer goes beyond printed text. The newer card includes an electronic chip, a QR code, and two fingerprints, except for children under 12 new card launch details. The chip also stores the holder's personal data and photo. In a fraud review, the printed face of the card is only one input. The chip and machine-readable data should agree with it.

Field-by-field reading order

A clean operational approach is to read the card in three passes.

1. Visible identity fields. Confirm the name, birth data, and nationality first.
2. Document fields. Check issue date, expiry date, card number, and issuing authority.
3. Machine and chip signals. Compare the MRZ, QR layer, and chip-derived data against the printed surface.

That order matters because visible typographic differences are usually easier to spot than subtle data mismatches. A forged or altered card often fails at the field-consistency layer before it fails at any deeper technical check.

The current format is still 85.60 × 53.98 mm, which is useful in reception workflows and scanning stations official guidance. Staff can be trained to recognize that size immediately, then move on to the data fields without pausing to identify the document family first. For a compliance desk, that speeds intake and reduces avoidable back-and-forth.

A genuine card doesn't look right only by appearance. Its printed fields, MRZ, and chip data all need to line up.

Eligibility, Application, and Renewal Workflow

A French national ID card is available to French citizens, including minors, and it remains not compulsory even though it is widely used to prove identity and nationality official consular guidance. For a compliance or intake team, that distinction matters. A person without the card still has legal status, so the fallback is a different identity document path, not a refusal.

For a first adult application, the request can be filed at any town hall with a recording station, so the applicant's domicile does not determine where the file starts service-public guidance. The online pre-application can be prepared, but it is not mandatory. That is a common point of confusion, and it matters operationally because a case should not be blocked just because the online step was skipped.

A practical way to think about the process is that the town hall is the intake point, while the application file is the control layer. The person can begin in one location, then complete biometric capture and document matching through the same administrative chain.

What the appointment usually requires

The workflow is document-heavy, and each item serves a different check. A recent photo, 35×45 mm, supports visual identity comparison. Proof of residence anchors the file to an address. The previous identity card is normally requested for renewals. Biometric fingerprints are taken at the appointment, and a pre-application reference number is used when the online step has been completed practical workflow guide.

Those inputs do more than fill a folder. They let staff compare the person, the paper trail, and the biometric record against the same application. The collection step also happens at the notification stage in the same controlled channel, which keeps retrieval tied to the original recording station practical workflow guide. For internal teams, that means the appointment location, collection location, and intake record are usually part of one sequence, not separate service points.

The renewal timeline is easier to state than to manage. The current adult and minor validity is 10 years official consular guidance, while older adult cards followed the 15-year period that had been in place since 1 January 2014 historical rollout details. One practical wrinkle is that free renewal can be available for people who need the card to activate digital identity, which adds another reason for renewal requests to depend on appointments, pre-applications, and supporting documents inclusive-access roadmap update.

For teams that need to inspect the data structure behind the card, the machine-readable zone follows the same general logic used on other identity documents, and a separate guide to the MRZ on identity documents helps explain why those lines matter during validation. In practice, the printed surface, the record in the file, and the machine-readable fields all need to agree.

Digital Identity and Travel Use of the CNIe

A French national ID card now serves as the physical anchor for France Identité, the official digital companion that lets a holder prove identity online after an NFC-based setup France Identité overview in a live digital ID report. For teams used to treating identity documents as items to scan and store, that changes the working model. The card is no longer only a visual credential, it also supports a digital identity layer that sits alongside the printed document.

That digital layer does not work by itself. France's public-sector roadmap links the CNIe to inclusion, training, local support, and assistance for users who may struggle with the setup process inclusive-access roadmap update. In practical terms, digital identity only becomes useful when the person can activate it. Users in low-service areas, older users, and people with limited digital access may need extra help before the flow is complete.

For a broader technical frame, the 2026 guide to biometric security is useful because it shows how biometric checks and chip-based verification are treated as trust signals. The NFC chip is not there for convenience alone. It supports a stronger identity check, especially when the card's printed data, chip data, and user interaction all need to align.

The machine-readable zone also matters here, because it is one of the easiest places to verify that the document data is coherent. A practical reference on MRZ reading for travel documents helps explain why those lines are checked during validation. For internal teams, the point is simple, the visible surface, the chip, and the machine-readable fields should all tell the same story.

Travel use is context-specific

The card's travel use is narrower than many people assume. It can be used across the European Union and the wider European Economic Area, but most destinations outside those frameworks still require a passport. A concrete example is the Channel Islands day-trip scheme, where the French national ID card is accepted and other forms of ID are not service-public nationality and travel context.

Travel acceptance and nationality proof are separate questions. A card can be valid for local movement while still being insufficient for another border or administrative scenario. If your team handles cross-border documents, keep the use case explicit. Online identity, EU travel, and nationality proof are not interchangeable.

Operational note: if the user is asking, “Can I use this card?”, answer with the context first. The right answer depends on whether the question is about online identity, EU travel, or French nationality proof.

When the Card Is Not Enough and Common Fraud Risks

A valid or recently expired French ID card can prove nationality, but if someone doesn't have that document, they may need a recent birth certificate or a Certificate of French Nationality, or CNF official service-public guidance. That's where many generic guides oversimplify the process. For naturalized citizens, people born abroad, or applicants with outdated paperwork, nationality proof can become a separate administrative track, not just an ID card check.

The edge cases that trigger manual review

The card can be insufficient when the document is damaged, outdated, or not the right proof for the requested process. A KYC reviewer should treat these as different cases, because the remediation is different in each one.

• Expired card. It may still help in some nationality contexts, but not in every official use.
• No recent identity card. The applicant may need civil-status documents instead.
• Outdated paperwork. Naturalized or foreign-born applicants often need more than a single card.
• Travel mismatch. A card that is valid for one border context may not work in another same service-public source.

A practical internal reference for broader ID workflows is what is identity verification. It's useful when a team needs to separate document collection from actual proofing logic.

Common fraud patterns and field checks

The most common manipulation patterns are re-photographed cards, altered expiry dates, forged MRZ codes, and counterfeit chip responses. Those threats don't always look dramatic on screen. Often, they show up as a small mismatch between layers.

Use these checks in order:

1. Match the MRZ against the visible card number.
2. Compare the chip's date of birth with the printed date.
3. Check the document signer against the issuing prefecture.

Those checks catch a lot of issues that a quick visual review misses. They also create a better escalation path for suspicious cases, because you can explain exactly where the mismatch happened. In a compliance file, that traceability matters as much as the final decision.

Extracting and Validating CNI Data Programmatically

Manual entry breaks down fast when a team processes French identity documents at scale. The better pattern is to turn the card into structured data, then validate each field before it enters the workflow. That gives finance, legal, and onboarding teams a cleaner audit trail and fewer avoidable corrections.

A practical JSON shape for extraction

A useful schema should capture the visible identity data and the machine-readable data together. For the French national ID card, the core fields are:

• card_number
• surname
• given_names
• sex
• date_of_birth
• place_of_birth
• nationality
• issue_date
• expiry_date
• issuing_authority
• address
• mrz_line_1
• mrz_line_2

A simple JSON example can look like this:

{"card_number":"","surname":"","given_names":"","sex":"","date_of_birth":"","place_of_birth":"","nationality":"","issue_date":"","expiry_date":"","issuing_authority":"","address":"","mrz_line_1":"","mrz_line_2":""}

Validation rules that actually catch errors

Validation should happen field by field, not only at the document level. The MRZ should pass checksum logic, dates should follow a consistent format, the card number should match a defined pattern, and nationality should map to a valid country code. If the chip data is available, it should override the printed surface when there's a disagreement, because the chip is the stronger trust layer.

A few implementation rules help keep the pipeline stable:

• Normalize French accents before comparing names.
• Handle rotated scans before OCR interpretation.
• Use regex on the card number to reject malformed values early.
• Compare MRZ and visible fields for consistency.
• Treat chip output as higher trust when the two sources disagree.

For a broader implementation pattern on structured document output, the image-to-JSON workflow is a good reference point. It's the right mental model for any IDP stack that needs readable fields, not just a screenshot.

CNI fields to extract and validate

Field	Source	Format	Validation Rule
Card number	Visible card, MRZ	Alphanumeric	Must match printed and MRZ versions
Surname	Visible card	Text	Must preserve accents and spacing
Given names	Visible card	Text	Must match chip or MRZ where available
Sex	Visible card	Single character or label	Must match the document surface
Date of birth	Visible card, chip, MRZ	Date	Must use one consistent date format
Place of birth	Visible card	Text	Should match extracted civil data
Nationality	Visible card, chip	Country code or text	Must map to a valid ISO country value
Issue date	Visible card	Date	Must be valid and earlier than expiry
Expiry date	Visible card	Date	Must be valid and later than issue date
Issuing authority	Visible card	Text	Should align with the issuing prefecture
Address	Visible card	Text	Must normalize line breaks and abbreviations
MRZ lines	MRZ	Two lines	Must pass checksum and character rules

Tools like Matil.ai can fit this workflow because they combine OCR, classification, validation, and workflow orchestration in one API, with structured JSON output and traceability for audits. In a document stack, that matters more than a simple text extraction pass, because the goal is usually downstream automation, not just transcription.

Recap and Practical Next Steps

A French national ID card is a 10-year ID-1 document that is not compulsory, yet it carries authoritative identity and nationality value in French settings official consular guidance. That status matters because teams cannot treat it as a simple plastic card. They need to read the printed surface, the MRZ, and the chip with the same level of care they would apply to any regulated identity document.

Two generations still coexist, and the older format remains valid until 2031 historical rollout details. Review teams therefore need to recognize both layouts before they decide whether a card is current, expired, or a legacy version still in circulation. A quick visual check can miss that distinction.

The card also sits inside a broader identity system. It supports France Identité and can be used for digital proof of identity, while travel use still depends on the destination and the legal context France Identité overview. In edge cases, the card may still be insufficient on its own, and additional civil-status documents can be required to prove nationality or family status official service-public guidance. For operations teams, the document is one signal in a larger decision tree, not the entire decision.

If your team processes French identity documents at scale, the practical next step is to move from manual review to structured extraction. Read the MRZ, validate the chip and printed fields, and route the result into JSON with audit-ready traceability. For broader quality and workflow planning, the PartnerScanX digital ID assessment can serve as a useful benchmark while you assess your own document pipeline.

If you are evaluating how to automate French ID processing, visit Matil to see how structured OCR, validation, and workflow orchestration can fit into a KYC or compliance stack. It is a practical way to turn French ID cards into usable JSON without manual entry.