Should You Use a VPN on Cellular Data Abroad? The Upload Used Less Data When It Stopped Restarting

The insurance upload failed at 78 percent while the clinic receptionist was preparing to close her desk. I was in Split, Croatia, trying to send my partner’s passport page, policy certificate and treatment estimate to our travel insurer. She had already been examined and her wrist was immobilized. What remained was administrative: the insurer needed the documents and a short video verification before issuing its direct-payment guarantee. I blamed the clinic’s guest Wi-Fi, disconnected from it and moved the phone onto my travel eSIM. The upload restarted, reached 41 percent and stopped again.

The insurer’s claims desk closed in thirty-one minutes.

Without the guarantee, we could still pay the clinic ourselves and claim reimbursement later. The amount was manageable, but it would consume most of the card balance we needed for the rest of the trip.

The receptionist looked at the frozen progress bar.

“Maybe send one file at a time?”

I had already compressed the scans and combined them into a 34-megabyte PDF.

The size was not unusual.

The connection was.

My phone showed four bars and 5G. The insurer’s page opened quickly. Messages arrived. Maps worked.

But the upload would not remain alive long enough to finish.

The travel eSIM solved access, not stability

I had kept my home line active for calls and verification messages while assigning cellular data to a prepaid travel eSIM. Modern phones make that arrangement straightforward: the home number remains available while the travel line handles data. (Apple Support)

It had worked well for maps, restaurant bookings and messages.

Inside the clinic, however, the roaming connection kept changing. Near the entrance, the phone showed 5G. In the treatment room, it dropped to LTE. In the corridor, data disappeared for several seconds even though the signal bars remained.

Other travelers report the same practical frustration: the phone still appears connected while a travel eSIM moves between 4G, 5G and no usable data. (Reddit)

A map can recover from that quietly.

A document upload may begin again.

That was the real problem in front of me. Cellular data was available, but it was not stable enough to carry the complete insurance claim.

Cellular data did not make the VPN unnecessary

Cellular data felt safer than the clinic’s open guest Wi-Fi.

That did not mean I wanted to send passport and medical documents without a VPN. Official mobile-security guidance still recommends using a reputable VPN for sensitive work while traveling, including on foreign cellular networks. (National Security Agency)

My hesitation was data usage.

The travel plan had 1.7 gigabytes left, and a VPN adds some overhead because traffic must pass through the encrypted tunnel. (Google Fi Wireless Help)

But the same 34-megabyte document had already restarted several times.

The overhead was not consuming my allowance.

Failure was.

The useful question was no longer whether a VPN used extra data. It was whether the VPN could stop me from uploading the same data repeatedly.

The familiar provider connected cleanly and recovered badly

I had used the same major VPN provider for years.

It had a long public history, broad server coverage and a support operation I trusted. Those were sensible reasons to open it first.

I selected a nearby European route.

The connection established immediately.

The insurer portal opened.

I signed in and approved a code sent to my home number.

The PDF upload reached 52 percent.

The phone changed from 5G to LTE.

The VPN displayed Reconnecting.

The portal returned to the document page with no file attached.

I selected another nearby server and tried again.

This attempt reached 86 percent.

Then the phone briefly lost data in the corridor. When the connection returned, the VPN had moved to another endpoint.

The insurer asked me to sign in again.

The receptionist glanced at the clock.

“Twenty minutes,” she said.

She was not trying to pressure me. The claims desk in another time zone was the real deadline.

Still, every percentage point now felt expensive.

Turning the VPN off did not fix the roaming connection

I disconnected the VPN to test whether the tunnel itself was causing the failure.

The insurer’s portal loaded faster.

I signed in again.

The upload reached 63 percent before the cellular connection disappeared.

The phone still showed signal bars.

The page stopped moving.

I toggled airplane mode, waited for the eSIM to reconnect and returned to the insurer’s site.

The session had expired.

Removing the VPN had removed one layer, but it had not made the roaming connection stable.

It had also left me preparing to resend passport and clinic documents through a connection I did not want to use directly.

That attempt settled the broader question.

Cellular data was a useful alternative to public Wi-Fi.

It was not a reason to abandon the VPN during a sensitive task.

The VPN simply had to handle the same instability as the phone.

Another server would create another restart

I returned to the established provider and tried a server with a lower reported load.

The file began uploading again.

While it moved, the claims agent sent a message through the portal:

