System requirements
Use this checklist before installing Connect or preparing a managed rollout.
Quick compatibility check
Review these baseline requirements first to confirm that the computer, network, and audio devices are ready for Connect. Complete each prerequisite in order and confirm that the operating system recognizes every required Connect component. Restart only when requested, then reopen the app and verify permissions before changing audio routing.
| Component | Minimum | Recommended |
|---|---|---|
| Processor | 64-bit dual-core processor | Recent quad-core processor or Apple Silicon |
| Memory | 4 GB RAM | 8 GB RAM or more |
| Storage | 500 MB free | 1 GB free for updates and logs |
| Network | 10 Mb/s stable connection | 25 Mb/s+, low jitter, wired or strong Wi-Fi |
| Audio | Working microphone and speakers | Wired USB headset with boom mic |
| Load | Enough capacity to run Connect and the calling app | Close heavy background audio, video, or CPU tasks |
Supported operating systems
Connect is available on the platforms listed below when the device also meets the corresponding hardware and permission requirements. Keep the installer version and device status available if the same step fails again. This separates an incomplete installation from a configuration problem. Complete each prerequisite in order and confirm that the operating system recognizes every required Connect component.
| Platform | Supported versions | Audio component |
|---|---|---|
| Windows | Windows 10 64-bit, build 1903 or later; Windows 11 | Connect virtual audio devices powered by VB-Cable |
| macOS | macOS 12 Monterey or later; Intel or Apple Silicon | Connect routing through BlackHole |
| Linux | Ubuntu 20.04+, Debian 11+, Fedora 36+; x86_64 | ALSA or PipeWire; libasound2 and libgtk-3 |
| Browser option | A current Chrome release when using the Connect extension | Browser microphone permission |
Required permissions
Grant each permission below so Connect can capture, process, and route audio correctly. Complete each prerequisite in order and confirm that the operating system recognizes every required Connect component. Restart only when requested, then reopen the app and verify permissions before changing audio routing. Keep the installer version and device status available if the same step fails again.
- Microphone access for Connect and the calling app.
- Audio-device installation during desktop setup.
- Local audio-device discovery so Connect can list physical inputs and outputs.
- Outbound secure web access for authentication, translation, updates, and account usage.
If a permission is blocked by policy, ask your administrator to approve Connect before reinstalling repeatedly.
Network quality
Bandwidth alone does not guarantee a clear translated call. Packet loss, unstable Wi-Fi, high latency, and a busy VPN can interrupt streaming audio even when a speed test looks fast. Note the device load, connection type, and calling application whenever the delay changes noticeably. Those details make the result easier to reproduce and resolve.
Verify your setup
Complete this short validation after installation to confirm that the app, virtual devices, and network are ready. Use the guidance here to make one deliberate change at a time and preserve a clear baseline. Confirm the result in a controlled test before moving to the next decision or configuration step.
- Open Connect and confirm your physical microphone and speaker appear.
- Use How I Sound? to hear a translated preview.
- Open your calling app and select Connect Mic and Connect Speaker.
- Place a short internal test call before the first customer or candidate conversation.
Frequently asked questions
These answers clarify the difference between meeting a listed minimum and having a dependable production setup. Hardware, permissions, network stability, security software, and the calling application must work together on the same computer image. Test the exact VPN, headset, drivers, and policies used by the team before a wider deployment.
Can Connect run on a 32-bit operating system?
The desktop requirements on this page are for supported 64-bit Windows and Linux systems, plus supported Intel or Apple Silicon Macs. Use the installer that matches the operating system and architecture rather than forcing an incompatible package.
Is a fast speed-test result enough for clear calls?
No. Real-time audio also depends on low packet loss, stable latency, low jitter, and consistent upload performance. Test a real Connect call on the same Wi-Fi, Ethernet, VPN, and office network that users will use.
Can security software or a managed-device policy block Connect?
Yes. Microphone privacy controls, application allowlists, audio-driver installation policies, VPN inspection, and endpoint security can affect setup. Validate Connect on the organization’s managed desktop image and ask an administrator to approve blocked permissions before reinstalling repeatedly.
How do I confirm that a computer is practically ready?
Open Connect, confirm the physical microphone and speaker, run How I Sound?, select Connect Mic and Connect Speaker in the calling app, and complete a short internal call. Passing only the hardware table does not verify the full audio path.
Support
Need help? Get in touch with our Support Team for assistance. Include the calling application, operating system, selected microphone and speaker, translation direction, and the exact step that failed. A short description of the expected result and what happened instead helps the team respond more quickly.