Section 2 · Register

Getting Started

Reports from soil, water, and living systems — each with its method, instrument, and measured uncertainty stated up front, so the work can be repeated in another field or another season.

85 reportsUpdated 2026-84-03Sorted by receipt
Setting up your phone with an eSIM in Canada

Setting up your phone with an eSIM in Canada

For a US traveler setting up service in Canada, you are choosing between two methods: purchasing and installing a physical SIM card upon arrival versus utilizing a carrier-provided eSIM profile…

13 SepOpen →
Switching to an eSIM from any major mobile provider

Switching to an eSIM from any major mobile provider

“What is an eSIM?”…

4 SepOpen →
How to manage an eSIM on mobile devices

How to manage an eSIM on mobile devices

“How does eSIM work?” The simplest answer is that it replaces a physical piece of plastic with software capability, allowing your phone to download and manage cellular subscription profiles remotely…

30 AugOpen →
Understanding your smartphone's eSIM capability

Understanding your smartphone's eSIM capability

eSIM, at its core, is not a physical card you pop into a tray; it is an embedded software profile within your phone that allows you to securely store and manage multiple mobile network operator…

29 AugOpen →

The main decision in getting started with eSIM is not which phone to buy but which provisioning standard your device and carrier actually speak: consumer phones and tablets run on GSMA SGP.22, automotive and industrial deployments have historically used SGP.02, and the newer IoT standard is SGP.32. If you are setting up a normal phone, you are in SGP.22 territory, the consumer specification currently sitting at version v2.6.1, and almost everything else follows from understanding what that standard does and does not let you do.

What an eSIM actually is, and what it is not

An eSIM is not a chip you activate once and forget. It is an eUICC — an Embedded Universal Integrated Circuit Card — defined by GSMA to store and manage multiple mobile network operator profiles on a single soldered-down component. The "e" stands for embedded, not electronic, and the practical consequence is that the SIM credential is now software that can be provisioned, swapped and deleted over the air rather than plastic you physically move between phones.

The mechanism that makes this work is Remote SIM Provisioning, or RSP: the GSMA-defined process for downloading, installing, enabling, disabling and deleting a subscription profile on the eUICC without a removable card. When you scan a carrier QR code or tap "add eSIM" in your phone's settings, you are triggering an RSP flow. The phone asks the carrier's provisioning server for a profile, the server issues one bound to your device's eUICC, and the profile lands in a secure enclave on the chip. From that point the carrier treats it as a live subscription exactly as it would a physical SIM.

The thing people most often get wrong is assuming an eSIM holds one number. It does not. A single eUICC can store multiple operator profiles, and the standard is built around that: you can hold a home profile and a travel profile side by side, or a work line and a personal line, and switch which one is active without deleting the other. What you cannot generally do is run more than one or two of them simultaneously — that limit is set by the modem and the radio hardware, not by the eUICC, and it varies by device. The profile storage is generous; the active-connection slots are not.

The trade-off of all this is that you lose the one thing a plastic SIM gave you for free: physical transferability. A dead phone with a physical SIM means pulling the card and dropping it into a spare handset in under a minute. With an eSIM, recovery depends on the carrier's re-provisioning process, which may mean a support call, an identity check, or a new QR code issued to a different device. That is the real cost of getting started, and it is worth knowing before you commit your primary line.

Which standard applies to your device

Consumer phones, tablets and laptops use GSMA SGP.22, the Remote SIM Provisioning architecture for consumer devices. That is the specification behind every mainstream eSIM activation you have encountered: the QR code on a carrier card, the in-app "install eSIM" button, the transfer flow when you move from an old iPhone to a new one. If you are setting up a personal device, SGP.22 is the only standard you need to think about.

The other two matter mainly if you are buying hardware for a fleet, a vehicle, or an industrial deployment. SGP.02 is the M2M specification, built for devices that are provisioned once and expected to run for years without a human touching them — telematics units, smart meters, asset trackers. SGP.32 is the newer IoT specification, designed to bring over-the-air profile management to IoT devices that previously could not support it cleanly. The split exists because consumer provisioning assumes a person with a screen and a decision; M2M and IoT provisioning assume nobody is there.

Where this bites a normal buyer is in grey-market hardware. A cheap imported tracker or a second-hand connected device may be built to SGP.02 and will not accept a consumer SGP.22 profile no matter what the listing claims. The tell is usually in the setup: consumer activation asks you to scan a QR code or confirm in an app, while an M2M device expects the carrier to push a profile to it remotely with no user interaction at all. If you are being asked to do nothing and the device still is not connecting, you may have the wrong standard, not a broken device.

The limits are worth stating plainly: standards compliance does not guarantee carrier support. A device can implement SGP.22 correctly and still fail to activate because your operator has not certified that model. The specification defines the plumbing; the carrier decides who gets to use it.

The decisions you make before you activate anything

The first decision is whether your primary line becomes an eSIM at all, and the honest answer for most people is: not on day one. Keep your main number on a physical SIM until you have used an eSIM for something low-stakes — a travel data plan, a second line, a tablet — and seen how your carrier handles installation, transfer and support. The failure modes are not catastrophic but they are inconvenient, and you want to discover them on a line you can afford to lose for an afternoon rather than the number tied to your bank's two-factor authentication.

