Common questions.

When you enter your email and tap Send sign-in email, Prayer Audio Controller sends a message to your inbox. It contains two things:

• A magic link — click it and you are signed in automatically in a new tab.
• A 6-digit code — type it directly into the code field in the extension popup if the link is inconvenient.

Both the link and the code expire after 10 minutes. If yours has expired, go back to the email step and request a new one.

Check your spam or junk folder first. The message comes from Prayer Audio Controller via Resend.

If it is not there, wait 30–60 seconds and try sending again. If you have already sent once recently, the popup will skip the re-send and take you straight to the code entry screen — this is expected, because sending too many codes too quickly is blocked by the email provider. Just use the code from the first email.

If no email arrives after a second attempt, email [email protected] with the address you are trying to use.

This happens when you tap Send sign-in email too many times in a short window. The popup will automatically move you to the code entry screen and show a message saying a code was already sent.

Use the code from the most recent email. If the code has expired, wait a few minutes before requesting a new one.

Yes. Prayer Audio Controller works on any Chromium-based browser that supports Manifest V3 extensions: Chrome, Brave, Edge, Arc, and Opera.

The minimum requirement is Chrome 114 or equivalent. Most users on Brave, Edge, Arc, and Opera are on recent enough versions for this to work out of the box.

Firefox and Safari are not supported — they use a different extension platform.

No. Chrome on iOS and Android does not support extensions. Prayer Audio Controller is a desktop browser extension only.

A dedicated mobile app is in development. When it ships, your account will cover it at no extra cost.

Spotify Web Player (open.spotify.com in a browser tab) — yes. Any audio playing in a Chrome tab is muted.

Spotify desktop app — no. The Spotify app runs outside the browser, so the extension cannot reach it.

Chrome extensions can only control audio playing inside Chrome tabs. The Spotify desktop app is a separate process — it runs at the operating system level, outside the browser, so the extension has no way to reach it.

This is a platform limitation, not something we can work around from the extension. The same applies to Apple Music desktop, iTunes, VLC, system sounds, and any other app that runs outside the browser.

Anything playing audio in a browser tab is muted:

• YouTube and YouTube Music
• Spotify Web Player (open.spotify.com)
• Apple Music Web (music.apple.com)
• SoundCloud, Mixcloud
• Twitch, Mixlr, and other livestreams
• Web radio (TuneIn, Radio Garden, and similar)
• Any other tab that is currently playing audio

Tabs that were already muted before the prayer started stay muted — only actively playing tabs are affected.

Anything outside Chrome tabs is untouched:

• Spotify, Apple Music, iTunes — desktop apps
• System volume and OS audio mixer
• Phone calls, Zoom, FaceTime, Teams
• Alarms, ringtones, system notifications
• Other browsers (Firefox, Safari)
• Bluetooth speakers at the system level

Prayer times are calculated on-device using the adhan.js library. The result is a calculated astronomical time — different organisations use slightly different sun-angle values for Fajr and Isha, so calculated times can vary by a few minutes.

Two adjustments fix most mismatches:

• Change the calculation method. Use the method your country's official religious authority uses — Diyanet for Turkey, ISNA for North America, Egyptian for Egypt, and so on. You can change it in the popup under Calculation.
• Set a mute start offset. If your local mosque's call consistently comes 2–3 minutes before the calculated time, set the offset to 2–3 minutes early. This shifts every mute window forward without changing the schedule display.

Open the Prayer Audio Controller popup and click Change next to your current location. You can search for any city by name. The schedule recalculates immediately and a confirmation appears at the top of the popup.

If you travel, you can update your location at any time from the popup. The schedule refreshes on every Chrome start as well.

No. Prayer Audio Controller runs as a Chrome extension — Chrome must be open and running at prayer times for muting to fire. If Chrome is closed at a prayer time, that mute window is skipped.

For shops and cafes that keep a computer on during business hours, this works as expected. If Fajr falls before the shop opens, just leave the Fajr toggle off in the prayer chip settings.

Yes. Prayer times are calculated using your device's current time. If your system clock is off by more than a couple of minutes, the mute window will fire at the wrong time.

Prayer Audio Controller checks the server time when the popup opens. If it detects a drift of more than 2 minutes, a warning appears at the top of the popup:

To fix this: on macOS, go to System Settings → General → Date & Time and enable Set time and date automatically. On Windows, right-click the clock → Adjust date/time and enable automatic time sync.

Yes. When you confirm a new city or coordinates, the popup shows a confirmation banner — "Schedule updated for [City] · [Timezone]" — and the schedule recalculates immediately.

If you do not see the banner, tap Change next to the location name and pick the city again. The extension also recalculates each time Chrome starts.

Open the popup and find the Mute start row. Set an amount (0–10 minutes) and choose early or late.

• Set it early if your local mosque's call tends to come before the calculated time — for example, 2 min early means muting starts 2 minutes before the calculated prayer time.
• Set it late if the call consistently comes after.

The label below the controls updates to show the current effect: "Mute starts 2 min early."

In the popup, scroll down to the Mute for row. You'll see five chip buttons — one per prayer. Click any chip to toggle it off. Disabled prayers appear with a strikethrough and are greyed out.

Disabled prayers still appear in the schedule display — they just won't trigger a mute. This is useful if Fajr falls before your business opens, or if you want to skip a specific prayer for any reason.

