eSIM vs Physical SIM — Technical Trade-offs
The shift from physical SIM to eSIM (eUICC) is one of the biggest changes in mobile technology. But from a technical perspective, what are the real differences? This comparison focuses on the developer and system integrator perspective — profile provisioning, security architecture, and hardware implications.
Technical Comparison
| Feature | Physical SIM (UICC) | eSIM (eUICC) |
|---|---|---|
| Form Factor | Removable (2FF/3FF/4FF) | Soldered MFF2 or iSIM (integrated) |
| Profile Switching | Physical swap required | Remote download via RSP (GSMA SGP.22) |
| Multiple Profiles | 1 per card | Multiple profiles (typically 2-8) |
| Security Architecture | Single security domain | ISD-R + ISD-P hierarchy (GlobalPlatform) |
| Device Size Impact | SIM tray + connector required | No tray — saves PCB space |
| Water Resistance | SIM tray is ingress point | No opening — better sealing |
| Carrier Lock-in | Low — swap SIM | Higher — profile policy can restrict |
| Remote Provisioning | No | Yes (SM-DP+, LPA) |
| IoT/M2M Suitability | Poor (physical access needed) | Excellent (remote lifecycle mgmt) |
| Cost per Unit | ~$0.10-0.30 | ~$0.50-1.50 (MFF2), ~$0 (iSIM) |
Developer Implications
eSIM requires understanding GSMA SGP.22
Working with eSIM means dealing with LPA (LPAd + LPAe), SM-DP+, BPP (Bound Profile Package), and the ES10a/b/c APDU interface. Physical SIM development is simpler — you read/write files. eSIM development requires understanding the full GSMA RSP stack.
We have a complete eSIM & eUICC Architecture Guide for the deep dive.
Physical SIM is still dominant for testing
For smart card development and testing, physical SIM cards remain more accessible. You can buy blank programmable SIM cards, use PC/SC readers, and test USIM applets directly. eSIM testing requires eUICC-capable hardware and SM-DP+ sandbox access.
Related
eSIM & eUICC Architecture Guide | APDU Command Builder | T=0 vs T=1 Protocol