Devices
Random Video Chat on Linux in Firefox or Chrome
Random video chat on Linux works in the browser you probably already use. Open omlet.site in Firefox, Chrome or Chromium, allow the camera and microphone, confirm you're 18 or older and press Start. Omlet is built on WebRTC, the same browser standard on every platform, so there's nothing Linux-specific to install.
Where Linux differs is the layer underneath: device access, audio servers and sandboxed browser packages. Here's how to check each one quickly.
Linux browsers that handle video chat
| Browser | Camera and mic | Install Omlet as an app | Notes |
|---|---|---|---|
| Firefox | Yes | Not in the usual way; pin the tab or bookmark it | Often preinstalled, sometimes as a Snap or Flatpak |
| Google Chrome | Yes | Yes, from the address bar or menu | Usually installed from Google's own package |
| Chromium | Yes | Yes, from the address bar or menu | Often packaged as a Snap or Flatpak |
Keep your browser current through your distribution's package manager or software center. Browser-specific settings are covered on our Firefox page and Chrome page.
Check that Linux sees your webcam
Before blaming the browser, confirm the system detects the camera. In a terminal:
- Run ls /dev/video* and look for at least one device, such as /dev/video0. Many webcams create two entries; that's normal.
- Run v4l2-ctl --list-devices (from the v4l-utils package) to see each camera by name.
- Open your desktop's camera app, such as GNOME's Camera or Cheese, to see a live picture.
- On some distributions your user must be in the video group. Check with the groups command; if needed, run sudo usermod -aG video $USER, then log out and back in.
If nothing shows up, try another USB port and test the camera on another computer. Webcam not working in the browser on Linux goes further, including driver and permission checks.
Pick the right mic with PipeWire or PulseAudio
Many current desktop distributions use PipeWire for audio, usually with a PulseAudio-compatible layer; older setups run PulseAudio directly. Either way, the browser normally takes the system's default input unless you choose another.
- Open your desktop's Sound settings, choose your headset or USB mic as the input, and speak to watch the level meter move.
- Make sure the input isn't muted and its volume isn't near zero.
- For finer control, install pavucontrol (PulseAudio Volume Control), which works with both. While Omlet is using the mic, its Recording tab shows the browser and lets you switch it to another input.
- From a terminal, wpctl status (PipeWire) or pactl list short sources lists the inputs the system can see.
Still silent? See microphone not working in the browser.
Flatpak and Snap browsers need camera permission
Sandboxed browser packages can only reach the devices their sandbox allows. Package defaults change over time, so check rather than assume.
- Flatpak: use Flatseal, or run flatpak info --show-permissions followed by the browser's app ID, to confirm it has device access. Adjust it in Flatseal or with flatpak override if it's missing.
- Snap: run snap connections firefox (or chromium) and check that the camera and audio-record interfaces are connected. If not, connect them with sudo snap connect firefox:camera and sudo snap connect firefox:audio-record.
- PipeWire camera portal: some newer browser versions can reach cameras through PipeWire and your desktop's portal instead of /dev/video directly. If your desktop shows a system prompt asking to allow camera access, approve it. Behavior varies by browser, version and desktop.
Quick test: if the camera works in your desktop's camera app but not in a Snap or Flatpak browser, it's almost always a sandbox permission, not a driver problem.
Allow camera access in the browser
Once Linux sees the devices, the browser still asks before letting a site use them.
- Firefox: the prompt lets you choose the camera and microphone from dropdowns. Tick Remember this decision to skip the prompt next time, then click Allow.
- Chrome and Chromium: click Allow. To switch devices later, open chrome://settings/content/camera and pick from the dropdown at the top, then do the same for the microphone.
- Blocked by mistake? Click the permission icon in the address bar, reset the permission and reload the page.
Webcam chat on Linux from your app menu
Chrome and Chromium can install Omlet as a web app: click the install icon in the address bar or use the menu's install option. It then appears in your application menu and opens in its own window. Firefox doesn't install web apps that way, so pin the tab or bookmark it.
The keyboard shortcuts are the same on every system: → starts a chat or skips to the next person, and Esc stops.
Firewalls, VPNs and how the call connects
Omlet's calls are encrypted and peer to peer: your browser tries to connect directly to your partner's, and when that isn't possible the call is relayed through Omlet's network provider. Direct connections usually use UDP. Most desktop firewalls allow outgoing traffic by default, but strict rules, some workplace networks and some VPNs can block or slow calls.
Because direct calls are peer to peer, the connection can share your IP address with the person you're talking to. A VPN hides it, at the cost of some extra lag. The plain-English guide to WebRTC explains how the pieces fit together.