A handful of browser settings make a real difference for video chat performance. None of these are Chatzyo-specific tweaks — they're general WebRTC best practices that help on any video platform, this one included.
Most browsers have a setting, usually under Settings → System, called something like "Use hardware acceleration when available." With it off, your CPU handles all the video decoding work, which can cause lag, dropped frames, or your device running hot during a longer call. Turning it on shifts that work to your graphics hardware, which is built for exactly this kind of job and handles it far more efficiently.
Some ad blockers and privacy-focused browser extensions include a setting that restricts how much connection information WebRTC sites can use — sometimes labeled something like "WebRTC IP handling." This exists for good privacy reasons in general, but it can also prevent a video call from connecting properly, since establishing a direct connection between two people requires exchanging some of that information. If a call won't connect and you're running one of these extensions, adding chatzyo.in to its allow list, or briefly disabling it to test, is a reasonable first thing to check.
A VPN is a legitimate tool worth using if IP visibility concerns you — see our guide on that — so this isn't a recommendation to stop using one. That said, some VPN configurations can interfere with how WebRTC establishes a connection. If you're having trouble connecting and you use a VPN, temporarily turning it off is a useful diagnostic step to isolate whether that's the cause, not a permanent suggestion against using one.
A cluttered cache can occasionally slow down how quickly your browser connects to a new site. Clearing it now and then is reasonable general maintenance — just be aware that clearing "Site Settings" specifically (rather than just cache) will also reset your camera and microphone permissions, so you'll be prompted to allow access again next time.
Video chat needs a reasonably stable connection more than it needs a specific number attached to it. A consistent Wi-Fi or wired connection generally performs better than a weak or congested mobile signal, and closing other things using bandwidth — a large download running in the background, for instance — helps more than chasing a particular speed figure. If video quality drops noticeably, checking what else is using your connection is usually more useful than assuming the number itself is the problem.
Desktop browsers tend to have more consistent performance for video calls, mainly because desktop hardware and network connections are typically more stable than mobile ones. That doesn't mean mobile doesn't work well — it does — just that if you're troubleshooting a specific performance issue, switching to desktop briefly is a reasonable way to check whether the device itself is part of the problem.
WebRTC is an evolving standard, and browser vendors regularly ship improvements to how it's implemented — better codec support, more efficient encoding, fixes for specific connection issues. An outdated browser version occasionally misses out on these improvements, and in rare cases, an older version might have a known WebRTC bug that's already been fixed in a newer release. Checking that you're on a reasonably current version is a low-effort thing to rule out if something feels off.
Chrome and Edge generally have the most mature WebRTC support, though current versions of Firefox and Safari work well too.
Yes. It shifts video decoding work from your CPU to your graphics hardware, which reduces lag and overheating during calls.
Yes. Ad blockers and privacy extensions sometimes restrict WebRTC connection details, which can prevent a call from connecting properly.