The default is 6 minutes, which covers a typical adhan. You can change it to anything from 1 to 30 minutes in the Mute duration row of the popup.

A typical adhan lasts 3–5 minutes. Setting 6–8 minutes gives a small buffer in case of variation. If your setup tends to play a longer recitation after the adhan, increase the duration to match.

This is expected. The schedule always shows all five daily prayer times — the chips only control which ones trigger auto-mute. A greyed-out, struck-through chip means that prayer will not mute audio, but the time is still displayed so you can track the day's schedule.

To disable a prayer: open the popup, scroll to Mute for, and click the chip for that prayer. It will appear struck through and greyed out when off.

At the calculated time, Prayer Audio Controller:

• Mutes every Chrome tab that is currently playing audio
• Shows a small banner at the top of each muted tab with the prayer name, a countdown, and a "Restore now" button
• Shows a red MUTE badge on the extension icon in the toolbar
• Sends a system notification with a one-tap "Restore audio" button

After the configured duration, each tab is returned to exactly the state it was in before — tabs that were playing resume, tabs that were already muted stay muted. The banner is also removed automatically.

The red MUTE badge on the extension toolbar icon means a mute window is currently active. Audio in your browser tabs has been muted for the current prayer.

The badge is visible even if you have the popup closed. You can click the icon at any time to open the popup and see the countdown, prayer name, and the Restore audio now button.

The tooltip on the icon also shows the prayer name and the time the mute ends — for example: "Prayer Audio Controller — muted for Maghrib until 19:44".

Three ways:

• From the in-page banner: a banner appears at the top of each muted tab. Click Restore now to restore all muted tabs immediately. You can also dismiss the banner with the × button — this hides the banner but does not restore audio.
• From the notification: tap the "Restore audio" button in the system notification that appears when muting starts. The notification stays visible until you dismiss it or use it.
• From the popup: click the extension icon in the toolbar. While a mute is active, a Restore audio now button appears at the top of the popup. Click it to restore immediately.

No problem. Open the extension popup by clicking the icon in the toolbar. The Restore audio now button appears there while any mute is active — it is not limited to the notification.

If the popup shows the normal next-prayer view instead of the active mute state, the mute window has already ended and audio was automatically restored.

When Prayer Audio Controller mutes a tab, a small banner appears at the top of that page. It shows the prayer name, a live countdown to when audio will be restored, and two buttons:

• Restore now — immediately restores audio in all muted tabs, clears the badge, and cancels the remaining countdown. This is a full restore, the same as clicking "Restore audio now" in the popup.
• × (Dismiss) — hides the banner from that tab only. Audio stays muted. The countdown and auto-restore continue normally.

The banner removes itself automatically when the mute window ends and audio is restored.

The banner cannot appear on certain restricted page types — this is a platform limitation that applies to all Chrome extensions:

• Chrome's new tab page
• chrome:// system pages (settings, extensions, etc.)
• file:// local files opened in the browser
• Other extension pages

On these pages, the extension can still mute the tab — the red badge and system notification serve as the fallback indicators.

No. Dismissing the banner (the × button) only hides the banner from that tab. Audio stays muted and the auto-restore countdown continues normally.

To restore audio, use Restore now in the banner, the popup, or the system notification.

Chrome uses this phrase for any extension that can display content inside browser tabs. Prayer Audio Controller uses this access for one purpose: to show the mute banner inside tabs it silenced.

What the extension does not do with this permission:

• Read page content, article text, or media
• Read form fields, passwords, or messages
• Read or transmit browsing history
• Read cookies or session data
• Inject tracking scripts or analytics

The banner is injected into a Shadow DOM element — it is visually isolated from the page and does not interact with page content in any way.

Prayer times are calculated entirely on-device — no prayer-time API call is ever made. Your coordinates are never sent to Prayer Audio Controller servers.

The extension contacts our servers only to verify your account access (checking trial or subscription status). A one-time request to BigDataCloud may be made during setup to get a readable city name — this request includes only your coordinates and no account identity.

No tab URLs, page content, or browsing activity is ever sent anywhere.

Prayer Audio Controller requires an account to verify that your trial or paid plan is active. The extension checks your access status each time Chrome starts — if access is valid, it runs normally.

Sign-in uses a one-time email code (no password). Your email is used only for authentication and billing, never for advertising or tracking.

Full access to every feature — all five prayers, every calculation method, mute duration and offset controls, per-prayer toggles, and the restore button. No card is required to start.

After 7 days, you can choose an annual ($19/year) or lifetime ($35 one-time) plan to continue. Your city and settings are preserved if you upgrade.

Paid plans include a 14-day refund policy. If you're not satisfied within 14 days of payment, email [email protected] and we'll refund you in full — no questions asked.

The trial is free and requires no card, so there's nothing to refund during the trial period.

In Chrome's local storage on your device:

• Your city coordinates and display name
• Your settings (calculation method, mute duration, offset, enabled prayers)
• Your session token (used to verify access)

On our servers (Supabase):

• Your email address and account details
• Your subscription status

Prayer times are calculated locally — no prayer-time API calls are made. Your coordinates are never sent to our servers for scheduling. A one-time request to BigDataCloud may be made during setup to resolve a readable city name.

No browsing history, tab URLs, or page content is read. No analytics SDK is included.