The second decision is carrier support, and it is more fragmented than the marketing suggests. Check three things before you commit: that your specific operator offers eSIM on your specific plan (prepaid often lags postpaid), that your specific device model is on their supported list, and that the activation method they use — QR code, app, or carrier-side push — is one your device handles. A carrier that only supports app-based activation is useless if you are provisioning a tablet with no cellular app store access.

The third decision is how many lines you actually need active at once. Holding multiple profiles is easy; running them simultaneously is a hardware question. If your reason for wanting an eSIM is dual-number life — work and personal, home and abroad — confirm your device supports dual eSIM active standby before you buy, because the spec allows the storage and the modem may not allow the concurrency.

What this costs you is time up front and flexibility later. The trade is real: you are trading the ability to swap a card between any two unlocked phones for the ability to hold several profiles and switch them in software. For someone who changes phones rarely and travels often, that is a good trade. For someone who keeps a drawer of spare handsets for emergencies, it is a worse one.

Installing a profile, step by step

Consumer eSIM installation under SGP.22 runs through one of three routes: a QR code supplied by the carrier, an activation inside the carrier's own app, or a transfer from a previous device during setup. All three do the same thing — deliver a profile to your eUICC over the air — but they fail in different places, and knowing which route you are on tells you where to look when it goes wrong.

The step people skip is the deletion of the old profile. Installing a new one does not always remove the old one, and a stale profile left enabled can cause the phone to hold onto a network it should have released. Go into the eSIM settings after activation and confirm exactly one profile is enabled for the line you intend to use. The other thing to check: give the profile a label you will recognise months later, because "Secondary" tells you nothing when you are standing in an airport trying to work out which line has data.

The limits here are practical rather than technical. Installation needs a working data connection and, for QR routes, a code your carrier has actually issued and not already consumed. Neither of those is guaranteed at the moment you need them, which is why the sensible sequence is to install travel profiles before you leave, on home Wi-Fi, rather than at the arrival gate.

Living with it: switching, travel and keeping a spare

The everyday experience of an eSIM is switching, and switching is where the gap between the spec and the hardware shows. Your eUICC may hold multiple operator profiles, but the number you can have active at once is a device property. Practically, this means you choose a default line for calls and messages and a default line for data, and you change those defaults when you travel rather than juggling active connections.

For travel, the pattern that works is: buy a data-only eSIM for the destination before you fly, install it at home, and leave it disabled until you land. On arrival, enable it and set it as the data line while keeping your home line active for calls and messages — that way your bank's verification texts still arrive, and you are not paying your home carrier's roaming data rate. The thing that catches people is the messaging default: if your travel line is set as the default for messages, your ordinary texts may go out from a number nobody recognises. Set the defaults deliberately, once, before you rely on them.

Keeping a spare is the part most guides skip. With a physical SIM, the spare is a card in a drawer. With an eSIM, the spare is a carrier process you have hopefully tested before you needed it. Find out now how your operator handles a lost or broken device: whether they can reissue a profile to a new eUICC without a store visit, whether there is a charge, and how long it takes. Some carriers handle it in an app in minutes; others require identity verification that you cannot complete without the phone you just lost. That asymmetry is the single strongest argument for keeping your primary number on plastic until you have confirmed your carrier's recovery path is one you can live with.

The honest trade-off of the whole arrangement: eSIM is better at holding options and worse at surviving disasters. If your life involves frequent number changes, multiple countries, or several devices, the flexibility is worth the recovery risk. If it involves one number, one phone and a preference for things that work when everything else has failed, a physical SIM in the primary slot is still the more robust choice, and there is no shame in running an eSIM only for the second line.

What goes wrong, and how you notice it

Most eSIM failures fall into a small set of recognisable patterns, and each has a distinct symptom that tells you where the problem sits. Knowing the symptom saves you the support call, or at least gets you to the right department faster.

SymptomLikely causeFirst move
QR code scan returns an error immediatelyCode already used, expired, or issued for a different deviceRequest a fresh activation from the carrier; do not retry the same code
Profile installs but shows "no service"Profile not enabled, or the line is not set as active for dataCheck eSIM settings for an enabled profile and correct line defaults
Install stalls partway throughNo data connection during download, or carrier server timeoutReconnect to Wi-Fi and restart; if the profile is half-installed, delete it before retrying
Device will not accept the profile at allDevice not on the carrier's supported list, or built to a different provisioning standardConfirm the model against the carrier's list before assuming hardware fault
Old line still active after transferPrevious profile not deleted or disabledRemove the old profile explicitly; do not rely on the transfer to clean up

The pattern behind most of these is that the failure surfaces on the device while the cause sits with the carrier — an unissued code, an uncertified model, a policy that blocks transfer. That is why the first move is almost always to establish which side of the provisioning chain owns the problem. A profile that installs cleanly and then fails to register is a carrier or coverage issue; a profile that will not install at all is usually a code or compatibility issue.

What you cannot fix from the device is a carrier that has not certified your hardware or does not support the activation route you need. That is a limit of the ecosystem rather than of the standard: SGP.22 defines how profiles move, not who is obliged to issue them. Before you buy any eSIM-only device, the certification check is worth more than any specification sheet, because a perfectly compliant phone from an unsupported model line is still a phone that will not activate.