> For the complete documentation index, see [llms.txt](https://docs.eseye.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eseye.com/anynet-sim/managing-sims/choose-the-right-anynet-sim-size.md).

# Choose the right AnyNet SIM size

AnyNet+ SIMs come in several sizes, called form factors. The right one depends on the SIM slot in your device, or whether the device has a SIM built in. Use this page to work out which size to order.

## Check your device first

Look in your device's datasheet or user guide for the SIM slot size. If the device has no slot because the SIM is soldered onto the board, you need the embedded size.

## Compare the sizes

| **Form factor** | **Size (L x W x H)** | **When to choose it**                                                   |
| --------------- | -------------------- | ----------------------------------------------------------------------- |
| Mini (2FF)      | 25 x 15 x 0.76 mm    | Devices with a standard Mini-SIM slot. Supplied in a full-size carrier. |
| Micro (3FF)     | 15 x 12 x 0.76 mm    | Devices with a micro-SIM slot.                                          |
| Nano (4FF)      | 12.3 x 8.8 x 0.67 mm | Small devices with a nano-SIM slot.                                     |
| Embedded (MFF2) | 6 x 5 x 0.9 mm       | Devices where the SIM is soldered permanently onto the board.           |

The original full-size SIM (1FF) is no longer produced.

## Order your SIMs

1. Note the form factor your device needs.
2. Check how many SIMs you need for your deployment.
3. Contact your Account Manager to place the order.

For iSIMs, contact your Account Manager.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.eseye.com/anynet-sim/managing-sims/choose-the-right-anynet-sim-size.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.