Form factor and capability are two different decisions
Most comparisons of IoT eSIM vs plastic SIM treat it as one choice: an old-fashioned card in a slot, or a modern chip soldered to the board. That framing mixes up two separate questions, and it leads to poor decisions.
The first question is form factor: is the SIM a removable card (2FF, 3FF or 4FF) or an embedded chip, usually the MFF2 package soldered to the circuit board? The second is capability: is it a conventional UICC that holds one operator’s identity for life, or an eUICC that can download, store and switch operator profiles remotely?
Those two questions combine in four ways, and all four exist in real deployments.
| Conventional UICC (one operator) | eUICC (remote profiles) | |
|---|---|---|
| Removable card | The classic plastic IoT SIM. Change operator by changing the card. | A removable eSIM card. Fits an existing SIM slot and supports remote profile switching, if the device and modem support it. |
| Embedded (MFF2) | Soldered and rugged, but locked to one operator for the device’s life. | What most people mean by “IoT eSIM”: soldered, rugged and remotely reprogrammable. |
The short version: “eSIM” describes what the SIM can do, not what it is made of. A plastic card can be an eUICC, and a soldered chip can be a conventional single-operator SIM.
1. Physical form and durability
Removable cards depend on a slot, a tray and spring contacts. In vibration, temperature cycling, damp or dusty environments those contacts are a common point of failure, and an accessible slot is also a tampering and theft risk. Industrial-grade cards with wider temperature ranges reduce the problem but don’t remove it.
An embedded MFF2 eUICC is soldered to the board, so there are no contacts to work loose and nothing to remove. That makes it the better physical choice for vehicles, outdoor equipment and anything installed where a site visit is expensive. The trade-off is that a soldered part can never be swapped by hand.
2. One operator or many
A conventional UICC carries a single operator profile, fixed when the card is made. Changing operator means changing the card.
An eUICC holds one or more operator profiles and can download new ones over the air. Normally one profile is active at a time, and how many the eUICC can store depends on its memory. That number is fixed at manufacture, so it is worth checking before you buy.
3. How provisioning works
With a conventional SIM, provisioning is physical and manual: order cards from the chosen provider, insert them on site or on the production line, configure the APN, and repeat the whole process if the provider or tariff changes.
With an eUICC, the device typically ships with a bootstrap profile that gives it enough connectivity to reach the provisioning system. An operational profile is then downloaded from the operator’s SM-DP+ server and enabled. Under SGP.32, the download is triggered and managed by an eSIM IoT Remote Manager (eIM), working with an IoT Profile Assistant (IPA) that sits either in the device (IPAd) or on the eUICC itself (IPAe).
The practical difference is that operator choice moves from the warehouse to the management platform. One hardware build can ship worldwide and pick up the right local profile when it is installed.
4. Three eSIM standards, three very different models
“IoT eSIM” has covered three generations of GSMA specification, and they behave very differently. A plastic UICC uses none of them.
| Standard | Designed for | Who controls profile changes | What it means in practice |
|---|---|---|---|
| SGP.02 | M2M | The operator, through its SM-SR platform | Remote provisioning works, but changing operator depends on the original one cooperating. Lock-in in practice. |
| SGP.22 | Consumer devices | The user, through an on-device assistant | Built around a person scanning a QR code or tapping a screen. Awkward for headless IoT devices. |
| SGP.32 | IoT | The device owner, through an eIM | Remote, scalable, no user interaction, and no dependence on the incumbent operator to release the device. |
The spec is part of the eUICC operating system and is fixed at manufacture: an SGP.22 eUICC can’t be upgraded to SGP.32 over the air. When comparing IoT eSIM options, ask which standard the eUICC is built to, not just whether it is an eSIM.
5. Remote swap and its real limits
Remote profile switching is the main reason to choose an eUICC. It allows a whole fleet to change provider for commercial or coverage reasons without a single site visit, and it can be scripted across thousands of devices through the management platform’s API.
It isn’t magic, though. A remote swap only works if:
- the device can still reach a network to receive the new profile;
- the eUICC has enough memory to hold the new profile alongside the current one;
- the modem passes the SIM toolkit and BIP traffic that profile management depends on;
- the new operator’s network uses a radio technology and bands the module supports.
Swaps also take time, typically minutes rather than milliseconds. They suit planned changes of provider, not moment-to-moment switching between networks as a vehicle crosses a border. That job is normally done by roaming or multi-network SIM services, which can sit on a conventional SIM or on an eUICC profile.
SGP.32 includes a fallback mechanism so that if a newly enabled profile can’t connect, the eUICC can return to a designated profile rather than leaving the device stranded. Always confirm how your provider and eIM handle fallback before running a fleet-wide swap.
6. Cost over the device’s life
Conventional SIMs are cheaper per unit and need no management platform. eUICCs cost more per unit and usually involve eIM or platform fees.
The comparison changes once the device is in the field. Every operator change on a conventional SIM costs a site visit per device, plus downtime. For a small fleet within easy reach, that can be cheaper than an eUICC platform. For a large, dispersed or long-life fleet, a single forced operator change can cost more than the eUICC premium on every device.
7. Manufacturing and stock
With conventional SIMs, manufacturers and distributors often hold different stock for different regions or providers, and the SIM is a separate item to source, fit and track.
An eUICC, especially an embedded one, allows a single hardware SKU for every market. The operator decision is deferred until the device is deployed, which simplifies stock, reduces the risk of shipping the wrong SIM, and makes it easier to change provider strategy without changing the product.
When a plastic SIM is still the right choice
A conventional removable SIM still makes sense for small deployments where devices are easy to reach, proof-of-concept and temporary installations, legacy hardware whose modem can’t support eUICC management, and projects that will only ever use one provider for a short life.
There is also a middle path that often gets overlooked. A removable eUICC card brings remote profile switching to existing devices with a standard SIM slot, provided the modem supports the toolkit and BIP functions involved. For estates of routers already in the field, that can be a far cheaper route to eSIM than replacing hardware.
How to choose
| Situation | Usually the best fit |
|---|---|
| Small, local, easy-to-reach deployment | Conventional removable SIM |
| Existing devices with SIM slots that need remote switching | Removable eUICC card |
| Harsh environment, vibration or tamper risk | Embedded MFF2 eUICC |
| Large, dispersed or multi-country fleet | Embedded MFF2 eUICC built to SGP.32 |
| Long-life device (10 years or more) | SGP.32 eUICC, with a removable path if field access is realistic |
Checklist before you specify
- Confirm the device’s modem supports eUICC management, including SIM toolkit and BIP.
- Specify SGP.32 for new IoT designs rather than SGP.02 or SGP.22.
- Check how many profiles the eUICC can store at once.
- Choose a bootstrap profile with broad, long-lived coverage.
- Agree how fallback works, and test it before any fleet-wide swap.
- Make sure eIM portability is in the contract, so you can change platform later.
- Decide early between public and private IP, and whether you need a private APN.
- Log every profile change and keep a rollback plan.
Frequently asked questions
Is an IoT eSIM the same as an eUICC?
Almost. The eUICC is the secure chip, with its own operating system, that stores and manages operator profiles. “eSIM” is the broader term for SIMs that can be provisioned remotely, and in IoT it usually means an eUICC.
Can a plastic SIM card be an eSIM?
Yes. Removable eUICC cards exist in standard SIM sizes. They behave like an eSIM for remote profile switching, but fit an ordinary SIM slot.
Can one eUICC store several operator profiles?
Yes, up to the limit of its memory. Normally one profile is active at a time.
What happens if a profile download or switch fails?
A failed download leaves the existing profile in place. If a newly enabled profile can’t connect, SGP.32’s fallback mechanism lets the eUICC return to a designated profile. Test this with your provider before relying on it.
Will my existing IoT routers support eSIM?
It depends on the modem and firmware rather than the router brand. Some routers have embedded eUICCs; many others can use a removable eUICC card in their existing slot if the modem supports the necessary SIM toolkit and BIP functions. Check the manufacturer’s specification for the exact model.
First published August 2025. Rewritten October 2026 to cover removable eUICC cards, the SGP.02, SGP.22 and SGP.32 standards, and the practical limits of remote profile switching.