After upload, remain online for identity verification. Do not leave the session.

That changed the test.

Finishing the PDF was no longer enough.

The same connection had to carry the upload, preserve the login, open a video check and remain active until the guarantee number appeared.

The major provider offered plenty of servers, but choosing among them was consuming the minutes I needed to complete the claim.

A new route might reconnect faster.

It could also mean another login, another address and another restart.

I closed the server menu with fourteen minutes remaining.

The smaller app began with the situation

I had installed OnlydogVPN^↗ before the trip but had not made it my default.

The established provider had more locations, more ratings and a much longer public record. The smaller service’s shorter history was why I had kept it as a backup.

But I did not need another list of cities.

I needed a protected route for sensitive documents on unstable cellular data.

I selected that situation in the app.

The connection established.

I reopened the insurer portal and completed the verification code one final time.

The PDF began uploading.

It passed 52 percent.

Then 78, where the first attempt had failed.

The cellular indicator changed from 5G to LTE.

The upload continued.

At 94 percent, the phone briefly showed no data.

The progress bar paused.

The connection returned.

The bar moved again.

Then the portal displayed:

Documents received

The claims agent opened the video check.

I held my passport beside my face, confirmed the policy number and turned the camera toward my partner’s clinic wristband.

The agent asked the receptionist to show the treatment estimate.

She held it in front of the phone.

“Thank you,” the agent said. “Please stay connected while I generate the guarantee.”

A minute later, the portal displayed a reference number.

The receptionist entered it into the clinic system.

“Approved,” she said.

That completed the task.

One completed upload used less data than four failed ones

The service uses an HTTP/3-based connection designed to remain usable when a mobile network weakens or changes.

The practical difference was already visible.

The established provider rebuilt its connection when the phone changed network conditions, and the insurer discarded the interrupted upload.

The direct connection lost the authenticated session when roaming data disappeared.

The backup paused, recovered and finished.

I could not observe the insurer’s or cellular carrier’s internal network rules. I could compare what happened on the phone.

The successful VPN attempt added some tunnel traffic.

It also prevented another full upload, another login code and another video-verification restart.

For this task, finishing once mattered more than minimizing the overhead on every packet.

The clinic door created the final handoff

The claim was approved, but the guarantee PDF had not yet arrived.

The receptionist closed her desk and asked us to wait near the entrance.

As we moved through the building, the phone returned to 5G.

Then it dropped to LTE outside.

The VPN remained connected.

The insurer’s message arrived:

Payment guarantee attached

I downloaded the PDF and forwarded it to the clinic’s billing address.

The receptionist checked her computer from behind the locked glass door and gave me a thumbs-up.

The main problem had already been solved.

The network recovery protected the smaller final step: delivering the document that proved it.

Without that recovery, I might have had a reference number in the portal but no copy for the clinic.

Signal bars measured the wrong thing

Before that afternoon, I had treated strong cellular signal as evidence that the connection was stable.

It was not.

The bars showed that the phone could reach the nearby mobile network. They did not promise that a roaming session, VPN connection or browser upload would survive every handoff.

The same was true of the 5G label.

5G looked reassuring while the document restarted.

LTE looked slower while the successful upload continued.

The useful questions were less visible:

Did the VPN stay connected when the phone’s network changed?

Did the upload continue rather than begin again?

Did the insurer retain the authenticated session?

Did the video check open inside the same claim?

Did the guarantee arrive before the claims desk closed?

The smaller route completed that sequence.

The answer depended on the task

I would not send every map search or café menu through a distant VPN server while traveling.

Cellular data was often the most practical connection available, and unnecessary routing could add delay and data use.

But the clinic claim was not casual browsing.

It involved identity documents, medical paperwork, account access and a deadline.

For that task, using a VPN on cellular data made sense.

The important choice was not cellular data or VPN, as though one replaced the other.

Cellular data was the underlying connection.

The VPN had to keep the complete sensitive task alive on top of it.

The established provider remained the larger and more familiar company. It offered more regions, more reviews and years of public history.

Its connection also turned one insurance claim into repeated uploads and expired sessions.

The smaller backup had fewer locations and a shorter record.

It was also the option that carried the passport file, video verification and payment guarantee across the same unstable roaming connection.

I had worried that a VPN would waste my cellular data abroad.

The insurer approved the claim on the attempt that finally stopped making me upload the same data again.