What is an MFF2 SIM Card: A Practical Guide for IoT Deployments

An MFF2 SIM card is a type of SIM used in IoT devices, soldered directly onto the device’s circuit board rather than inserted into a removable slot. It becomes a permanent part of the hardware, meaning it can’t be removed, swapped, or physically accessed after the device is built.

The term “MFF2” refers specifically to the form factor (the physical format of the SIM), not how connectivity is managed. That distinction matters. Many people use “eSIM” as a blanket term, but in fact, MFF2 and eSIM are not the same thing. MFF2 describes how the SIM is installed, while eSIM (more precisely, eUICC) describes whether you can manage network profiles remotely.

In real deployments, MFF2 is commonly used in devices that need to run for years without maintenance. Think vehicle trackers, industrial sensors, or equipment installed in hard-to-reach locations. Once the device is deployed, there’s usually no practical way to open it and replace a SIM card, so the connectivity has to be built in from the start and expected to last.

What Is an MFF2 SIM Card?

An MFF2 SIM card is a small, embedded SIM that is soldered directly onto a device’s circuit board during manufacturing. Unlike a standard SIM card that sits in a tray and can be removed or replaced, an MFF2 SIM becomes a fixed part of the hardware. Once the device is assembled, the SIM stays in place for its entire lifecycle.

The term “MFF2” refers to the SIM's physical format, not to how connectivity is managed. That’s where some confusion usually comes in. People often use “eSIM” to describe anything embedded, but technically, eSIM (or eUICC) is about remote profile management. An MFF2 SIM can support eUICC, but it doesn’t have to. You can have an MFF2 SIM without remote provisioning, and you can have eUICC on other form factors as well.

MFF2 is widely used in IoT devices that are deployed once and expected to operate for years without being opened. The goal is to make connectivity part of the device from the start, since there's no easy way to access the SIM after installation.

How is an MFF2 SIM different from a regular SIM card?

At a glance, a regular and an MFF2 SIM card do the same job: they connect a device to a cellular network. The difference becomes clear when you look at how they’re built into the device and what happens after deployment.

A regular SIM card (often called 3-in-1) is designed to be inserted and removed when needed. It sits in a tray or slot, which makes it easy to swap between devices or replace it if something goes wrong. That works well for equipment that’s easy to access. With MFF2, the SIM is soldered directly onto the PCB (Printed Circuit Board) and integrated during manufacturing, so there is no slot, no tray, and no practical way to remove it later. It’s treated as part of the device itself, not an external component.

This changes how devices are built and handled at scale. Instead of inserting SIM cards during setup or in the field, everything is integrated upfront. Devices leave production already equipped with connectivity, which simplifies assembly and avoids small but recurring issues like loose contacts or incorrectly inserted cards.

If you want a deeper look at how these two approaches compare in real deployments, this breakdown of 3-in-1 vs MFF2 IoT SIM goes into more detail.

Why So IoT Devices Use MFF2 SIM cards?

Most IoT devices are built on a very different assumption from consumer electronics: once they’re installed, they’re not meant to be touched again. That changes how every component is chosen, including the SIM.

One of the main reasons MFF2 is used is its reliability. A removable SIM relies on physical contacts between the card and the tray, and over time, those points can degrade, especially in environments with vibration, dust, or temperature swings. With MFF2, the SIM is soldered directly onto the board, so there’s no connector to loosen or wear out. In practice, that makes a noticeable difference for devices operating in vehicles, outdoor installations, or industrial settings where conditions are far from stable.

There’s also the question of how long the device is expected to run. It’s not unusual for IoT deployments to stay in the field for five, sometimes ten years or more. Sending someone out to replace or reseat a SIM card sounds simple until you multiply it across hundreds or thousands of units, often spread across different regions. Using an embedded format avoids that entire category of maintenance from the start.

Manufacturing is another aspect that often goes unnoticed. When SIM cards are inserted manually, even small inconsistencies can slow things down or introduce errors at scale. With MFF2, the SIM is integrated during the standard assembly process, so every device leaves the production line in the same state, already equipped with connectivity.

Is MFF2 the Same as eSIM?

Short answer: no, they’re not the same thing, even though they’re often used interchangeably.

MFF2 describes how the SIM is physically built into the device. It tells you that the SIM is embedded and soldered onto the board. eSIM, on the other hand, is about functionality, specifically, whether the SIM can be managed remotely, with profiles added or changed over the air.

MFF2 vs eUICC (eSIM Capability)

To be more precise, what people usually call “eSIM” is actually eUICC (embedded Universal Integrated Circuit Card). That’s the feature that allows remote provisioning. It lets you download, switch, or update operator profiles without physically touching the device.

