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.
- QR Generator
- Gratis Visitekaartjes Ontwerper
- Printbare WiFi Kaarten
- Batch CSV (500 codes)
- 40 Templates
- 20 Talen
Dit barcode-formaat wordt monochroom weergegeven met alleen voorgrond- en achtergrondkleuren. Sjablonen, punt-/oogvormen, verlopen, kaders en centrale logo's gelden alleen voor QR-codes en zijn hier verborgen.
Laat 30 templates meer zien
Sla een stijl op met de knop hierboven om je favorieten hier te bewaren.
Of kies een ingebouwd icoon:
108 extra pictogrammen tonen
Wordt achter de QR weergegeven met verlaagde dekking. Forceert automatisch EC=H zodat de QR via de foto scanbaar blijft.
Batch Generatie
Upload een CSV om tot 500 QR-codes in één batch te genereren. Elke rij wordt een eigen QR — kies een sjabloon of overschrijf 21 eigenschappen per rij: kleuren, frames, stippen-/ogen-/oogbolstijlen, gradiënten, transparantie, formaat, foutcorrectie, bestandsformaat, ingebouwd logo en meer.
21 kolommen: type, data, filename, frametext, frame, template, fgcolor, bgcolor, size, ec, dotstyle, eyestyle, format, logo, gradient, g2, gtype, gangle, transparent, eyeball, eyecolor. Alleen type en data zijn verplicht. Gebruik | om velden binnen data te scheiden (bijv. ssid|password|WPA).
Alle 20 QR-types worden ondersteund, waaronder URL, WiFi, vCard, MeCard, Email, SMS, Event, Location, UPI, SEPA, PayPal, Crypto, Micro QR en rMQR. Download de voorbeeld-CSV om alle kolommen, alle 40 sjablonen, 11 framestijlen en de 12 ingebouwde logo's in actie te zien.
1. Voorbeeld-CSV downloaden · 2. Bewerken in Google Sheets, Excel, Numbers of een teksteditor · 3. Hier uploaden
Sla de hele QR â type, alle veldwaarden, stijl, frame, logo, visitekaartjesontwerp â op als één .qr.json bestand. Laad het later om alles in één klik opnieuw te maken.
Voer inhoud in om je QR-code te genereren
E-handtekeningen die standhouden in de rechtbank
Abundera Sign gaat verder dan gewone e-handtekeningen. Elk document krijgt cryptografisch bewijs, onafhankelijke verificatie en een manipulatiebestendig bewijspakket.
- Automatisch gegenereerde rechtbankklare bewijspakketten
- Persoonlijk documentzegel — detecteert manipulatie onmiddellijk
- Verankerd aan 5 onafhankelijke systemen — geen enkel storend punt
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.
Beschikbaar in 26 talen
Volledig vertaalde UI, native scriptweergave en rechts-naar-links-ondersteuning voor Arabisch en 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.