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.
- Penjana QR
- Pereka Kad Perniagaan Percuma
- Kad WiFi Boleh Dicetak
- CSV Batch (500 kod)
- 40 Templat
- 20 Bahasa
Format barkod ini dirender monokrom dengan warna latar depan dan latar belakang sahaja. Templat, bentuk titik/mata, kecerunan, bingkai dan logo tengah hanya berkenaan untuk kod QR dan tersembunyi di sini.
Tunjukkan 30 templat lagi
Simpan gaya dengan butang di atas untuk menyimpan kegemaran anda di sini.
Atau pilih ikon terbina dalam:
Tunjukkan 108 ikon lagi
Dipaparkan di belakang QR dengan kelegapan rendah. Memaksa EC=H secara automatik supaya QR masih boleh diimbas melalui foto.
Penjanaan Batch
Muat naik CSV untuk menjana sehingga 500 kod QR dalam satu kumpulan. Setiap baris menjadi QR tersendiri — pilih templat atau tindih 21 sifat bagi setiap baris: warna, bingkai, gaya titik/mata/bebola mata, gradien, ketelusan, saiz, pembetulan ralat, format, logo terbina dalam dan banyak lagi.
21 lajur: type, data, filename, frametext, frame, template, fgcolor, bgcolor, size, ec, dotstyle, eyestyle, format, logo, gradient, g2, gtype, gangle, transparent, eyeball, eyecolor. Hanya type dan data yang diperlukan. Gunakan | untuk memisahkan medan di dalam data (cth. ssid|password|WPA).
Menyokong kesemua 20 jenis QR, termasuk URL, WiFi, vCard, MeCard, Email, SMS, Event, Location, UPI, SEPA, PayPal, Crypto, Micro QR dan rMQR. Muat turun sampel CSV untuk melihat setiap lajur, kesemua 40 templat, 11 gaya bingkai dan 12 logo terbina dalam dalam tindakan.
1. Muat turun CSV sampel · 2. Edit dalam Google Sheets, Excel, Numbers atau mana-mana editor teks · 3. Muat naik di sini
Simpan keseluruhan QR â jenis, semua nilai medan, gaya, bingkai, logo, reka bentuk kad perniagaan â sebagai fail .qr.json tunggal. Muatkannya kemudian untuk mencipta semula semuanya dalam satu klik.
Masukkan kandungan untuk menjana kod QR anda
Tandatangan digital yang sah di mahkamah
Abundera Sign melangkau tandatangan digital asas. Setiap dokumen mendapat bukti kriptografi, pengesahan bebas dan pakej bukti yang tidak boleh diubah.
- Pakej bukti sedia automatik yang sah di mahkamah
- Meterai Dokumen Peribadi \u2014 mengesan gangguan serta-merta
- Ditamatkan ke 5 sistem bebas \u2014 tiada satu titik kegagalan
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.
Tersedia dalam 26 bahasa
UI yang diterjemahkan sepenuhnya, paparan tulisan asli, dan sokongan kanan-ke-kiri untuk bahasa Arab dan Urdu.
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.