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.
- Best for
- Mobile carrier eSIM activation — one scan provisions the profile.
- Scans on
- iOS 12.1+ Camera, Android 10+ Camera.
- When not to use
- For physical SIMs or non-eSIM-capable devices.
- Standards
- GSMA SGP.22 LPA activation code.
- QR-generator
- Gratis visittkortdesigner
- Utskrivbare WiFi-kort
- Batch CSV (500 koder)
- 40 maler
- 20 språk
Kompatibilitetsforklaring
Dette strekkodeformatet rendres monokromt med bare forgrunns- og bakgrunnsfarger. Maler, prikk-/øyeformer, gradienter, rammer og sentrumslogoer gjelder kun QR-koder og er skjult her.
Vis 30 maler til
Lagre en stil med knappen over for å beholde favorittene dine her.
Eller velg et innebygd ikon:
Vis 108 ikoner til
Rendres bak QR-en med redusert opasitet. Tvinger automatisk EC=H slik at QR-en fortsatt skanner gjennom bildet.
Batchgenerering
Last opp en CSV for å generere opptil 500 QR-koder i én batch. Hver rad blir sin egen QR — velg en mal eller overstyr 21 egenskaper per rad: farger, rammer, prikk/øye/øyeeple-stiler, gradienter, gjennomsiktighet, størrelse, feilkorrigering, format, innebygd logo og mer.
21 kolonner: type, data, filename, frametext, frame, template, fgcolor, bgcolor, size, ec, dotstyle, eyestyle, format, logo, gradient, g2, gtype, gangle, transparent, eyeball, eyecolor. Kun type og data kreves. Bruk | for å skille felt inne i data (f.eks. ssid|password|WPA).
Alle 20 QR-typer støttes, inkludert URL, WiFi, vCard, MeCard, Email, SMS, Event, Location, UPI, SEPA, PayPal, Crypto, Micro QR og rMQR. Last ned eksempel-CSV for å se hver kolonne, alle 40 maler, 11 rammestiler og de 12 innebygde logoene i aksjon.
1. Last ned eksempel-CSV · 2. Rediger med dine data · 3. Last den opp her
Lagre hele QR-en — type, alle feltverdier, stil, ramme, logo, visittkortdesign — som en enkelt .qr.json-fil. Last den inn senere for å gjenskape alt med ett klikk.
Skriv inn innhold for å generere QR-koden din
E-signaturer som holder i retten
Abundera Sign går utover grunnleggende e-signaturer. Hvert dokument får kryptografisk bevis, uavhengig verifisering og en manipulasjonsbestandig bevispakke.
- Automatisk genererte rettsklare bevispakker
- Personlig dokumentsegl — oppdager manipulasjon umiddelbart
- Forankret til 5 uavhengige systemer — ingen enkelt feilpunkt
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.
Tilgjengelig på 26 språk
Fullt oversatt grensesnitt, native skriftgjengivelse og høyre-til-venstre-støtte for arabisk og 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.