VPN and video calls: troubleshoot lag and poor quality

Why a VPN can affect a video call

A video meeting uses more than one kind of network traffic. Signaling helps participants start and manage the call; media traffic carries audio, video, and screen sharing. Real-time media is sensitive to delay, jitter, and packet loss, not just download speed. That is why a file might download normally while a call freezes or voices sound choppy.

A VPN adds another network leg: traffic travels through a VPN server before reaching the meeting service. Depending on the network, server, app, and route, that extra path can add latency or encounter restrictions. But a VPN is only one possible cause. Video services may use connectivity checks and relays to establish a working path through different kinds of networks. WebRTC, for example, uses ICE and STUN/TURN mechanisms to help find a connection between participants. Microsoft notes that routing Teams media through a VPN can affect call quality.

Start with the symptom rather than assuming the VPN is at fault. Can’t join the meeting? Can the other person hear you? Is your audio breaking up, your video freezing, or the entire call dropping? These symptoms have different possible causes, including a muted microphone, a busy Wi-Fi network, a blocked media path, or an app problem.

A quick check: separate network, app, and device issues

Before changing VPN settings, make a short checklist:

Confirm that your device is online and that you joined using the intended app or browser.
Check the selected microphone, camera, and speakers. If you use a headset, try the built-in devices or another headset as a comparison.
Close apps and browser tabs that are using the network or camera. If others share your Wi-Fi, ask them to pause large downloads briefly.
If possible, compare Wi-Fi with mobile data or connect a computer to Ethernet. Change only one condition at a time so you can tell what made a difference.
Repeat the call with the same app and, if practical, the same participant.

If only one app has trouble, update it or your browser and check the meeting’s own device settings. If several apps have trouble on the same network, look at the network or VPN path. If the network is otherwise fine but the camera or microphone fails, start with device selection and permissions.

How to test whether the VPN is involved

For a controlled comparison, temporarily disconnect the VPN and make a short test call under similar conditions: use the same network, room, app, and—if possible—the same person. Compare specific symptoms, such as interruptions, delay, or call drops, rather than relying on a vague impression of speed.

If the call is noticeably more stable without the VPN, that suggests the route may be involved, but it does not prove the VPN is the only cause. Wi-Fi congestion, mobile signal, the meeting service, the app, and time of day can all affect results. If call quality is unchanged, reconnect the VPN as you normally would and continue checking the network and device. A quick test does not require changing your permanent settings.

You can also compare your public IP, DNS behavior, and connectivity before and after connecting. The VPN connection-check guide explains how to check those basics and distinguish a routing question from a camera or microphone problem.

Symptoms and what to check

The other person can’t hear you

Check whether you are muted in the meeting and whether the app selected the correct input device. Another program may already be using the microphone. On iPhone, apps need permission to use the microphone and camera; review access under Settings → Privacy & Security. On a computer, check the operating system’s privacy settings as well as the browser permission for the meeting site.

If the app shows microphone activity but no one can hear you, check the headset and selected audio output. Reconnect a Bluetooth device or test the built-in microphone. A microphone issue by itself is not evidence that the VPN is malfunctioning.

Video freezes, looks blurry, or falls behind

Reduce the load for a minute: turn off your camera, close unnecessary tabs and apps, and see whether the audio becomes steadier. If audio improves when video is off, the device or connection may be short of resources or available bandwidth in those conditions. That does not automatically mean you need a faster VPN server; network congestion and latency matter too.

On Wi-Fi, move closer to the access point or test another network. If practical, compare with a wired connection. Google Meet’s official troubleshooting guidance also recommends checking network stability when video quality is poor.

The call won’t connect or keeps dropping

Try opening the meeting in another supported browser or the app, and note any message about a firewall or timeout. Some home, school, or corporate networks restrict the protocols or ports that a meeting needs. WebRTC connections can use ICE and STUN/TURN; the exact path depends on the service and network conditions. Don’t open random ports or change firewall rules on your own. Ask the network administrator to review the service’s requirements.

Low-risk fixes to try

Make one change at a time, and undo it if things get worse:

Restart the meeting app or browser. Restart the device if the issue persists.
Install available updates for the app, browser, and operating system.
Test another Wi-Fi or mobile network. If the call works on one network but not another, tell the administrator of the problem network.
If your VPN app offers multiple servers, compare another available option and test the actual call. Don’t choose a server based on distance alone.
If your VPN is managed by your employer or school, don’t change its routes, DNS, or split-tunnel rules yourself. Ask the administrator to check how the service’s media traffic is routed.
If your VPN supports split tunneling, read what the feature changes before adding an exception. The split-tunneling guide explains the trade-offs and how to test a rule safely.

Split tunneling can send selected traffic directly to the internet while other traffic continues through the VPN. That changes the network path and the protection applied by the VPN, so don’t create exclusions at random. Follow your organization’s policy on managed devices. An administrator can check the meeting service’s requirements and choose an appropriate route.

Why you shouldn’t disable security features as a first step

A meeting service may encrypt its media at the app level, while a VPN provides a separate protected route between your device and the VPN server. These are different layers; one does not automatically make the other pointless. At the same time, a VPN cannot guarantee that an app will work without errors or that call quality will never change.

Don’t disable a firewall, leak protection, or a block on connections outside the VPN just to get through one call if you’re unsure what that setting does. On Android, the Always-on VPN and lockdown guide explains the relevant controls. If a strict block prevents a call while the tunnel is unavailable, that may be the expected result of the protection setting—not a reason to switch it off without understanding the consequences.

When to contact support

If the problem keeps coming back, give your VPN provider or network administrator useful details:

the meeting app and device you use;
whether you were on home Wi-Fi, a work network, or mobile data;
whether the VPN was connected and when the problem started;
what changed in the comparison test with the VPN disconnected;
the exact error message and approximate time of the issue.

Don’t post meeting invitations, passwords, connection profiles, or unredacted diagnostic logs in a public forum. Logs may contain personal information. For a work device, the administrator may need to check media-service access, routing, and network restrictions. For a personal device, first find out whether the issue also occurs on another network.

A short checklist before your next meeting

Check permissions and selected devices. Try another network. Then compare one call with the VPN connected and disconnected, changing only one factor at a time. If disconnecting the VPN helps, share that result with support and ask about an approved route for the meeting app rather than making random configuration changes. If it doesn’t help, investigate Wi-Fi, the device, and the meeting app.

This process helps narrow down the cause without promising perfect call quality or turning off protection unnecessarily. A VPN is only one part of the route; the call depends on the full connection and on both participants’ devices.

VPN and video calls: fix lag, dropouts, and audio issues