Free eSIM Activation QR Code Generator
Build standard LPA: activation QR codes that iPhone (iOS 17.4+) and Android (13+) scan to provision an eSIM profile from your SM-DP+ 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 个独立系统上 — 无单点故障
How eSIM Activation QR Codes Work
Every modern eSIM provisioning flow ends in a QR code. The format is defined by the GSMA's SGP.22 Remote SIM Provisioning specification: a payload that begins with LPA: (Local Profile Assistant) and encodes the address of the carrier's SM-DP+ server plus a one-time matching ID. When the device's eUICC scans the QR, it contacts the SM-DP+, downloads the profile, and installs it — no SIM tray, no physical card, no carrier-store visit.
The exact payload format is LPA:1$smdp.example.com$matching-id[$$confirmation-code]. The leading 1 is the activation code version. The optional confirmation code adds a second factor that the user types after scanning. Carriers, MVNOs, and IoT-platform operators all generate activation codes in this format.
Use cases
- Carrier self-service portals — issue an eSIM from a customer dashboard and email/show the QR.
- Travel eSIMs — Airalo, Holafly, GigSky and the rest deliver QR codes by email after purchase.
- IoT fleet provisioning — embed the QR on the device label so installers can onboard with a phone scan.
- BYOD enterprise rollouts — IT generates activation codes per employee.
- Re-provisioning a wiped phone — keep the QR archived; rescan to reinstall after device loss.
Required fields
- SM-DP+ Address — the FQDN of the carrier's Subscription Manager — Data Preparation server (e.g.
rsp.truphone.com). - Activation Code (matching ID) — the one-time token that authorises this specific profile download.
- Confirmation Code — optional second factor; the device prompts the user to type it after scan.
Compatibility
iOS 17.4 and later scan eSIM QRs from any camera. Earlier iOS requires opening the camera in the eSIM setup wizard. Android 13+ supports direct scanning system-wide; Pixel and Samsung have shipped eSIM scanning since Android 11. Most major eUICC vendors (G+D, Thales, Idemia, Kigen, eSIM.me) accept the same LPA format.
支持 26 种语言
完全翻译的界面、原生字符渲染,以及对阿拉伯语和乌尔都语的从右到左支持。
Frequently Asked Questions
Is the activation code single-use?
Yes — every legitimate matching ID is single-use by design. Once a device redeems the code, the SM-DP+ marks it consumed and any future scan returns 'profile not available'. If your carrier supports re-issuing, request a fresh code rather than reusing the QR.
Will iPhone or Android show the carrier name automatically?
Yes. The SM-DP+ returns metadata (carrier name, plan name, optional icon) before installation, so the user sees a confirmation screen with branding before the profile is installed.
Can I encrypt the activation code so a phone screenshot doesn't expose it?
The matching ID is one-time and tied to a specific SM-DP+, so leakage is bounded — anyone capturing the QR before the legitimate user redeems it can install the profile, but only once. For high-value deployments, add a confirmation code so the QR alone is insufficient.
What if my carrier hasn't given me a QR but only the SM-DP+ and matching ID strings?
Paste them into the form here and we'll build the QR from the standard LPA format. This is exactly what carrier self-service portals do under the hood.
Does this work for dual-SIM phones?
Yes. The eSIM is added as an additional line; the physical SIM remains active. iOS supports up to eight stored eSIM profiles (one active at a time alongside the physical SIM); Android phones vary by manufacturer.
Can I use this for IoT M2M eSIMs?
If your eUICC supports SGP.22 consumer remote provisioning, yes. Many M2M deployments use SGP.32 (the IoT-specific spec) which has a different bootstrap flow but ultimately reads the same LPA format. Consult your eSIM vendor.
Why does my QR say 'invalid activation code'?
Three usual causes: (1) the matching ID has already been redeemed, (2) the SM-DP+ FQDN is wrong (check for trailing slash or http:// prefix — strip both), (3) the carrier scoped the matching ID to a specific eUICC and your device's EID doesn't match. Contact the carrier support line.