Overview
Poor meeting quality can come from network instability, camera or microphone selection, Bluetooth issues, background processing, weak Wi-Fi, or browser/application problems.
Why this happens
Video meetings combine real-time network traffic with local camera, microphone, graphics, and CPU use. A problem in any one layer can reduce quality.
Before you begin
- Identify the meeting platform.
- Record whether audio, video, or both are affected.
- Note whether the issue occurs in every meeting.
- Do not install unapproved camera or audio utilities.
Click-by-click troubleshooting
Step 1: Confirm selected camera and audio devices
Action: Open the meeting application's Settings > Devices or Audio/Video section and verify microphone, speaker, and camera selections.
Why this matters: Applications can switch to disconnected docks, headsets, or virtual devices.
What to look for: Look for unexpected devices or missing input levels.
Expected result: The meeting app should use the intended working hardware.
Step 2: Test camera and microphone locally
Action: Use the application's test-call or device-preview feature if available.
Why this matters: This separates hardware problems from meeting-network problems.
What to look for: Check video clarity, microphone level, and speaker output.
Expected result: Local preview and test audio should work normally.
Step 3: Check the network connection
Action: Open Settings > Network & internet and confirm the intended Wi-Fi or Ethernet connection. Test two public websites.
Why this matters: Unstable connectivity affects real-time media before ordinary browsing may appear broken.
What to look for: Look for weak Wi-Fi, reconnects, or slow page loading.
Expected result: The device should have a stable network path.
Step 4: Close unnecessary heavy applications
Action: Save work and close nonessential applications that are using high CPU, memory, disk, or network bandwidth.
Why this matters: Resource contention can degrade encoding, decoding, and audio processing.
What to look for: Check Task Manager for high resource usage.
Expected result: Meeting quality should improve if local resource pressure was contributing.
Step 5: Compare browser and desktop application if supported
Action: If the meeting platform supports both, test the same account using the alternate approved client.
Why this matters: This separates a browser/app problem from the network and account.
What to look for: Note whether audio/video quality changes between clients.
Expected result: A large difference points toward the original client environment.
Step 6: Test another trusted network
Action: If allowed, test on a trusted wired connection or mobile hotspot.
Why this matters: This isolates the original Wi-Fi or ISP from the device and meeting platform.
What to look for: Compare audio breakup, freezes, and disconnects.
Expected result: Better quality elsewhere indicates a local network-path problem.
What to look for
- Local preview bad: device or hardware issue.
- Alternate client works: app/browser issue.
- Alternate network works: Wi-Fi or ISP issue.
- Many users affected: provider or office-network issue.
When to stop
When to contact IT
Contact J3 Systems Group if poor quality occurs across multiple meeting platforms or networks, devices disappear, drivers show errors, or many users are affected. Include article code KB-15.005 and which tests improved or did not improve quality.
Need help with this issue?
J3 Systems Group supports small businesses and nonprofits with Microsoft 365, Google Workspace, cybersecurity, devices, documentation, and day-to-day IT operations.
Contact J3 Systems GroupAuthoritative references
Vendor interfaces, licensing, and security guidance can change. Verify current platform behavior against the primary documentation below before making high-impact production changes.