Every few weeks someone asks me whether their next device should have an eSIM or an eUICC, as if they were choosing between two products on a shelf. They aren’t. In eSIM vs eUICC for IoT, one word mostly describes how the SIM is packaged and sold, and the other describes what the chip can actually do. Mix them up and you can end up soldering a chip to a board that will never change network, while believing you’ve future-proofed the device for fifteen years.
So let’s separate the two properly, because the difference decides what you can do with a device once it has left the building.
The short answer. An eUICC is the GSMA’s name for a SIM that can hold more than one operator profile and have new ones loaded remotely. “eSIM” is a looser word. On a phone it means an eUICC. On an IoT datasheet it very often just means a SIM chip soldered to the board, usually in the 5 x 6 mm MFF2 package, and that chip may or may not be an eUICC. Always ask two separate questions: what package is it in, and can it take a new operator profile over the air?
Why eSIM and eUICC get muddled
Three terms are doing the work here, and only one of them has a tight definition.
- UICC is the smart card platform every SIM has run on since 3G. It hosts the USIM application, and a conventional UICC carries one operator’s identity and keys, written in at the factory. If you want a different operator, you change the SIM. I covered how we got here in the story of the SIM card.
- eUICC is a UICC with a defined security architecture that lets it hold several operator profiles, enable one, disable another and download new ones remotely. That architecture is written down in the GSMA’s remote SIM provisioning specifications. The “e” originally stood for embedded, because the early assumption was that these chips would be soldered in. Today it’s a software and security capability, and you can buy it in a plastic card.
- eSIM is the word everybody actually uses. The GSMA uses it for its remote provisioning technology as a whole. Phone makers use it to mean “no SIM tray, scan a QR code”. And plenty of IoT suppliers use it to mean “the soldered one”, full stop.
That last habit is where the trouble starts. A soldered chip is a form factor. Remote provisioning is a capability. You can have either without the other.
Form factor and capability are two different axes
The easiest way I’ve found to explain it is a simple grid. Packaging goes one way, what the chip can do goes the other. Every SIM you can buy for an IoT device sits in one of these four boxes, with the integrated SIM sitting just below them.
The combinations you will actually meet
Here’s how those boxes turn up in real products, and what each one means once the device is in a cabinet, on a lamp post or bolted to a trailer.
| What you are sold | Package | Remote profile change? | Where it makes sense | Watch out for |
|---|---|---|---|---|
| Standard IoT SIM | Plastic 2FF, 3FF or 4FF | No | Routers and gateways where someone can reach the slot | A network change is a physical job across every site |
| Plastic eUICC | Plastic 2FF, 3FF or 4FF | Yes | Retrofitting existing routers, mixed estates, trials | Only works if the modem and firmware support the provisioning route |
| “eSIM” chip, single profile | Soldered MFF2 | No | Short-life or single-country devices that need vibration and temperature tolerance | Locks the hardware to one operator, often without the buyer realising |
| eUICC chip | Soldered MFF2 or smaller | Yes | Long-life, sealed or multi-country devices | Which GSMA spec it supports, and who controls the profiles |
| iSIM / integrated eUICC | Inside the modem chipset | Usually yes | Very small, low-power, high-volume devices | The chipset vendor’s ecosystem becomes part of your connectivity decision |
A note on that third row. Some soldered single-profile chips do allow the operator to update files and settings over the air, using the older remote file and applet management tools. That’s useful, but it isn’t the same as swapping in a different operator’s profile. If the datasheet doesn’t mention GSMA remote SIM provisioning, assume it can’t.
Not all eUICCs are the same eUICC
Once you’ve established that a chip really is an eUICC, there’s a second question that matters just as much: which GSMA specification does it follow? There are three families, and they work in quite different ways.
| Specification | Built for | Who drives a profile change | What it means for IoT |
|---|---|---|---|
| SGP.02 (M2M) | Machine-to-machine, cars, early IoT | The network side pushes changes to the chip through a subscription manager | Works, and still widely deployed, but switching operator usually needs the operators’ platforms integrated with each other |
| SGP.22 (consumer) | Phones, tablets, watches | The device, usually prompted by a person with a QR code or activation code | Common in eSIM routers, normally wrapped in the router vendor’s own management cloud |
| SGP.32 (IoT) | Unattended IoT devices with no screen or user | A remote manager called the eIM, talking to an IoT Profile Assistant (IPA) on the chip or the device | The one built for fleets. v1.3 was published in May 2026, with v1.2 still the certification baseline |
I’ve written at length about the third one, including why SGP.32 readiness depends on the device in the middle and which modules, eUICCs and routers support it. If you’re seeing SGP.22 problems in the field, this piece on SGP.22 provisioning failure modes is worth ten minutes.
My take: “eSIM” on a quote tells you almost nothing
When I see “eSIM” on a quote or a datasheet, I treat it the way I treat “industrial grade” or “5G ready”. It’s a starting point for questions, not an answer. It might mean a soldered chip with one operator burned in. It might mean a proper SGP.32 eUICC. It might mean an SGP.22 eUICC that only changes profile through the vendor’s own cloud. Those are three very different products with three very different futures.
The cost of getting it wrong isn’t on the invoice. It turns up five or eight years later, when a network sunsets a technology, a contract comes up for renewal or a customer moves the kit to another country, and you discover the only way to change operator is to send someone to every site with a soldering iron, or a new device. I’d rather pay a bit more for the chip on day one than pay for a call-out on every device later.
Equally, an eUICC is not automatically the right answer. A mains-powered router in a UK cabinet, with a removable SIM and a decent multi-network IoT tariff, may never need one. I go through when you do and don’t in what is an eUICC, and do you need one for IoT?
The trap to avoid. An eUICC gives you the technical ability to change operator. It doesn’t give you the commercial right to. Check who owns the bootstrap profile, who runs the remote manager and whether you can move both to another supplier. Otherwise the lock-in hasn’t gone away. It has just moved somewhere less obvious.
Six questions to ask before you sign
- What is the package? Plastic card, MFF2 or integrated into the modem.
- Is it an eUICC, and to which GSMA specification? SGP.02, SGP.22 or SGP.32, and which version.
- Is the eUICC certified? Ask for the GSMA compliance and security assurance details for the exact part.
- Does the device support it? The modem, its firmware and, for SGP.32, the IPA mode all need to line up. A clever chip in an unsupportive device is a very expensive ordinary SIM.
- Which profiles can I actually load? Get the list of operators and countries in writing, not “hundreds of networks”.
- Can I take it with me? Who controls the profiles and the remote manager, and what happens if you change connectivity supplier?
If you’re buying connectivity rather than chips, you don’t buy SGP.32 covers the commercial side, and our IoT eSIM guide looks at providers, public IP and private IP options.
eSIM vs eUICC: quick answers
What is the difference between eSIM and eUICC?
eUICC is the GSMA term for a SIM that can store several operator profiles and have new ones downloaded remotely. eSIM is a broader, looser term. In phones it means an eUICC; in IoT it often just means a SIM chip soldered to the board, which may or may not be an eUICC.
Is every MFF2 eSIM an eUICC?
No. MFF2 is a 5 x 6 mm package defined by ETSI for soldered SIMs. Plenty of MFF2 chips carry a single fixed operator profile. Only an MFF2 chip that supports GSMA remote SIM provisioning is an eUICC.
Can an eUICC be a removable plastic SIM?
Yes. Plastic eUICCs exist in the standard 2FF, 3FF and 4FF sizes, and they are a common way to add remote profile switching to routers already in the field, provided the device supports the provisioning method.
Which eUICC standard should IoT devices use?
For new unattended IoT devices, SGP.32 is the GSMA standard designed for the job, managed through an eIM rather than a person or a QR code. Many current routers use SGP.22 with a vendor cloud, and older M2M deployments use SGP.02.
Is iSIM the same as an eUICC?
iSIM puts the SIM function inside the modem chipset instead of on a separate chip. It is usually built as an integrated eUICC, so it can still take remote profiles, but it is a different package rather than a different capability.
Sources: GSMA, eSIM consumer and IoT specifications status table; GSMA, SGP.32 v1.3 eSIM IoT Technical Specification (May 2026); GSMA, SGP.22 RSP Technical Specification, eUICC architecture; ETSI TS 102 671, machine-to-machine UICC form factors (MFF2). Diagram by IoTPortal.
The eSIM explained series: Part 1: eSIM vs eUICC (you are here) · Part 2: What is an eUICC? · Part 3: What is an eIM? · Part 4: SGP.32’s three-body problem



