How much data ride-hailing and food delivery really use
The numbers are far smaller than travellers fear, but this is the data you cannot afford to be out of at five in the morning waiting for an airport car.
Quick answer
- Booking one ride costs roughly 2–5 MB, and watching the car move on the map until you arrive adds roughly another 3–8 MB per trip.
- Delivery apps cost several times more because a menu page is wall-to-wall photographs — roughly 10–25 MB per browsing session.
- Set the pickup point and book while you are still on the hotel Wi-Fi, then walk down to wait — no gambling on the signal outside the lobby.
Ride-hailing apps such as Grab, or whichever local equivalent runs in the city you are visiting, use roughly 2–5 MB to book a ride and roughly another 3–8 MB to follow the car on the map until the trip ends. A complete journey therefore sits somewhere around 5–13 MB, which is less than a few minutes of short-form video. These are planning estimates rather than measurements from your handset, and they move mostly with how long you spend dragging the map before you confirm.
What people get wrong is not the size of the number but its importance. This is a trivial slice of a trip's data and an absolutely non-negotiable one, because it is needed at the worst possible moments: outside the hotel at five in the morning heading for a flight, or in the rain after the restaurant has closed. If your plan happens to empty right then, you cannot summon a car, cannot see where it is, and cannot message a driver who may be parked across the street.
Rough figures, action by action
| What you are doing in the app | Roughly how much | A 7-day trip at this rate |
|---|---|---|
| Booking one ride | Roughly 2–5 MB | 2 rides a day ≈ 30–70 MB |
| Live-tracking the car to your destination | Roughly 3–8 MB per trip | 2 trips a day ≈ 40–110 MB |
| Panning the in-app map to set a pickup point | Roughly 2–5 MB each time | 3 times a day ≈ 40–105 MB |
| Browsing menus in a delivery app | Roughly 10–25 MB per session | Once a day ≈ 70–175 MB |
| The app refreshing in the background | Roughly 20–50 MB a day | Across 7 days ≈ 140–350 MB |
| Messaging or calling the driver in-app | Roughly 0.5–2 MB per trip | 2 trips a day ≈ 7–28 MB |
Every figure here is a planning estimate, not a measurement.
The two most interesting rows are the last ones. Actually hailing cars for a whole week may not reach 200 MB, yet the app refreshing in your pocket and an evening of menu browsing can together outweigh the real use several times over. Delivery apps are built so you scroll through beautiful food photography across dozens of restaurants, and every one of those photographs is data. If you want to browse, do it on the hotel Wi-Fi and place the order when you get back to the room rather than standing on a street corner deciding.
Set the pickup point while still on Wi-Fi
This is the single habit that pays back most, and not only in data. While you are still in the room or a lobby with Wi-Fi, open the app, drop the pickup pin, enter the destination and let it show you the route and the rough time. The part that costs both data and time is dragging the map around hunting for the right pickup spot, especially at a hotel with several entrances or down a lane no car can enter. Get that done while you are still comfortable, and all that is left downstairs is confirming.
- Open the app while still on Wi-Fi and let it finish loading the map around you. Tiles it has already fetched are cached for a while, so reopening it downstairs pulls down very little.
- Put the pin on the door you will actually walk out of. At a large hotel, type the entrance or street name in as well, so the driver does not wait on the far side of the building while you trade calls.
- Enter the destination now too. For an airport, name the terminal and the airline, because a big airport has several drop-off points and being set down at the wrong one costs half an hour on foot.
- If you are leaving in a few minutes, book the car while still on Wi-Fi and then walk down. The lift having no signal does not matter, because the booking has already gone through.
Delivery apps are the heavy half
A delivery app's screen is wall-to-wall high-resolution photography: promotional banners, hero shots and a cover image for every restaurant you scroll past. Ten minutes of that costs roughly 10–25 MB, more than two or three rides put together, and browsing idly every evening for a week turns into hundreds of megabytes before you have ordered a single dish.
- Pick the restaurant on Wi-Fi and leave it in the basket, then place the order when you are actually hungry. Submitting an order costs very little next to the browsing that precedes it.
- Turn off Background App Refresh for delivery apps on iOS under Settings > General > Background App Refresh, or the app's Background data on Android under Settings > Apps > that app > Mobile data. They like to pre-fetch fresh promotions you never asked for.
- Keep notifications on for the ride app and off for delivery promotions. A notification itself is tiny, but every time you tap one you load a page full of photographs.
- If the city runs on a local app that everybody there actually uses, install it over Wi-Fi at home. Downloading a new app abroad can cost hundreds of megabytes at the exact moment you are in the biggest hurry.
When the plan really is nearly empty
If you are genuinely low and still have to move, prioritise like this: hailing a car and seeing where it is come first, and everything else waits. Switch on the system data saver, stop photo and mail syncing, and reserve what remains for the apps that get you from place to place, because those last few megabytes are worth more than at any other point in the trip.
The other habit people forget is keeping an offline fallback. Before leaving the hotel, screenshot the address in both English and the local script, the hotel's phone number and a rough route back. A screenshot needs no connection at all, and if everything fails at once you can still hold the screen up to a taxi driver at the kerb — which is sometimes faster than trying to nurse the app back to life.
FAQ
Can I still book a ride with only a few dozen megabytes left?+
Comfortably, since a booking plus live tracking together come to roughly 5–13 MB. The risk is not the ride app but everything else on the phone quietly spending your last megabytes on photo sync or an update, so switch the system data saver on before you tap to book.
Why do delivery apps cost several times more than ride apps?+
Because they are sending completely different things. A ride app sends coordinates and short messages, which weigh almost nothing. A delivery app sends high-resolution photographs of every dish in every restaurant you scroll past, and a single image can outweigh the tracking for an entire trip.
What happens if my data runs out while the car is on its way?+
The confirmed booking survives: the driver still sees the pickup pin and still comes. What you lose is live tracking and in-app chat. If your usual line can still take calls, the driver can normally reach you. The best response is to stand exactly on the pin you dropped and not wander.
How much of a 7-day plan should I set aside for getting around?+
For hailing and tracking alone, roughly 200–300 MB is generous. Add an evening of menu browsing most days and roughly 500 MB to 1 GB is the safer allowance. Put your own rides-per-day into the calculator to see the trip as a whole.
Instagram and TikTok have no web share button, so we open your phone's share sheet or copy the link instead.