eSIM for a layover: is it worth it for a few hours?

What a layover actually asks of your phone

A layover is not one task, it is a short list of them. You want the airline app for the boarding pass and the gate number. You want the notification that arrives when the gate moves or the departure slips. If the connection is tight, you want to be able to rebook without joining a queue at a transfer desk. You want to tell whoever is meeting you at the other end that you have landed. And if the stop is long enough that you leave the terminal, you want maps, a ride-hailing app, a translation app and a way to pay. Most of that list is small. A message, a boarding pass refresh, an app notification — none of it needs much bandwidth. What it needs is a connection that holds up at the exact minute something changes, which is usually the same minute everyone else in the terminal is trying to do the same thing. So the real question is not whether the airport has Wi-Fi. Most do, and many give it away. The question is whether that network will still be there, logged in and fast enough, when your gate changes. That is a per-airport question, and it is worth answering before you fly rather than at the gate.

Why airport Wi-Fi is often the weak link

Airport networks are built to be free at the point of use, which often means they are built with friction. The usual pattern is a captive portal: you connect, a page opens, and you accept terms or hand over an email address before anything loads. Some portals go further and want a phone number so they can text you a code. If your home line does not roam, or your phone is set to a line with no signal, that code may never arrive — and you have no data to work around it, because the thing you are trying to log into is the data. Then there is re-authentication. Sessions expire. Move from one concourse to another and you may have to sign in again, usually while walking with luggage. At peak hours, around the gates where everyone is waiting, the network tends to slow down exactly when the departure boards start changing. Some airports sell a faster tier, which tells you something about what the free tier is like. This is not true everywhere. Hub airports compete on passenger experience, and some run networks that are genuinely good — no registration, no time limit, fast enough to stream. But that is a reputation thing, not a category thing. You have to check the specific airport, and ideally the specific terminal, you are passing through. Recent traveller reports are a better source than the airport's own marketing page.

When it is not worth buying anything

Here is the case against, stated plainly. If your layover is two or three hours, you are staying airside, and you are not changing terminals, you will probably be fine on the airport's network. You are going to sit near a gate, watch the board, send a few messages and get back on a plane. That is a low-bandwidth, short-duration use case, and the annoyance of the captive portal is smaller than the chore of buying and installing a plan you will barely use. It is also worth checking what you already have. If you have bought a regional plan for the trip, the country you are transiting may already be on its coverage list, in which case there is nothing to buy — you just switch that line on when you land. If your home carrier's plan includes roaming in the country you are passing through, the same applies, and the answer costs nothing. There is a value argument too. Travel data plans are sold by validity window and data allowance, not by the hour. A plan bought to cover a three-hour stop is mostly a plan you will not use, and whatever allowance is left when the window closes does not carry over. One practical point that catches people out: installing an eSIM happens over an internet connection. If you decide at the gate, you are relying on the airport network to finish the install — the very connection you were unsure about.

The two-minute decision rule

Run through these and count the answers. They do not all need to point the same way. Length. Under about three hours with no terminal change, lean no. Five hours or more, or an overnight stop, lean yes. The longer the wait, the more chances of a delay or a gate change. Airside or landside. If you plan to leave the airport — a hotel, a meal, a short look at the city — you need data that works outside the terminal, and airport Wi-Fi becomes irrelevant. That one fact settles it. Delay risk. If the connection is tight, or the airline is having a bad day, your own data is what lets you rebook from your seat instead of from a queue. This matters more than the length of the layover. The specific airport. Look up recent reports for the airport and terminal you are transiting. A network with heavy registration, short session limits or a paid fast tier should be treated as no network at all. What you already own. A regional plan that covers the transit country, or a home plan that includes roaming there, means the decision is already made. If two or more of those point to yes, buy a plan for the stop. If all of them point to no, do not — and enjoy skipping a task at the gate.

If you do buy, buy for a few hours

For a layover you are buying reliability, not volume. Usage will be small: the airline app, messages, a boarding pass, a map lookup. What you need is a plan active on the right dates that connects the moment you switch it on. Check coverage first: a single-country plan for your destination will not cover a layover in a different country. If the trip crosses several countries, including the transit stop, a regional plan is the simpler purchase, and removes the risk of finding out at the gate that the stop is not included. Read the coverage list against your routing. Check what starts the clock. Providers differ on whether the validity window begins at installation or at the first connection to a network. On a short trip that decides whether the plan is still alive when you land. Data-only is normally the right shape. A few hours in a terminal rarely needs a local number. If you might need to call a hotel or a transfer service, check that the plan supports voice — many travel plans do not. Install it before you leave, on home Wi-Fi, days ahead if you can. Leave the line off, and turn it on when you land or the moment the airport network fails you. Keep your own number enabled for calls and codes, and set the travel plan as the data line. Some providers need roaming switched on for that line to attach to a partner network; their setup instructions will say so.

Keep reading