An MFF2 SIM can support eUICC, but it doesn’t have to. Some deployments use MFF2 with fixed connectivity, where everything is configured upfront and doesn’t change. Others combine MFF2 with eUICC to allow more flexibility over time.

How Connectivity Works on an MFF2 SIM Card

The MFF2 format only specifies how the SIM is inserted into the device. It doesn’t define how the device connects to networks or how that connection is managed over time. That part depends on the SIM architecture and the provider behind it.

Two devices with identical MFF2 SIMs can behave very differently depending on how connectivity is set up. The differences show up in how networks are selected, how failures are handled, and how much control you have after deployment.

Multi-IMSI SIMs

One common approach is using a SIM that stores multiple IMSI profiles. Each IMSI represents a different operator identity, and the device can switch between them based on location or predefined rules. This setup gives some flexibility, especially in regions where coverage varies between carriers.

On paper, it sounds straightforward. In reality, it can get a bit messy. The list of available IMSIs is usually defined in advance, which means the set of networks is fixed from the start. If something changes later (new markets, new requirements, or issues with a specific operator), adjusting that setup isn’t always simple. There’s also some overhead in managing how and when the SIM switches between identities.

If you want a deeper look at how this model works, this breakdown of Multi-IMSI IoT SIM Card goes into more detail.

eUICC (Remote Profile Management)

Another option is eUICC, which enables remote management of operator profiles. Instead of storing multiple identities on the SIM from the beginning, profiles can be downloaded, updated, or replaced over the air.

This gives more flexibility, especially for deployments that span multiple countries or need to adapt over time. At the same time, it introduces another layer that has to be managed. Profiles need to be distributed, lifecycle rules need to be defined, and the system handling all of this has to stay in sync with the devices in the field. For some teams, that’s a fair trade-off. For others, it adds complexity they didn’t plan for.

Single Global Profile Approach

There’s also a different way to structure connectivity, where the SIM itself stays relatively simple and most of the logic moves into the network platform. In this model, the SIM operates with a single global identity, while network selection and routing decisions are handled centrally.

From the device perspective, the behavior is more consistent. It connects to available networks without switching between multiple IMSIs or downloading profiles. From an operational standpoint, it reduces the amount of SIM-level management required, since changes can be handled through the platform rather than on each device.

This approach doesn’t eliminate all complexity, but it shifts it into a place where it’s easier to control and scale, especially when dealing with large fleets across multiple regions.

MFF2 vs Other Embedded SIM Options

MFF2 is often the default choice for embedded SIM deployments, but it’s not the only option on the table. Over the past few years, newer approaches have begun to emerge, each seeking to solve similar problems in slightly different ways.

MFF-XS

MFF-XS follows the same idea as MFF2, but in a smaller package. It’s designed for devices with extremely limited board space, such as compact sensors or wearables.

In theory, it offers similar capabilities while taking up less space. In practice, it hasn’t seen the same level of adoption. The ecosystem is still catching up, which means fewer modules support it and fewer suppliers build around it. For teams working on large-scale deployments, that lack of standardization can slow things down or limit options.

iSIM

iSIM takes a different route by integrating SIM functionality directly into the device’s main chipset. There’s no separate SIM component at all; everything is handled inside the system-on-chip.

That can simplify hardware design and reduce space requirements, but it comes with a trade-off that tends to show up later. Because the SIM is tied to the chipset, decisions about connectivity become closely linked to the chip vendor. If you need to change providers, adjust how connectivity is managed, or support new regions, those dependencies can make things less flexible than expected.

SoftSIM

SoftSIM pushes the idea further by moving SIM functionality entirely into software. Instead of relying on dedicated hardware, identity and authentication are handled within the device’s software stack.

This offers greater flexibility from a manufacturing perspective, since there’s no SIM component to install. At the same time, it raises questions around security models, standardization, and long-term support. Adoption is still evolving, and not every network or use case supports it in the same way.

Comparison of embedded SIM options

How MFF2 SIM Cards Are Used in Real IoT Deployments

Most IoT deployments don’t happen in controlled environments. Devices move, operate in different regions, or sit in hard-to-reach places. In those conditions, the SIM has to work as part of the system without requiring attention.

Fleet Tracking Across Countries

Fleet tracking is a good example of a use case where MFF2 makes sense. Vehicles move between cities, regions, and sometimes countries, so the device must stay connected across different networks without interruption.

Using a removable SIM would technically work, but it introduces a dependency on physical access. If something goes wrong or connectivity needs adjustment, someone has to intervene. With MFF2, the SIM is already part of the device, so the focus shifts to how connectivity is managed rather than how the SIM is handled. In setups like these, having a global IoT SIM that supports multiple networks helps maintain stable data transmission without constant adjustments.

Industrial Equipment in Remote Locations

