Your California licence can live on your phone. You still have to carry the plastic one.

There is a particular kind of disappointment that comes from a technology working exactly as designed and still not doing the thing you assumed it would.

A Californian adds their driver licence to their phone. The state issues it, at no charge, as a genuine credential. And then the DMV says, in the plainest language the department uses anywhere: keep carrying the plastic one.

That is not a bug in the rollout. It is the shape of the programme, and understanding why turns a confusing half-measure into something genuinely useful.

Three things Californians routinely merge into one

Most of the confusion here comes from treating three separate objects as versions of each other.

• A California driver licence — the credential that authorises you to drive.
• A REAL ID-compliant licence — the same card, meeting a federal standard, which matters for federal purposes such as boarding a domestic flight or entering certain federal facilities. Whether you need one, and what alternatives are accepted, is a federal question answered by TSA and by the DMV, and it is not answered by whether you have a mobile licence.
• A mobile driver licence, or mDL — a digital credential you add to a wallet app.

They are related. They are not interchangeable, and the mDL does not substitute for either of the first two. Adding a licence to a phone changes the format in which a credential can be presented. It does not change what the credential is or which federal standard it meets.

The DMV’s own word for it is “companion”

The department does not hedge. Its own guidance says the mDL is voluntary and serves as a companion to the physical, plastic card — that it is not a replacement, and that you must continue to carry your physical driver licence or state ID.

The reason is not technical caution. It is that acceptance is a separate problem from issuance. The DMV states that law enforcement, state government agencies and businesses are not yet accepting the mDL, and that it is currently authorised for limited usage.

This is the ordinary difficulty of any identity system, and it is worth naming because it is not going to be solved by better software. Every counter, checkpoint, bar, pharmacy, letting agent and patrol car that currently reads a plastic card has to acquire a reader, a procedure and a legal basis for accepting a digital one. That is thousands of separate decisions by thousands of separate organisations, and the state can only make its own.

Where it actually works today

Narrow, but not trivial. The DMV describes where it works today.

Note what is conspicuously not on that list. A traffic stop. A county office. Most shops. The DMV says so directly rather than leaving a reader to discover it at the worst moment, which is to its credit and is the reason this page can be short about it.

For a Fresno traveller the practical read is specific: FAT is not among the California airports the DMV names, so a Valley resident flying from home is in the carry-the-card case, while the same person flying out of SFO or LAX may not be. The list is TSA’s to change, which is a reason to check it rather than memorise it.

The genuinely interesting part is what it does not show

Hand over a plastic licence and you hand over everything printed on it. Your date of birth, your full name, your home address, your height, your licence number — all of it, to whoever asked, whatever they actually needed to know.

A bartender checking you are over 21 does not need your home address. A shop verifying age does not need your licence number. But the card is a single object and it discloses as a single object.

A digital credential can, in supported implementations, answer the narrower question instead: is this person over 21? That is data minimisation, and it is the strongest argument for the whole programme — considerably stronger than the convenience of not reaching for a wallet.

On the surveillance question the DMV is unusually specific. It says usage is not tracked and no data leaves the device without your consent; that neither California nor Apple can see when or where you present your ID; and that information about usage, including where, when and what personal information you shared, is encrypted and stored only on your device.

That is a design claim from the issuing authority, and it is the right thing to read before adding a licence to anything. It is also, honestly, a stronger privacy posture than most people assume a state identity programme would adopt.

What the DMV says about signing up

It is voluntary. That word is the department’s own, and it carries more weight than it looks. A state identity programme that is opt-in is making a different offer from one that is a condition of holding a licence, and the difference is worth noticing while the programme is still young.

It costs nothing. There is no charge to add a California driver licence or state ID to the wallet. A convenience with a fee attached invites the question of what you are buying; a free one only has to be worth the space.

It has device requirements, and they are published. The DMV states the minimum iPhone and operating-system versions rather than leaving you to discover eligibility halfway through. An older handset simply will not be able to do this, and knowing that before you begin is the difference between a two-minute task and a frustrating evening.

It is also reversible. The department documents how to remove a licence or state ID from a device, which matters more than it sounds: a credential you can add and cannot withdraw is a different proposition from one you can take off a phone you are selling, replacing or simply no longer want carrying your identity. Voluntary at the start and reversible afterwards are both the state’s own description, and together they are the fairest summary of what is being asked of a participant.

What this page does not describe is the enrolment flow itself — what you scan, what you photograph, what is transmitted where. That sequence circulates widely in launch coverage and in a device maker’s own announcement, and a company’s material establishes only what that company says. The DMV publishes its own instructions, and those are the ones worth following.

