Free AAMVA Driver's License Barcode Generator
Build PDF417 barcodes that conform to the AAMVA Card Design Standard. Round-trip them through this site's scanner to see the structured License Preview parser. Free, client-side, never sent to a server.
- 二维码生成器
- 免费名片设计器
- 可打印的 WiFi 卡片
- 批量 CSV (500 个码)
- 40 种模板
- 20 种语言
此条码格式仅以前景色和背景色单色渲染。模板、点/眼形状、渐变、边框和中心徽标仅适用于二维码，此处已隐藏。
显示更多 30 个模板
使用上面的按钮保存样式，以便将您最喜欢的样式保存在此处。
或者选择内置图标：
显示更多 108 个图标
以降低的不透明度渲染在 QR 背后。自动强制 EC=H，使 QR 仍可通过照片扫描。
批量生成
上传 CSV 文件，一次最多可生成 500 个二维码。每一行都会生成独立的二维码——您可以选择模板，也可以逐行自定义 21 项属性：颜色、边框、点/眼/眼球样式、渐变、透明度、尺寸、纠错等级、格式、内置 logo 等。
21 列：type, data, filename, frametext, frame, template, fgcolor, bgcolor, size, ec, dotstyle, eyestyle, format, logo, gradient, g2, gtype, gangle, transparent, eyeball, eyecolor。仅 type 和 data 为必填项。使用 | 分隔 data 内的字段（例如 ssid|password|WPA）。
支持全部 20 种二维码类型，包括 URL、WiFi、vCard、MeCard、Email、SMS、Event、Location、UPI、SEPA、PayPal、Crypto、Micro QR 和 rMQR。下载示例 CSV，查看所有列、40 个模板、11 种边框样式以及 12 个内置 logo 的实际效果。
1. 下载示例 CSV · 2. 在 Google Sheets、Excel、Numbers 或任意文本编辑器中编辑 · 3. 在此上传
将整个二维码——类型、所有字段值、样式、框架、徽标、名片设计——保存为单个 .qr.json 文件。稍后加载它以一键重新创建所有内容。
输入内容以生成您的二维码
在法庭上也能成立的电子签名
Abundera Sign 超越了基本的电子签名。每份文件都获得加密证明、独立验证和防篡改证据包。
- 自动生成的法庭就绪证据包
- 个人文件封印 — 即时检测篡改
- 固定在 5 个独立系统上 — 无单点故障
Use for legitimate purposes only: AAMVA parser testing, kiosk and age-gate development, ID-scanner integration testing, accessibility tools, and demoing AAMVA workflows. Producing a counterfeit government ID is identity fraud and is prosecuted as a felony in every US state. Use real data only when you own the source license, or use synthetic data clearly marked as such.
What's the AAMVA Card Design Standard?
The American Association of Motor Vehicle Administrators (AAMVA) publishes the Card Design Standard that every US state, the District of Columbia, and the Canadian provinces use to encode driver-license and ID-card data on the back of the card as a PDF417 barcode. The standard defines a header (compliance indicator + ANSI prefix + Issuer Identification Number + version + jurisdiction version + entry count), one or more subfile designators (DL/ID + offset + length), and a subfile body of three-letter element codes followed by their values.
The current version is the 2020 edition (compliance indicator @, ANSI version 10). Most state DMVs are on version 8 or higher.
What this generator does
- Captures the standard set of AAMVA element codes via a friendly form (DCS family name, DAC first name, DAD middle, DAQ license number, DAG/DAI/DAJ/DAK address, DBB date of birth, DBA expiry, DBD issue date, DBC sex, DAU height, DAY eyes, DCA class, DCB restrictions, DCD endorsements, DCG country).
- Builds an AAMVA-compliant payload string with the correct header structure, subfile designator, and element ordering.
- Encodes it as a PDF417 barcode via bwip-js (lazy-loaded; only ~1 MB the first time you pick a non-QR type).
- Lets you scan the result back via this site's scanner — the AAMVA parser detects the
@ ANSIheader and renders a structured "License Preview" card showing the decoded fields.
What this generator does NOT do
- Does not produce a card that any state DMV would consider authentic. Real licenses include holographic overlays, ghost photos, microprinting, UV/IR features, and a tactile signature panel — none of which a printed barcode can substitute for.
- Does not compute a real Document Discriminator (DCF) — DMVs derive that from internal cardstock serials. We emit a placeholder.
- Does not sign or hash the payload — AAMVA does not require digital signatures.
Legitimate use cases
- Kiosk development: testing self-service kiosks (DMV check-in, hotel check-in, rental-car pickup) without a real license in hand.
- Age-gate development: building bar / liquor-store / cannabis-dispensary scanners. Use synthetic data tagged as test-only.
- AAMVA parser unit tests: generating fixtures with edge cases (missing fields, longer-than-spec values, unicode in name fields, etc.).
- Accessibility tooling: reading DLs for users who can't see them.
- ID-scanner SDK QA: verifying a 3rd-party SDK behaves correctly across jurisdictions.
The 51 jurisdictions
AAMVA assigns a 6-digit Issuer Identification Number (IIN) to each jurisdiction. We ship the standard set: all 50 US states, DC, and the Canadian provinces. Selecting a state in the form sets the IIN automatically (e.g. California = 636014, Texas = 636015, New York = 636001).
支持 26 种语言
完全翻译的界面、原生字符渲染，以及对阿拉伯语和乌尔都语的从右到左支持。
Frequently Asked Questions
Will this barcode pass a real DMV scanner?
It will parse as AAMVA-compliant on any standards-following reader. It will not pass a real DMV's authenticity checks because real licenses also rely on physical security features (holograms, microprinting, UV/IR layers) that a printed barcode can't substitute for.
Is generating my own driver's license illegal?
Generating a barcode that parses like a driver's license is not illegal. Presenting a counterfeit ID to a government official, retailer, or bartender as if it were authentic is fraud and a felony in every US state. Use this tool only for testing, kiosk dev, and other legitimate purposes.
Why does my parsed barcode show different fields than my real license?
DMVs may include jurisdiction-specific element codes (e.g. social-security suffix, organ-donor flag, veteran indicator) beyond the AAMVA core set. Our generator covers the universally-required fields; states like California and Texas add ZF*-prefixed proprietary codes that we don't currently expose.
What's the difference between AAMVA versions?
Version 8 (2013) added the compliance header, version 9 (2016) clarified DCF format, version 10 (2020) added document image elements. We emit a version-10 header but the payload is backwards-compatible with parsers down to v8.
Can I parse a real license I scanned with my phone?
Yes — the scanner here detects any AAMVA payload and renders the License Preview. Privacy: parsing happens entirely in your browser, never sent anywhere. You should still trust the source of any DL data you scan.
Why does the printed barcode look slightly different from my actual license?
DMV cardstock printers run at 600 DPI with specific aspect-ratio tuning. We render at the size you pick. The encoded data is identical; only the visual proportions differ. To approximate a real card, set Size to 1050 px wide and use the PDF417 column count from the form.
Does this generate ID-card barcodes too (non-driver IDs)?
Yes — pick Identification Card in the Document Type dropdown. The subfile designator changes from DL to ID; everything else is the same.