Frequently Asked Questions

OpenedMic is a browser-based live audio and video broadcasting service. A broadcaster opens a room in a supported browser and presses MIC ON. Listeners join by scanning a QR code or opening a link in their browser. No app or account is required on either side. See How It Works for a full walkthrough.

If a room's QR image does not appear, use the join link or enter the 6-character room code at openedmic.com/app in a supported browser. Both options use the same room entry path while the room is active.

Yes. No registration is required and no payment is needed to open a room or join as a listener.

No. Neither the broadcaster nor listeners create an account. You enter a name when opening or joining a room - that name is used only within the session and is not stored after the session ends.

Open openedmic.com/app in a supported browser. Enter your name, choose a broadcast mode, and press MIC ON. The room displays a QR code and join link for listeners.

No. Listeners scan a QR code or open the join link in a supported browser. No app download, account, or sign-up is required. See how QR joining works.

Three ways: scan the broadcaster's QR code, tap the join link if it was shared by message, or enter the 6-character room code manually at openedmic.com/app.

Up to 200 listeners can join a single room simultaneously.

Yes, if the broadcaster enables it. Group chat is off by default. Listeners can also send emoji reactions at any time. The broadcaster sees reactions and can toggle chat on or off during the session.

Yes. Each listener controls playback volume on their own device using the available system and browser controls.

Yes. One listener at a time can request the Approved Guest Mic, and the broadcaster decides whether to approve. After approval, microphone permission, and connection, the guest audio is mixed into the live broadcast. This is controlled participation, not an open conference call.

Only the broadcaster can approve, deny, or end an Approved Guest Mic. Listener requests appear as a prompt on the broadcaster's screen with the listener's display name and avatar. The broadcaster taps Approve or Deny.

Yes. While a guest is live, the broadcaster has a guest volume slider, a mute toggle, and an End Guest button. The configured ducker lowers the guest level while the broadcaster speaks, then restores it.

No. The guest is just a listener who tapped Ask to speak. No account, no install, no registration. The microphone is captured in the listener's browser using WebRTC after the listener grants browser permission.

Yes. After the broadcaster approves, the listener's browser will request microphone permission. If the listener denies the prompt, the guest mic ends cleanly and the room continues normally. On mobile devices the page must be served over HTTPS for the browser to allow microphone access - when joining via the QR code or link from a real device, this is already the case.

No. OpenedMic does not store guest audio on its servers. The server handles signaling and room state but does not record or transcribe live media. Operational analytics use restricted fields such as mode and status; they do not contain names, room IDs, audio data, or persistent device identifiers.

The Approved Guest Mic is a controlled way for one listener to speak in an otherwise broadcast-first room. Listeners are muted by default. A listener can request to speak; the broadcaster approves a single guest at a time; the guest's microphone audio is mixed into the live broadcast; and the broadcaster can revoke or end the guest mic at any moment. It is audio-only.

No. Only one approved guest can speak at a time. OpenedMic is broadcast-first: the broadcaster leads, and at most one listener is granted the Approved Guest Mic at any moment. It is not a multi-speaker meeting or conference call.

No. The Approved Guest Mic is audio-only. An approved guest speaks through their microphone; there is no guest camera, no guest video, and no guest screen sharing. (Broadcaster-side screen share and presenter camera, where the broadcaster's device and browser support them, are separate broadcaster tools and are not part of the guest path.)

No. OpenedMic is a broadcast-first live audio room with one host and many listeners. Listeners stay muted by default. Participation is limited to one host-approved, audio-only guest at a time.

OpenedMic supports compatible iPhones whose current Safari version provides the required WebRTC and media features. Screen sharing is not offered on iOS in the current application. Test the intended device and network before a live session.

OpenedMic supports compatible Android devices whose current browser provides the required WebRTC and media features. Screen-sharing availability varies by browser and device, so check the control on the intended setup.

OpenedMic requires current WebRTC, Web Audio, and media-permission support. Compatibility varies by browser, operating system, and device policy. No OpenedMic extension, plugin, or driver is required.

No special microphone is required. OpenedMic uses a microphone made available by the supported browser, including a built-in input or compatible external input. Each broadcast mode selects a documented processing preset. Results still vary with the device, environment, and network.

Yes. When creating a room, the broadcaster can set it to private and optionally add a password. Listeners who have the code or link are prompted to enter the password before joining. The password is held in server memory only for the session duration and is not stored.

OpenedMic does not store the live media on its servers. WebRTC uses a direct path when available or an encrypted TURN relay when required. If you use local recording, the WebM file is saved only to the broadcaster's device. See the Privacy Policy for details.

A room exists only while an active broadcast session is running. When the broadcaster ends the session or disconnects without reconnecting within 15 seconds, the room is destroyed and all listeners are disconnected. Rooms do not persist across sessions.

Supported browsers may offer home-screen installation. Use the in-app Install control when the browser makes it available, or use the browser's own Add to Home Screen action. No app-store package is involved.

Yes. Broadcasters have a local recording control in the broadcast panel. The recording is saved directly to your device as a WebM file when you stop the recording. Nothing is uploaded to any server.