Industrial deployments often occur in environments where devices are installed once and left alone. That could be equipment in a remote facility, infrastructure along transport routes, or systems placed in areas where regular maintenance isn’t practical.

In these cases, the ability to physically access a SIM card is rarely part of the plan. The expectation is that the device will operate for years with minimal intervention. MFF2 fits that model because it removes the need for any interaction with the SIM itself. Combined with a stable connectivity setup, it reduces the risk of unexpected downtime caused by something as simple as a hardware connection issue.

Agriculture IoT Sensors

Agriculture deployments tend to deal with uneven coverage. Sensors are often distributed across large areas, sometimes in locations where signal quality varies with the network.

Here, the challenge isn’t just durability, but also maintaining connectivity when conditions aren’t ideal. Devices need to attach to whichever network performs best in a given location, and do so consistently over time. An embedded SIM like MFF2 ensures the hardware side remains stable, while the connectivity layer handles network selection and data routing.

In all of these scenarios, the SIM itself isn’t the part teams want to think about after deployment. It’s expected to work quietly in the background while the focus stays on the device and the data it produces. This is also where solutions like Keepgo IoT SIM, available in both MFF2 and 3-in-1 formats, tend to fit, since they are designed to support different deployment models without requiring changes to how devices are built or managed.

Common challenges when deploying MFF2 SIM cards

Choosing an embedded SIM solves many hardware-related issues, but it doesn’t eliminate the questions teams usually have before rollout. In most cases, the uncertainty isn’t about the form factor itself — it’s about whether the connectivity will actually hold up once devices are in the field.

• Coverage and network compatibility. Coverage maps may appear reliable on paper, but actual performance is contingent on the SIM's interaction with local carriers, the supported technologies (LTE, LTE-M, and NB-IoT), and the practical handling of network selection.
• Device and platform integration. The SIM has to work with the device firmware, the cellular module, and the platform that processes the data. Issues tend to show up when something in that chain behaves differently than expected, especially with third-party fleet management systems or custom backends.
• Testing before deployment. Validating connectivity across multiple regions is not always straightforward. It’s one thing to test in a lab or a single country and another to confirm that the same setup works consistently across different markets. Without proper testing, teams often discover gaps after deployment, when fixes are more difficult to implement.
• Integration and engineering effort. Even when the SIM itself works as expected, integrating it into an existing system can take time. API connections, data handling, and device management all need to be aligned. For smaller teams or companies with limited engineering resources, this step can become a bottleneck.
• Reliability and provider stability. There’s also a longer-term concern that tends to come up during evaluation. If connectivity is built into the device, switching providers later is not trivial. That makes provider stability and network uptime serious considerations, since any disruption can directly affect the product and the end-customer experience.

How to Choose MFF2 SIM Cards Connectivity Provider

With MFF2, the SIM is part of the device, so changing providers later isn’t something you want to rely on. Most teams take a cautious approach here, shortlist a few providers, then validate them through testing rather than specs alone. If you want a structured view of that process, this guide on how to choose an IoT SIM card provider covers it in more detail.

What matters most is how connectivity behaves in real conditions. Coverage lists are a starting point, but the real questions are which networks the SIM connects to, whether it supports LTE, LTE-M, or NB-IoT where needed, and how stable those connections are.

Testing usually gives the clearest answers. Running SIMs in a few target locations helps catch issues early, whether it’s network performance or integration with your device and platform.

If you’re still evaluating, it’s worth starting with a test kit and validating everything end-to-end. And if parts of the setup are unclear, a quick discussion with a provider like Keepgo can help you figure out what to expect before scaling.

Frequently Asked Questions about MFF2 SIM Cards

Is MFF2 the same as eSIM?

Not exactly. MFF2 refers to the physical format of the SIM. It’s soldered into the device. eSIM (or eUICC) refers to the ability to manage profiles remotely. An MFF2 SIM can support eSIM functionality, but the two terms describe different things.

Can MFF2 SIM cards be replaced?

No, they’re not designed to be replaced. Since the SIM is soldered directly onto the PCB during manufacturing, accessing it later would require disassembling the device. In most cases, that’s not practical, so the setup is meant to stay unchanged.

Do MFF2 SIM cards support LTE-M and NB-IoT?

They can, but it depends on the module and the connectivity provider. The SIM itself doesn’t define the supported technologies. The device hardware and the network capabilities available in each region determine those.

How do you test MFF2 connectivity before deployment?

Testing usually happens with development units or test kits before full production. Teams run the SIM in real devices, often across a few target locations, to check network behavior, signal stability, and integration with their platform.

Are MFF2 SIM cards suitable for global deployments?

Yes, they’re commonly used in global deployments, especially when devices need to operate across multiple countries without physical maintenance. The key factor is choosing a provider that can support consistent connectivity across those regions.