What Are the Differences between SIM, eSIM and iSIM?
By Amelie Huart
May 14, 2026
Estimated reading time: 9 minutes

The physical SIM card has been part of cellular connectivity for decades. It plays a leading role in many consumer mobile devices and Internet of Things (IoT) deployments. However, the SIM market is evolving rapidly, and newer options eliminate the need for a removable SIM.
The embedded SIM (eSIM) is soldered to a device’s printed circuit board (PCB). It provides a way to send SIM profiles to devices over the air using remote SIM provisioning.
The latest iteration in the SIM market is the integrated SIM (iSIM). It streamlines the eSIM’s functionality by porting it into a system-on-a-chip (SOC) architecture. This capability means the SIM does not require dedicated hardware.
Counterpoint Technology Market Research expects that by 2030, around 70% of cellular devices will use an eSIM. Furthermore, the report shows iSIM dominating as the preferred SIM form factor across all cellular categories.

The traditional SIM is a removable card that comes in various sizes. It was first developed for the consumer mobile phone market and inherited by the machine-to-machine (M2M) industry.
Traditional SIMs evolved into new form factors to fit smaller devices. They are straightforward and convenient for consumer applications and some IoT use cases. However, they can present reliability and security risks for large-scale device deployments.
When SIMs are easy to access, they’re also subject to stealing or tampering. IoT managers must monitor SIM cards in their devices. Otherwise, someone could remove them and place the SIMs in other devices.
Traditional SIMs are convenient for an organization that needs to change device profiles when switching mobile carriers. All that one must do is remove the old SIM and plug in the new one. However, removing and replacing SIM cards on multiple devices in large-scale IoT deployments can be costly or impossible.
There are two primary forms of security accreditation for eSIMs and SIMs. The first is the Evaluation Assurance Level (EAL) standard. Created by Common Criteria, it is a security level adopted by the mobile network operator (MNO) community.
If a chip manufacturer attains EAL4+ certification, the hardware is processed to ensure it is not vulnerable. Carriers ensure that their SIM vendors comply with this standard, which includes the chip’s physical security. It applies to traditional SIM cards and eSIMs.
The GSMA provides a Security Accreditation Scheme (SAS) with two different specifications. It applies to SIMs and eSIMs as well as remote provisioning servers.
This specification guarantees that the SIM’s manufacturing site meets physical security standards. SAS-UP also ensures that the site follows strict security procedures for personalizing and producing SIMs.
The SAS-SM specification provides security auditing and accreditation. This is for providers who want to offer remote provisioning services to MNOs and OEMs.
GSMA also runs the embedded Universal Integrated Circuit Card (eUICC) eUICC Security Assurance (eSA) scheme designed specifically for eUICC security certification.

Embedded SIM (eSIM) originally referred only to a SIM soldered in a device. The term now also refers to an eUICC-enabled SIM that can support multiple MNO profiles through remote provisioning. eUICC is a global solution.
eSIM can refer to an embedded SIM or a SIM that can host multiple MNO profiles. In practice, “eSIM” often refers to eUICC capability. That capability extends beyond a soldered form factor.
The connected car industry drove the adoption of eSIM. To address traditional SIM limitations in certain use cases, automotive OEMs developed a tamper-proof SIM with stronger security. Such a SIM would serve their connection needs and protect against extreme environmental conditions, including:
Today, the automotive industry has widely adopted the technology, and most connected cars use soldered eSIMs.
The eUICC is defined within the GSMA remote SIM provisioning specifications. It allows remote provisioning of the hardware with connectivity profiles. Including remote SIM provisioning on the service and card sides makes the eSIM versatile.
The standard allows MNOs to remotely send their SIM profiles to eSIM devices. By removing the need for physical access, eUICC enhances connectivity management for IoT deployments at scale.
The eUICC standard also enables multiple profiles to be loaded. Devices manufactured for global use are switched to the appropriate regional provider profile when deployed or moved.
GSMA’s eSIM for IoT specifications include SGP.31 and SGP.32. SGP.31 defines the architecture and requirements for remote provisioning in network- or user-interface-constrained IoT devices. SGP.32 defines the technical implementation that enables remote profile download and life cycle operations at scale.

OEMs must create devices that are data- and energy-efficient and minimize bill of materials (BOM) costs. They can achieve this by leveraging low-tier IoT cellular options such as narrowband IoT (NB-IoT) and LTE-M.
iSIM technology incorporates the SIM operating system into the cellular module hardware. It enables industries to provide coverage with data and energy efficiency.
Every square millimeter makes a difference in size-constrained applications. The iSIM is a space saver in hardware design and can reduce the device footprint. It does not require physical space for an eSIM chip or a removable SIM card.
With iSIM functionality built into the base cellular module, there is no need for separate SIM hardware. This results in savings from eliminating such components as:
iSIM is now standardized. The GSMA launched an integrated eUICC (ieUICC) technology initiative in 2015. This resulted in a proof of concept (PoC) demonstrated in 2017. Since then, the integrated eUICC has been considered in the existing RSP specifications for devices, including:

