eUICC and eSIM are used as if they mean the same thing. They do not, and the difference decides whether a connected device can change network after it has shipped or stays tied to one operator for its working life. For a deployment expected to run for years across several countries, that is a procurement decision, not a technicality.
What is eUICC?
eUICC stands for embedded Universal Integrated Circuit Card. It is the GSMA-standardised capability that lets a single SIM store more than one mobile operator profile and switch between them remotely, over the air, without anyone handling the device. The point most explanations get wrong is that eUICC is a capability defined by a standard, not a particular piece of hardware.
The same eUICC capability can sit on a removable card in the familiar 2FF, 3FF and 4FF sizes, on a soldered-in embedded chip (MFF2), or on an integrated SIM built into a device’s processor. When people talk about an eUICC SIM, they mean a SIM that can hold and manage several network profiles, whatever its physical shape.
eUICC vs eSIM: the difference that matters
This is where the language collapses. eSIM most precisely describes a form factor, the embedded SIM soldered into a device, though the term is often stretched to cover the whole remote provisioning arrangement. eUICC describes the software capability that makes remote profile switching possible.
An eSIM almost always includes eUICC, but eUICC is not limited to eSIM hardware. You can have a removable card that is eUICC-capable, and you can have an embedded chip that is not. Treating the two as identical leads teams to assume that choosing an embedded SIM automatically gives them the freedom to change operator later. It does not. That freedom comes from eUICC, and from a provider whose infrastructure can actually carry out the switch.
| Term | What it actually is | How the network changes | Typical IoT fit |
|---|---|---|---|
| Traditional SIM (UICC) | A card holding a single operator identity | Physically swap the SIM | Fixed, single-network deployments |
| eSIM | A form factor: the embedded, non-removable SIM | Depends on whether it is eUICC-capable | Space-constrained or sealed devices |
| eUICC | A capability: stores and switches multiple profiles remotely | Download or switch operator profiles over the air | Long-life devices that may change operator after shipping |
| Multi-IMSI | Multiple network identities on one SIM | Switch identity in the network core | Coverage resilience needed today, low device overhead |
How eUICC works, and what remote SIM provisioning involves
Remote SIM provisioning, or RSP, is the process that does the work. A device usually ships with a bootstrap profile, just enough connectivity to reach the provisioning servers, then downloads a full operational profile once it is in the field. From that point the operational profile behaves like any other network subscription. Only one profile is active at a time, though several can be stored and switched between.
The switching is handled by back-end components: subscription management systems that prepare, protect and deliver the operator credentials to the SIM. Under the earlier GSMA M2M standard, SGP.02, this relied on a Subscription Manager Secure Routing component. The consumer standard, SGP.22, moved more of the control onto the device itself. For IoT, the direction of travel is a newer standard again, covered next.
Where the standards are heading: SGP.32
SGP.32 is the GSMA specification for remote SIM provisioning built specifically for IoT, published to address the limits of earlier standards on constrained and unattended devices. It removes the dependence on the older secure-routing component and introduces an eSIM IoT Manager to orchestrate profile changes across a fleet. It is still maturing, so credible providers describe SGP.32 in terms of readiness and roadmap rather than a finished feature. OV ONE is designed to support current eUICC standards and to adopt SGP.32 as it matures. There is a fuller explanation in our guide to SGP.32.
eUICC or multi-IMSI: which fits an IoT deployment
For deployments that need network resilience today, without the provisioning overhead, multi-IMSI is usually the more practical starting point. It switches between pre-loaded network identities in the core, which places less demand on the device and works well where the goal is simply staying connected across regions. eUICC earns its place when you need to change operator profile after devices are deployed, run very long device lifecycles, or must load a local profile to meet in-country regulatory rules.
In practice the two are not rivals. Many real deployments use a multi-IMSI SIM for everyday coverage, with eUICC available where a full profile change is genuinely required.
What catches teams out
The most common surprise is power. Downloading a profile takes a stable connection for long enough to complete, and battery-powered or intermittently connected devices often wake for only a few seconds. If the connection window is too short, the profile download fails and the device is left in an awkward state. Deployments with sleepy or low-power devices need to plan provisioning around this rather than assume it happens instantly.
The second is the provider gap. Hardware can be eUICC-compliant while the connectivity provider has no working remote provisioning back end to perform the switch. The SIM is capable; the service is not. This is why procurement should test the switch, not just read the datasheet. Certification and interoperability between operators also matter, because a profile change only works if both sides of the exchange are properly integrated.
The third is the assumption that an embedded SIM automatically means multi-network freedom. As above, embedded is a form factor. Without eUICC and a provider able to provision it, an embedded SIM can be just as locked to one network as a soldered-in single-profile chip.
Choosing an eUICC SIM provider
The hardware is rarely the hard part. The provider is. The things worth checking are multi-network reach, integration at operator level rather than a resold layer, a single interface to manage profiles and SIM lifecycle, an API to automate it, and a credible SGP.32 roadmap.
OV operates as a Global IoT Mobile Network Operator with direct integration into its own network core, across 180+ countries and 600+ networks. OV ONE, built in-house by OV engineers, gives teams provisioning, real-time monitoring and SIM lifecycle control from a single interface, with every function also available through a documented API. Network access policies let you control which networks devices use, and OV ONE supports bulk operations of up to 1,000 SIMs at a time. OV’s IoT eSIM is designed to support current eUICC standards and to migrate to SGP.32 as the standard matures.
Evaluating eUICC or multi-IMSI for a deployment? The most reliable way to see how either behaves is to test it on real hardware over a live network. Request a free IoT SIM trial, or talk to the OV team about your deployment.
Frequently asked questions
What is an eUICC?
An eUICC (embedded Universal Integrated Circuit Card) is the GSMA-standardised capability that lets one SIM hold several mobile operator profiles and switch between them remotely, over the air. It is a standard rather than a fixed piece of hardware, so it can appear on a removable card, a soldered embedded chip, or an integrated SIM. Its purpose is to let a device change network without anyone physically swapping the SIM.
Is eUICC the same as eSIM?
No. eSIM most precisely describes a form factor, the embedded SIM soldered into a device, while eUICC describes the software capability that allows remote profile switching. Most eSIMs include eUICC, but eUICC can also run on removable and integrated SIMs. Choosing an embedded SIM does not on its own let you change operator later; that comes from eUICC and a provider able to carry out the switch.
What is the difference between eUICC and eSIM?
The simplest way to hold the two apart is that eSIM is about the hardware, the physical form the SIM takes, and eUICC is about what that hardware can do. eUICC is the reprogrammable capability that stores and switches operator profiles remotely, and eSIM is one of several form factors that capability can live in. For procurement, the useful question is not whether a device has an eSIM but whether it is eUICC-capable and whether the provider can actually provision and switch profiles.
What is an eUICC SIM card?
An eUICC SIM card is a SIM whose chip can store more than one operator profile and accept new profiles over the air, rather than being locked to a single network for life. It can be a removable card or an embedded chip. On its own the card is only half the picture, because remote switching also depends on the provider running the remote SIM provisioning back end that delivers and activates profiles.
How does eUICC differ from multi-IMSI?
Multi-IMSI stores several network identities on one SIM and switches between them in the network core, which is lighter on the device and effective for coverage resilience today. eUICC goes further by allowing whole operator profiles to be downloaded and changed after deployment, which matters for long device lifecycles and local regulatory requirements. Many IoT deployments use both, with multi-IMSI for everyday coverage and eUICC where a full profile change is needed.
What is SGP.32?
SGP.32 is the GSMA specification for remote SIM provisioning built specifically for IoT, published to address the limits of earlier standards on constrained and unattended devices. It removes the dependence on the older secure-routing component and introduces an eSIM IoT Manager to orchestrate profile changes at fleet scale. It is still maturing, so providers describe SGP.32 support in terms of readiness and roadmap rather than a finished feature.
