Crew WiFi Is Slow: 11 Fixes That Actually Work
Some links on this page are affiliate links. If you buy through them we may earn a commission at no extra cost to you — it never changes which product we recommend.
Crew WiFi is slow because forty people are sharing one satellite link that was sized for the bridge, not for you. You cannot fix the bandwidth. You can change when you use it, what you ask it to do, and how much of your data budget goes to things you never chose to download. Those three levers are worth more than any gadget you can buy in the next port.
I have been sailing as an engineer long enough to have used every generation of this problem, from a 512 kbps VSAT shared across the whole crew to a Starlink terminal that still crawls at 21:00 when the entire ship is on video calls. The advice below is what I actually do, in the order I do it.
Why crew WiFi is slow in the first place
Crew WiFi is slow for three separate reasons, and they need three different fixes. Confusing them is why people buy the wrong thing.
Reason one is the satellite link itself. On a VSAT ship you might be sharing 2 to 8 Mbps across everyone onboard. On a Starlink ship the raw speed can be very good, tens of Mbps, but latency spikes and dropouts still happen when the terminal loses line of sight behind a crane or an accommodation block.
Reason two is contention. Bandwidth is shared. At 21:00 ship time, when the day workers are off and the watchkeepers are on break, everyone hits the link at once. The same connection that gave you 6 Mbps at 05:00 gives you 0.3 Mbps at 21:00. Nothing is broken. There are just more of you.
Reason three is the WiFi itself, which has nothing to do with the satellite. Ship accommodation is steel boxes stacked on steel boxes. An access point in the crew mess does not reach into a cabin two decks down through three bulkheads. Your phone shows one bar, decides the connection is bad, and starts retransmitting, which slows the access point down for everyone else in range.
Test which one you have before spending money. Run a speed test at 05:00 and again at 21:00, standing in the same place. If the numbers are wildly different, that is contention and no equipment will help. Then run a test in the crew mess and in your cabin at the same hour. If the mess is fast and the cabin is dead, that is a WiFi coverage problem, and a portable router in your cabin genuinely does fix it.
The single biggest win: stop background traffic
Most of your data is spent on things you did not ask for. On a slow shared link, background traffic is the difference between a usable connection and a dead one.
Here is what runs without asking you:
- Photo backup. iCloud Photos and Google Photos will happily push a 4K video of the main engine you filmed this morning. That is a few hundred megabytes at satellite speed, which can be an hour of the whole ship's bandwidth.
- App and OS updates. A phone with 40 apps downloads a few hundred megabytes a week on its own. iOS and Android point updates run into gigabytes.
- Cloud drive sync. Dropbox, OneDrive and Google Drive sync in both directions the moment they see WiFi.
- Messaging app media auto-download. WhatsApp downloading every video in a family group chat is a classic way to burn a crew data allowance in two days.
Turn all of it off before you connect, not after. On iOS, set the ship network as a Low Data Mode network in the WiFi settings for that network, then switch off iCloud Photos upload over WiFi and disable automatic app updates. On Android, mark the ship network as a metered connection under WiFi network details, which makes the operating system treat it like a limited mobile plan and holds back most background sync. In WhatsApp, set media auto-download to "no media" for WiFi as well as mobile, because most people only change the mobile setting.
Do this once and you free up more bandwidth than any other single action on this page.
Time your usage around the ship's rhythm
The fastest connection on the ship is at 04:00 to 06:00, and it is not close. Everyone is asleep, the link is nearly empty, and a download that would fail at 21:00 completes in minutes.
Ship connectivity has a very predictable daily curve. Learn yours and work with it.
| Time (ship time) | Typical load | Best used for |
|---|---|---|
| 04:00 to 06:00 | Very low | Big downloads, OS updates, uploading photos, video calls if the family time zone allows |
| 06:00 to 08:00 | Rising | Email, messages, banking |
| 08:00 to 17:00 | Moderate, dips during work | Normal browsing, work portals, course video downloads |
| 17:00 to 20:00 | Heavy | Text messaging only |
| 20:00 to 23:00 | Peak, worst of the day | Voice notes instead of calls, plain text, nothing heavy |
| 23:00 to 04:00 | Falling | Second best window for large transfers |
If you are on watch at 04:00, you already have the best internet on the ship and you may not have noticed. Queue your downloads before you go up, and they will be done by the time you come off.
The other rhythm worth learning is the port call. Coastal coverage often improves near the terminal, and many ships lift restrictions in port. If your ship allows personal SIMs, an eSIM data plan bought before arrival turns a two hour gangway wait into your real internet session for the week. I install the Airalo profile over ship wifi the day before, so it is already sitting on the phone ready to switch on the moment a local network is in range. That is where I do everything the ship link cannot handle.
Fix the WiFi side, which you can actually control
Cabin WiFi problems are usually about distance and interference, and both have cheap fixes.
Move toward the access point. This sounds obvious and people still do not do it. Standing in the alleyway outside your cabin, or in the mess, can be the difference between 1 bar and 4 bars. Signal through a steel bulkhead drops hard.
Use 2.4 GHz, not 5 GHz, when you are far from the AP. 2.4 GHz is slower at close range and travels much further through obstacles. If the ship broadcasts both bands as separate names, connect to the 2.4 GHz one from your cabin and the 5 GHz one when you are sitting in the mess. This one change fixes a lot of "my cabin has no internet" complaints.
Get your phone off the shared WiFi when you are not using it. A phone hunting for a weak signal keeps talking to the access point and slows down everyone in range. Switch WiFi off when you go to bed.
A cabin router with a directional client mode helps, when the problem is coverage. It connects to the ship AP from a better position, for example clipped near the cabin door or a porthole, then rebroadcasts a strong local signal for your devices. It does not create bandwidth. It only recovers what the bulkheads were eating.
Check what the ship actually permits first. Some operators forbid personal routers on the crew network, and on a few ships plugging one in gets you a conversation with the ETO. Ask before you install anything.
Make each app use less data
Every app has a setting that decides how much bandwidth it wants, and the defaults assume you have fibre at home.
Video calls are the big one. A standard video call to family uses roughly 0.5 to 1.5 Mbps in each direction. Voice only uses around 0.05 Mbps. On a congested ship link, voice connects and holds when video will not even ring. WhatsApp voice, Messenger voice and Signal voice are all workable at speeds where video is hopeless. Tell your family in advance that voice at sea is a technical decision, so nobody thinks you are hiding a bad mood.
Streaming needs the same treatment. Set YouTube playback quality to 144p or 240p manually, because auto quality will keep trying for higher and buffer forever. For anything you plan to watch properly, download it in the quiet window rather than streaming it live. Our guide to watching Netflix onboard covers the download workflow in detail, and it applies to Spotify and podcast apps too.
Some more per-app settings worth changing on day one:
- Browsers: turn on data saver in Chrome or use a reader mode. Blocking autoplay video removes a surprising share of page weight.
- Email: switch off automatic image loading and set attachments to download on demand rather than with the message.
- Maps: download the port area offline before you need it, which is covered in offline maps for shore leave.
- Social apps: disable autoplay video in Instagram, TikTok and Facebook. Autoplay is the single greediest default on a phone.
- Podcasts and audiobooks: set them to download only on the schedule you choose, at the lowest quality that still sounds fine for speech.
What about a VPN?
A VPN will usually make a slow crew connection slower, and there are still two reasons to use one.
The overhead is real. Encryption adds bytes, and the extra round trip to a VPN server adds latency, which hurts most on a high latency satellite link. On a bad evening, a VPN can be the thing that stops a call connecting at all.
The two good reasons are these. First, some ships block or throttle specific services, and a VPN routes around that. Second, port WiFi in a terminal building or a seafarers' centre is genuinely worth protecting, because you have no idea who else is on that network. If you use one, pick a server geographically close to your position, use WireGuard rather than OpenVPN where the app offers it, and turn it off when you need every last kilobit for a call home. We compared what holds up onboard in the guides to VPNs for cruise ship crew and VPN setups that survive Starlink maritime.
Things that will not help, and cost money
Some purchases sound like fixes and are not, so save your money for the ones that are.
A WiFi extender that repeats the ship signal. A basic repeater halves throughput because it receives and retransmits on the same radio and channel. On a link that is already at 0.5 Mbps, that is a bad trade. A dedicated client bridge with separate radios is a different device and does work, but the cheap plug-in repeaters from the mall usually make things worse.
A better phone. Your phone's modem is not the bottleneck. A ten year old handset connects to a congested satellite link at exactly the same speed as a new flagship.
A "speed booster" app. These do nothing. Some inject ads and consume the data you are trying to save.
More expensive crew WiFi vouchers, in some cases. On many ships the voucher buys you data volume, not priority. Buying double the gigabytes at 21:00 gives you double the gigabytes at the same crawling speed. Read what the package actually promises before you top up.
The honest limits of all this
None of this creates bandwidth, and you should know exactly what these fixes can and cannot do.
If your ship gives the crew 2 Mbps shared between thirty people at peak hour, careful settings will get you working text messaging, voice calls that mostly hold, email with small attachments, and downloads that finish overnight. They will not get you a stable video call at 21:00, a live football match, a large software update during dinner hour, or cloud gaming. The gap between those two lists is the physics of the link, and no amount of configuration crosses it.
The three real cons of managing a slow link this way are worth stating plainly. First, it takes discipline. You are living on a schedule set by other people's sleep patterns, and being awake at 05:00 to send photos gets old. Second, turning off background sync means you have to remember to sync manually, and people lose photos this way when a phone goes over the side. Third, on some ships the restrictions are administrative, and no setting on your phone overrides a firewall the company configured ashore.
If your ship's link is genuinely broken rather than merely busy, say so through the right channel. Persistent packet loss, a terminal that drops out every time the ship turns onto a certain heading, or an access point that has been dead for a month are maintenance items, and they get fixed faster when the ETO has a written record rather than corridor complaints.
Who should not bother with all this
If you are on a modern ship with a well provisioned Starlink installation and light crew usage, most of this is unnecessary. Turn off photo auto backup, and get on with your life. Our honest look at Starlink maritime for crew covers what that setup actually feels like day to day.
If you are only onboard for a two week trip, do not spend money on a router you will use twice. Buy an eSIM for the port calls and accept that the sea days will be quiet.
And if your ship still runs a low bandwidth VSAT with a strict per person allowance, be honest with yourself about video calls. Plan around voice, write longer messages, and put your energy into the port call instead. There is more on that trade-off in what to expect from internet on bulk carriers.
FAQ
Why is crew WiFi slower at night than in the morning?
Because bandwidth is shared and almost everyone is online in the evening. The satellite link delivers the same capacity all day, so when thirty people use it at 21:00 instead of three people at 05:00, each person gets a fraction of what was available earlier. This is the reason a download that fails at night completes in minutes before breakfast.
Will a portable router make my crew WiFi faster?
It will fix weak signal in your cabin, and it will not increase the ship's bandwidth. If the crew mess is fast and your cabin is dead, a router positioned in a better spot recovers signal that the bulkheads were blocking. If the whole ship is slow at the same time, a router changes nothing, because the bottleneck is the satellite link rather than the WiFi.
Does a VPN slow down ship internet?
Yes, usually. Encryption adds overhead and the detour through a VPN server adds latency, which is already high over satellite. Use one when the ship blocks a service you need or when you are on untrusted port WiFi, and switch it off when you want maximum speed for a call home.
How much data does a video call to family actually use?
A standard video call uses roughly 0.5 to 1.5 Mbps in each direction, depending on the app and resolution, while a voice only call uses around 0.05 Mbps. That is a difference of ten to thirty times. On a congested crew network, voice calls connect and stay up in conditions where video will not start at all.
What is the first thing I should change on my phone?
Mark the ship network as metered on Android or enable Low Data Mode on iOS for that network, then set WhatsApp media auto-download to nothing on WiFi. Those two changes stop most unrequested downloads. Photo backup over WiFi is the next one to switch off, because a single 4K video can consume a meaningful share of the ship's daily traffic.
Is it worth buying a bigger crew data package?
It depends on what the package sells. On ships where the voucher buys volume rather than speed, a bigger package gives you more gigabytes at the same slow rate during peak hours. Check the wording before you top up, and if the package does include a priority tier, that is the one worth paying for.
Verdict
Treat the link as a shared resource with a timetable, and it becomes usable. The order that works is this: kill background sync first because it is free and immediate, then shift your heavy usage into the 04:00 to 06:00 window, then fix cabin coverage only if a speed test proves coverage is the actual problem. Save your money for an eSIM at the next port instead of a repeater.
About the author
I am a working marine engineer and I have spent years living on the other side of these connections, on bulkers and container ships with everything from a 512 kbps VSAT to a current Starlink installation. Everything here is what I do on my own phone in my own cabin. I have no relationship with any of the products mentioned, and where something does not work I say so, which is the only reason this site is worth reading. If crew WiFi is slow on your ship, start with the settings you control and the clock, because that is where the honest gains are.