The SAS-UP requirements have been adapted for iSIM production. iSIM production involves the SoC manufacturer and the SIM operating system (OS) supplier. The GSMA has defined a two-step personalization process:
For iSIM, two-step personalization occurs before the in-factory profile provisioning process. The in-factory provisioning process applies to both eSIM and iSIM.
The GSMA in-factory provisioning process is still being specified. Although the architecture and requirements document (SGP.41) is ready, the full standard, including the test specifications, is not expected until 2027.
Even though most of the standards are defined, large-scale iSIM (ieUICC) adoption will take time. The SoC makers must prove the hardware’s robustness. The vendors must adapt their tools and processes to comply with the GSMA two-step personalization.
eUICC implementations, including iSIM-based eUICCs, must demonstrate functional compliance with GSMA RSP requirements. GSMA IoT test specifications in the SGP.33 series provide test coverage for eSIM IoT technology (SGP.31/32). The GSMA RSP compliance process is defined in SGP.24 and covers both consumer and IoT eSIM specifications.
Ecosystem adoption is progressing through pilots and early implementations. Broader commercialization depends on interoperability testing and certification readiness across suppliers.

Debating between SIM, eSIM and iSIM? When selecting a SIM type and form factor for your IoT deployment, start by considering cost structure. It reflects the business model behind the device.
For example, in the automotive sector, the final product’s cost might motivate you to invest in expensive chips. Embracing a less expensive platform would mean compromising on resiliency and security.
If your product is a low-tier device, such as a pet tracker, spending an extra dollar or two on hardware per device could eliminate your profit margin. In that case, seeking a low-cost iSIM solution makes sense.
Also, consider whether the use case will require remote provisioning. While eSIMs are best known for this feature, all form factors are candidates for eUICC software that enables OTA profile updates.
GSMA has designed a large-scale provisioning scheme for the IoT space. MNOs can provision devices in large volumes simultaneously.
Remote SIM provisioning is a core capability of eUICC-based SIMs. It simplifies connectivity management for devices deployed across multiple regions or for equipment expected to change networks over time. In these scenarios, the ability to download and manage operator profiles remotely can reduce operational effort and support long device life cycles.
The economics of remote provisioning vary by deployment. Platform fees and integration effort can add cost. Ongoing management requirements also factor into the overall business case. These investments are easier to justify in devices with moderate to high data usage or in solutions designed for extended service life. Low-tier IoT devices with narrow margins may realize fewer advantages from advanced provisioning capabilities.
Network conditions also influence provisioning strategy. Reliable connectivity is required to complete profile downloads and updates. Devices operating in areas with limited or inconsistent coverage may face constraints that affect how provisioning is managed.
For these reasons, remote provisioning should be evaluated in context. Device cost plays an important role in that decision. Connectivity conditions and life cycle expectations should also be considered. In many deployments, remote provisioning delivers clear operational advantages. In others, a simpler connectivity approach may be more appropriate.
Despite the huge growth of eSIM and iSIM, traditional SIM cards continue to exist in the IoT market — at least for now. In many countries, prepaid service remains the predominant way to connect, making traditional SIM cards the most practical choice.
For high-end IoT use cases with an inherently higher cost structure that require a high degree of MNO acceptance from the first day, eSIMs are an ideal solution. iSIMs will come into play for low-tier IoT connections where device size and energy efficiency are necessary strengths.
There’s a lot to consider when choosing between SIM, eSIM and iSIM. Depending on the use case, there’s room for every form factor and SIM type for the foreseeable future.
Speak with our experts today to learn more about SIM technology.
What is iSIM?
An integrated SIM (iSIM) is a next-generation SIM technology. It embeds SIM functionality into a device’s main processor.
Unlike traditional SIM cards or embedded SIMs (eSIMs), iSIM doesn’t require a separate chip. This feature:
iSIM is valuable for compact, low-power devices like wearables and IoT sensors.
What is eSIM?
An embedded SIM (eSIM) is a physical component that can host multiple connectivity profiles (“digital SIM”). It can be embedded on a device or standalone. It allows users to activate cellular service and switch carriers without inserting or replacing a physical SIM card.
eSIMs are remotely programmable, making them ideal for IoT devices like smartphones and wearables. This technology simplifies logistics and enhances security. In addition, eSIMs support global connectivity through remote provisioning.
How does an eSIM work?
An eSIM works in IoT devices by embedding initial connectivity profile(s) to allow the device to connect to cellular networks.
eSIMs enable remote provisioning. Connectivity profiles can be downloaded over the air. This is useful for large-scale IoT deployments in which managing physical SIMs would be impractical.
In addition, eSIMs support switching carriers remotely. This helps optimize connectivity and costs across different regions.
What is the difference between a SIM card and an SD card?
A Subscriber Identity Module (SIM) card enables cellular connectivity. It allows the IoT device to connect to mobile networks (like LTE or 5G) to send and receive data. This is essential for devices deployed in the field (e.g., smart meters or remote sensors) where Wi-Fi or wired connections aren’t available.
A secure digital (SD) card provides local storage. It’s used to store data, including:
This is useful for edge devices that need to operate offline or buffer data before uploading it to the cloud.
In short:
Many IoT devices use both:
Editor’s note: This blog was originally published on 6 May 2020 and has since been updated.