“Currently authorised for limited usage” is the whole status

That phrase is the DMV’s, and it is doing more work than any other sentence on the department’s pages. It is not a description of how good the technology is. It is a description of how far permission extends.

Read it beside the other thing the department says — that law enforcement, state government agencies and businesses are not yet accepting the credential — and the shape becomes clear. The constraint is authorisation and acceptance, not capability. The credential can do more than it is currently allowed and equipped to do.

That distinction decides how a reader should hold the whole thing. Limited authorisation is a state that can widen; it is not a defect awaiting a patch. Which also means the honest answer to “when can I stop carrying my licence?” is not a date on a product roadmap. It is whenever the authorisation and the acceptance catch up — and the department has told you plainly that neither has yet.

It is worth noticing how unusual that candour is. A great deal of launch coverage described a wallet replacing a wallet. The issuing authority’s own pages say the opposite, in short sentences, near the top. When the agency and the enthusiasm disagree, the agency is the one that has to answer for it.

Two documents, two questions, before you fly

A traveller should separate two questions that feel like one at the kerbside.

What gets me through security? That is a TSA question, answered by what TSA accepts at the specific checkpoint you are standing at.

What do I need at the other end? A hotel, a rental-car counter, a bar, a pharmacy, a hospital admissions desk. None of those is bound by what TSA accepts, and most are not yet reading mobile IDs at all.

A credential that clears airport security and then cannot collect the hire car is not a wallet replacement. It is a very good queue-shortener at one specific door.

The one setting where the answer is unambiguous

Of all the doors a licence opens, the traffic stop is the one where the DMV’s position is least ambiguous and most consequential: law enforcement is not yet accepting the mobile credential.

So the honest framing for a driver is not that presenting a phone would be inconvenient. It is that the digital credential does not do this job at all right now, and offering it in place of the card is offering something the officer has no route to read.

There is a second, quieter reason not to reach for a phone at a roadside stop, which has nothing to do with identity systems and everything to do with what handing over an unlocked device can mean. That is a separate question and a serious one, and it is not answered here — but it is one more argument for the card being the thing in the door pocket.

The failure mode nobody plans for

A plastic card has one virtue that is easy to overlook until it matters: it does not run out of battery, it does not need a network, and it does not lock you out because a face scan failed in bad light.

A digital credential inherits every dependency of the device holding it. A dead phone at a checkpoint, a cracked screen, a handset left in a taxi, an update that goes wrong at the wrong hour — each of those turns a working identity document into a rectangle of glass. And the moment you need identification is disproportionately likely to be a moment that has already gone badly.

This is a second, quieter reason the carry-the-card instruction is sound advice rather than bureaucratic caution. Even in a future where acceptance is universal, the sensible household position on a single-point-of-failure identity document is a physical fallback — which is exactly the arrangement the DMV already asks for.

So is it worth adding?

It costs nothing, the state says it collects no usage record, and it works at a handful of doors including some airport checkpoints. On those terms the case is reasonable for someone who flies from the named airports and unremarkable for someone who does not.

What it is not is a reason to change any habit. The card stays in the wallet. The phone is an addition, and a state that says so plainly in its own documentation has behaved better here than the enthusiasm around the launch did.

The technology is finished. The acceptance is not. Those are separate clocks, and only one of them is running in the DMV’s control.

How to verify this yourself

• The DMV’s mobile driver licence questions and answers carries the companion-not-replacement language, the absence of a charge, the named California airports, the acceptance settings and the statement that usage is not visible to the state or to Apple.
• The DMV’s mDL programme page states that law enforcement, state agencies and businesses are not yet accepting the credential and that usage is currently authorised on a limited basis, and the minimum device and operating-system versions.
• The Q&A page also carries the voluntary enrolment and the instructions for removing a licence or state ID from a device. The enrolment sequence itself is deliberately not described here: the accounts in circulation are a device maker’s and a launch story’s, not the department’s.
• Which checkpoints accept a mobile ID is TSA’s determination and changes; the DMV points readers to TSA for the current list, and so does this page.
• REAL ID requirements are a separate federal question. Whether your card meets the standard, and what other documents are accepted, is answered by the DMV and TSA and deliberately is not asserted here.

Authorisation and acceptance are both expanding. Where the DMV’s pages and this one disagree, the DMV is current.

Also on this desk

• What a California earthquake alert actually tells you — another state system whose limits are published and widely misread.
• What an airline owes you when a flight is cancelled.
• What if the price on your screen was calculated for you?