A physical wallet card has been the standard proof of identity for drivers for over a century. That's changing. Several states now allow residents to store a version of their driver's license on a smartphone — and more are moving in that direction. But a mobile driver's license (mDL) isn't simply a photo of your card. It's a distinct credential with its own technical standards, acceptance rules, and legal standing that differs meaningfully from the plastic in your wallet.
This page explains what a driver's license on your phone actually is, how it works, where it's accepted, and what variables shape whether — and how — it applies to you.
The term covers a range of things people think of when they imagine storing their license digitally, and it's worth separating them clearly.
A mobile driver's license (mDL) is a state-issued digital credential provisioned to a smartphone wallet app — either a state-specific app or a platform wallet like Apple Wallet or Google Wallet. It is not a scan or photograph of your physical card. It's a cryptographically secured credential that can be verified by a reader or officer without showing the full card, and in some implementations, without even handing over your phone.
A digital ID is sometimes used interchangeably with mDL, but the term can also refer to other forms of electronic identity verification that aren't tied to a DMV-issued license credential.
Storing a photo of your license in your phone's camera roll or a third-party app is neither of these. That type of image carries no legal weight as an identity document in any U.S. jurisdiction.
The distinction matters because acceptance, legal standing, and how you use each type varies significantly — sometimes even within the same state.
📱 In states where mDLs are available, the process typically starts with your existing driver's license. You don't apply for a new license to get an mDL — you provision a digital version of your current credential through a state DMV app or an approved wallet platform. This generally requires identity verification, often including a selfie matched against your DMV photo, and confirmation that your physical license is valid and in good standing.
Once provisioned, the mDL is linked to your DMV record. If your physical license is suspended, expired, or revoked, that status is typically reflected in the digital credential as well. An mDL doesn't create a separate or independent license — it represents the same underlying credential.
Some states issue mDLs only through their own apps; others have partnered with Apple or Google to allow storage in platform wallets. The provisioning steps, verification requirements, and supported devices vary by state.
This is where many people run into surprises. Acceptance of mDLs is not universal, and it doesn't work the same way everywhere.
TSA checkpoints at select airports accept mDLs from participating states at identity verification lanes equipped with compatible readers. The traveler taps or presents their phone; the reader verifies the credential without requiring the phone to be handed over. Not all airports have this infrastructure, and not all states' mDLs are accepted even where readers exist.
Age verification at participating retailers is another use case that some states and apps support, often allowing you to confirm you're over a certain age without revealing your full date of birth or address — a privacy feature the physical card doesn't offer.
Law enforcement traffic stops are a more variable situation. Some states explicitly authorize officers to accept mDLs during stops; others haven't established that legal framework. Whether an officer is equipped or trained to verify a digital credential also varies. In many jurisdictions, carrying the physical card remains required or strongly advisable regardless of mDL availability.
Federal facilities, voting, and certain government transactions may or may not accept mDLs depending on jurisdiction and use case. The rules are still evolving, and readers should verify acceptance for any specific context with the relevant authority.
Private businesses — bars, hotels, rental car companies — are not required to accept mDLs even in states where they're legally valid, and many don't yet have the infrastructure or policies to do so.
Understanding why acceptance is so uneven requires knowing a bit about how the technology works. The leading technical standard for mDLs is ISO/IEC 18013-5, an international specification that defines how a mobile driver's license credential should be structured, transmitted, and verified. When states and readers are built to this standard, credentials from different states can theoretically be verified by the same reader infrastructure.
The standard supports two main data transfer methods: NFC (Near Field Communication), which works like a tap payment, and QR code presentation. Some implementations support both. The verifier — whether a TSA reader or a retailer device — requests only the specific data fields needed for the transaction, and the holder's device responds with just those fields. This selective disclosure is one of the key privacy advantages of a standards-based mDL over a physical card.
Not all state implementations fully conform to ISO/IEC 18013-5, and infrastructure for verifying mDLs is still being built out. This is the underlying reason why even a legally valid mDL from one state may not be readable at a given checkpoint or retailer.
The mDL landscape is defined by variation. Several factors determine what applies to any individual reader:
| Variable | Why It Matters |
|---|---|
| State of issuance | mDL availability and legal standing differ by state; not all states offer them |
| License class | Most mDL programs currently cover standard Class D/non-commercial licenses; CDL holders should verify separately |
| Physical license status | The mDL reflects the underlying credential — suspensions, expirations, and restrictions apply |
| Device and OS version | Some wallet integrations require specific iPhone or Android versions |
| Acceptance context | TSA, law enforcement, retailers, and government agencies each have their own rules |
| Real ID compliance | Some states' mDLs carry Real ID status; others don't — this affects federal use cases |
Real ID is worth addressing specifically. A physical Real ID-compliant card carries a star marking. Whether a state's mDL also carries Real ID status — and whether a given federal use case accepts a Real ID mDL — depends on the specific state implementation and the federal agency involved. These are not assumptions you can make without checking current guidance from both your state DMV and the relevant federal authority.
An mDL does not replace your physical license in most states that offer it — at least not yet. The practical standard across the country remains that drivers carry their physical license while operating a vehicle. Even in states where mDLs are legally recognized for traffic stops, the physical card remains the default expectation in most enforcement contexts.
For international travel, rental cars in some countries, and many private transactions, a physical license is the only accepted form. The mDL ecosystem is built primarily for domestic use cases that have the reader infrastructure to support it.
Some states are beginning to explore or pilot digital-only license options for specific populations or use cases, but a true replacement of the physical credential with a phone-only document remains the exception rather than the norm.
The privacy argument for mDLs is genuine. A physical license handed to a bartender reveals your full name, address, date of birth, height, and license number — far more than needed to confirm you're over 21. A standards-compliant mDL can respond to that same request with only an age confirmation and a photo, sharing nothing else.
Security works differently too. A lost or stolen phone is recoverable in ways a lost wallet is not — credentials can be remotely disabled, and biometric locks protect access. But a dead battery or a software failure means your credential is temporarily unavailable, which is why carrying the physical card remains the practical standard.
The question of what data is retained by verifiers after an mDL transaction — and how that data is protected — is still being worked through in state regulations and the standards themselves. Readers who want to understand their state's specific data handling policies should consult their DMV's mDL program documentation directly.
Several questions naturally follow from a foundational understanding of mDLs. How to add a driver's license to Apple Wallet or Google Wallet depends on your state and which platform your DMV has partnered with — the steps are different enough to warrant their own treatment. How mDLs are handled at TSA checkpoints involves specific airport and state eligibility requirements that go beyond what a general overview covers.
Whether an mDL can be used during a traffic stop, and what officers are actually authorized or equipped to accept, varies enough by state that it deserves careful, state-aware coverage. The question of whether your mDL carries Real ID status — and what that means for federal building access or domestic air travel — intersects directly with the broader Real ID Act requirements that apply to physical licenses as well.
For commercial drivers, the question of whether CDLs are included in any given state's mDL program is a separate inquiry entirely, since CDLs carry federal requirements that add complexity to any digital credentialing approach.
Your state, your current license class, and the specific context where you plan to use a digital credential are the variables that determine what any of this means for you. What this page establishes is the framework — the rest depends on where you are and what you're trying to do.