> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tuple.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Joining a call from your browser (alpha)

<Warning>
  The Tuple web client is in **alpha**. It's off by default and available to a small number of teams. [Reach out to support](mailto:support@tuple.app?subject=Web%20client%20alpha) to have it turned on. Behavior described here may change as we iterate on feedback.
</Warning>

The web client lets someone open a [call link](/pairing-with-tuple/joining-a-call-via-a-linkurl) and join the call from a browser tab. It allows other folks on your team to join calls without having to install Tuple. It also works on mobile, so you can be a part of the conversation when you're not at your desk.

The web client is intentionally limited, and is not a replacement for the desktop app. **Sharing your screen and drawing on someone else's still require [the Tuple app](https://tuple.app/download?utm_source=docs)**.

## What works in the browser

* **Audio**: you can hear others, and be heard
* **Webcams**: you can see other people, and they can see you
* **Viewing a shared screen**: if someone on desktop is sharing, you'll be able to see it. You'll also see other peoples' cursors and annotations

## Joining from a browser

Open any call link (a personal room link, a regular room link, or a generated call link). They all look like `https://tuple.app/c/...`.

On a computer, opening the link attempts to open the Tuple app first. Below that prompt, a **Join from your browser** button takes you into the call.

On a phone or tablet, **Join from your browser** is the primary button, since there's no Tuple app to open.

### Waiting to be let in

What happens next depends on the room's [door](/pairing-with-tuple/using-rooms#open-vs-closed-door-control):

* If the room is open, you go straight in.
* If the room is closed and the owner isn't in the call yet, you'll see **Waiting for \[name]**, and you'll join automatically the moment they start the call.
* If people are already in the call, they get a **Join request** notification and you're admitted when someone accepts.

## In the call

Everyone on the call gets a tile. Tiles show a webcam if there is one and initials if there isn't, plus status badges:

The control bar contains three things:

* **Microphone**: toggles your mic, which comes up automatically when you join. The chevron opens a menu to pick your **Input** (with a live level meter) and **Output** device.
* **Camera**: toggles your webcam, off by default. The chevron picks which camera.
* **Leave call**.

### Watching a shared screen

When someone shares their screen, it takes over the stage in your tab and the participant tiles move aside. You can:

* **Zoom** with a scroll wheel, or by pinching on a touchscreen.
* **See other viewers' cursors**, labeled with their names, along with anything they draw or type on the screen.

Only one screen is on stage at a time; if a second person starts sharing, theirs replaces it for everyone.

You can't share your own screen or annotate someone else's from the browser.

## Leaving

**Leave call** drops you out and releases your camera and microphone. You land on a **Call ended** page with a **Join call again** button, so it's easy to rejoin if you refresh the page. You can also rate the call quality there.

## Multiple tabs

The call lives in one tab. Open the same call link in a second tab and the first tab should show that the call is open in another tab. There's also an option to bring the call back into the original tab.

Closing the tab that houses the call allows the other tab to reclaim it.

## Supported browsers

Use a current version of **Chrome**, **Edge**, **Safari**, or **Firefox**, on macOS, Windows, Linux, iOS, or Android.

Browser calls run on the same call engine as the desktop app, with the same end-to-end encryption.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Your browser blocked the microphone or camera">
    The browser, not Tuple, holds that permission. Allow access from the icon in the address bar, then click the **Microphone** or **Camera** button again. The notice clears itself once access is granted.
  </Accordion>

  <Accordion title="Your microphone or camera is in use elsewhere">
    Another app has the device open. Close it, then click the button again.
  </Accordion>

  <Accordion title="No microphone or camera found">
    Connect one and click the button again — the browser picks it up without a reload.
  </Accordion>

  <Accordion title="Connection lost, or Reconnecting…">
    The tab lost either its connection to Tuple or its connection to the other participants. It rejoins on its own when the network comes back. If it doesn't, use **Rejoin call**.
  </Accordion>

  <Accordion title="This call is full">
    Browser participants count toward the call's [participant limit](/pairing-with-tuple/joining-a-call-via-a-linkurl) like anyone else. Try again once someone leaves.
  </Accordion>

  <Accordion title="You're already on this call">
    The same account is in the call on another device. Leave it there, or use **Move the call here**.
  </Accordion>
</AccordionGroup>

The web client is new, and we want to hear what breaks and what's missing. [Tell us](mailto:support@tuple.app?subject=Web%20client%20feedback) what you think!