If you've ever clicked a mailto: link and nothing happened, or your browser silently ignored a request from a website that wanted to handle calendar invites, messaging protocols, or custom app links, there's a good chance the culprit is a single browser permission called "Allow sites to ask to become default handlers for protocols." In this guide, I'll walk you through exactly what this setting does, why it gets turned off, and how to fix it step by step across every major browser on Windows, macOS, and Linux.

What Are Protocol Handlers and Why Do They Matter?

Before we dive into the fix, it helps to understand what's actually happening under the hood. A protocol handler is a registered application or web service that your operating system or browser calls when it encounters a specific URL scheme, the short prefix that comes before the colon in a link.

You interact with protocol handlers every single day, often without realizing it:

mailto:, opens your email client when you click an email address link
tel:, triggers your phone app or Skype when you tap a phone number
webcal:, imports a calendar subscription into your calendar app
sip:, connects a VoIP call
Custom schemes like slack://, zoom://, spotify://, and hundreds of others used by desktop applications

Web-based protocol handlers take this one step further. Instead of opening a desktop app, they let a website register itself as the handler. Gmail is the classic example, when you visit Gmail and it asks "Do you want Gmail to open all mailto: links?", that's a web protocol handler registration request. The same goes for web-based calendar apps, online messaging platforms, and productivity suites.

The browser permission we're focusing on, "Allow sites to ask to become default handlers for protocols", is the gatekeeper for all of this. When it's disabled, websites can never even ask to register themselves. The prompt never appears, and users have no way to set up web-based handlers through normal browsing.

Why This Setting Gets Disabled (And Why You're Here)

There are several common reasons you might find yourself needing to re-enable this permission:

1. Browser Reset or Fresh Installation

When you do a clean install or reset your browser to default settings, many content permissions revert to their factory state. Depending on the browser and version, the protocol handler permission may default to "Ask" or "Block." Chrome and Edge have historically shipped with this set to "Ask," but enterprise policy configurations sometimes override that to "Block."

2. Group Policy or MDM Enforcement

If you're on a work or school computer, your IT department may have pushed a Group Policy or Mobile Device Management (MDM) profile that disables this permission across the entire fleet. In this case, the setting in your browser UI may appear grayed out, and you'll need to talk to your admin rather than change it yourself.

3. Accidental User Action

It's surprisingly easy to accidentally click "Don't allow" on a permission prompt and then have the browser remember that choice permanently. Once you block a site's request, future prompts from that domain are silently suppressed.

4. Privacy Extensions or Hardened Browser Profiles

Privacy-focused browser extensions, security auditing tools, or hardened browser profiles (like some Chromium hardening guides recommend) can disable protocol handler registration as a potential fingerprinting or tracking vector.

5. Corrupted Browser Profile

In rare cases, a corrupted browser profile can cause permissions to behave erratically, showing as enabled but not actually working, or resetting every time you restart the browser.

Quick Tip: Before spending time on advanced troubleshooting, confirm which scenario applies to you. If the setting is grayed out in your browser, it's almost certainly a policy issue. If it's toggleable but not working, you're dealing with a profile or extension conflict.

Step-by-Step Fix: Google Chrome

Chrome is the most common browser where users encounter this issue, so let's start here.

Open Chrome Settings

Click the three-dot menu in the top-right corner of Chrome, then select Settings. Alternatively, type chrome://settings directly into the address bar and press Enter.

Navigate to Privacy and Security

In the left sidebar, click Privacy and security. Then click Site settings in the main content area.

Find the Handlers Permission

Scroll down to the Permissions section and click Additional content settings. You'll see an expanded list of less-common permissions. Look for Protocol handlers, it may also appear as "Allow sites to ask to become default handlers for protocols."

Enable the Permission

Click Protocol handlers to open the detail page. You'll see two radio button options:

Sites can ask to handle protocols, this is what you want
Don't allow any site to handle protocols, this is what you're turning off

Select Sites can ask to handle protocols. The change saves automatically, no restart required.

Clear Any Blocked Site Exceptions (If Needed)

While you're on the Protocol handlers page, scroll down to the Not allowed to handle protocols section. If the specific site you're trying to use appears there, click the three-dot menu next to it and select Remove. This clears the remembered "block" for that site so it can prompt you again.

Test the Fix

Navigate to the website that needs protocol handler access (for example, Gmail at mail.google.com). If the site needs to register a handler, it will now show a prompt in the address bar or as an infobar at the top of the page. Click Allow when prompted.

Important: If the toggle is grayed out and you can't change it, your organization has enforced this setting via Group Policy. See the "Group Policy and Enterprise Environments" section below.

Step-by-Step Fix: Microsoft Edge

Edge uses the same Chromium engine as Chrome, so the process is nearly identical, just with slightly different menu names.

Open Edge Settings

Click the three-dot menu (top-right), select Settings, or type edge://settings in the address bar.

Go to Cookies and Site Permissions

In the left sidebar, click Cookies and site permissions.

Find Protocol Handlers

Scroll down through the permissions list until you see Protocol handlers. It's usually near the bottom of the "All permissions" section.

Enable It

Click Protocol handlers, then select Allow sites to ask to handle protocols. Just like Chrome, this saves immediately.

Remove Blocked Exceptions

On the same page, check the Block list at the bottom. Remove any sites that should be allowed to prompt you.

Edge Shortcut: You can jump directly to this setting by pasting edge://settings/content/protocolHandlers into the address bar and pressing Enter.

Step-by-Step Fix: Mozilla Firefox

Firefox handles protocol handlers a bit differently from Chromium-based browsers. It doesn't have a single "allow sites to ask" toggle, instead, it manages handlers through the Applications settings and the about:config page.

Open Firefox Settings

Click the hamburger menu (top-right), select Settings, or type about:preferences in the address bar.

Go to the General Tab and Find Applications

On the General settings page, scroll down to the Applications section. This is where Firefox lists all known protocol and file type handlers.

Search for the Protocol You Need

Use the search box to find the protocol (e.g., "mailto"). Click the dropdown in the Action column next to it and select either a specific web handler or Always ask.

Re-enable Web Handler Prompts via about:config

If Firefox has stopped showing handler registration prompts entirely, type about:config in the address bar and press Enter. Accept the warning, then search for gecko.handlerService.allowRegisterFromDifferentHost. If the value is false, double-click it to toggle it to true.

Also check the preference gecko.handlerService.schemes, this controls which schemes Firefox recognizes as registerable.

Note for Firefox Users: Firefox stores handler registrations in your profile's handlers.json file. If you've recently migrated profiles or restored from backup, mismatched handler data can cause silent failures. We'll cover how to fix that in the Advanced Troubleshooting section.

Step-by-Step Fix: Safari (macOS)

Safari on macOS handles protocol associations differently, these are managed at the operating system level rather than inside the browser itself.

Open System Settings (macOS Ventura and Later)

Click the Apple menu, select System Settings, then go to General > Default web browser. Note: this controls the browser, not individual protocol handlers.

Use the Terminal for Protocol Associations

macOS uses Launch Services to manage URL scheme handlers. To reset a corrupted handler association, open Terminal and run:

/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -kill -r -domain local -domain system -domain user

This rebuilds the Launch Services database and can fix cases where protocol handler registrations are stuck or corrupted.

Check Safari's Website Settings

In Safari, go to Safari > Settings > Websites. Some protocol-related permissions may appear here depending on your macOS version. If you previously clicked "Don't allow" for a site's handler request, you can change it here.

Advanced Troubleshooting

Group Policy and Enterprise Environments

If you're on a managed Windows machine and the protocol handlers setting is grayed out, your IT admin has likely set the RegisterProtocolHandlers policy to disabled. Here's how to check and (if you have admin rights) fix it:

Check Effective Policies

In Chrome, navigate to chrome://policy. In Edge, go to edge://policy. Look for any policy named RegisterProtocolHandlers or ExternalProtocolDialogShowAlwaysOpenCheckbox. If these are listed with a value of false or 0, a policy is blocking you.

Edit Group Policy (Admin Required)

Press Win + R, type gpedit.msc, and press Enter. Navigate to:

Computer Configuration > Administrative Templates > Google Chrome > Content Settings

(or the equivalent Microsoft Edge path). Find Allow websites to register protocol handlers and set it to Enabled or Not Configured.

Edit Registry Directly (Admin Required)

If Group Policy Editor isn't available (Home editions of Windows), you can edit the registry directly. Press Win + R, type regedit, and navigate to:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge

Look for a value named RegisterProtocolHandlers. If it's set to 0 (disabled), change it to 1 (enabled) or delete the value entirely to let the browser use its own default.

Warning: Editing the registry incorrectly can cause serious system problems. Create a registry backup (File > Export) before making any changes. On a corporate machine, always get approval from your IT department first, changing policy settings without authorization may violate your organization's security policies.

Resetting the Handler Database (Chrome / Edge)

Sometimes the internal preferences file that stores handler registrations becomes corrupted. Here's how to reset it cleanly without wiping your entire browser profile:

Close Your Browser Completely

Make sure no Chrome or Edge windows are open, including background processes. Check Task Manager (Ctrl + Shift + Esc) and end any lingering browser processes.

Navigate to Your Profile Folder

Press Win + R and enter:

Chrome: %LOCALAPPDATA%\Google\Chrome\User Data\Default
Edge: %LOCALAPPDATA%\Microsoft\Edge\User Data\Default

Back Up and Delete the Preferences File

Find the file named Preferences (no extension). Rename it to Preferences.bak as a backup, then restart your browser. Chrome/Edge will create a fresh Preferences file with default settings. Note that this will reset some browser customizations, bookmarks and history are stored in separate files and won't be affected.

Diagnosing Extension Conflicts

If the setting appears enabled but web handler prompts still don't appear, a browser extension may be interfering. Test this by:

Opening a new Incognito or InPrivate window (extensions are usually disabled here by default)
Navigating to the site that should show a handler prompt
If the prompt appears in Incognito but not in a regular window, disable extensions one by one to find the culprit

Common offenders include ad blockers, privacy shields, and content security policy modifiers. Check the extension's settings for a "block protocol handlers" or "block custom protocol requests" option.

Firefox handlers.json Repair

If you're experiencing Firefox handler issues after a profile migration or backup restore:

Type about:support in Firefox's address bar and press Enter
Click Open Profile Folder
Find handlers.json in that folder
Open it in a text editor and look for entries with "action": 3, these are blocked handlers. Change the action value to 2 to set them to "Always ask" instead

How to Prevent This Issue in the Future

Be Deliberate When Responding to Permission Prompts

The most common way users end up in this situation is by reflexively clicking "Block" on browser permission prompts. When a website asks to handle a protocol, take a moment to read what it's asking. If it's a trusted service (like your company's web email client asking to handle mailto: links), click Allow. If you're unsure, you can dismiss the prompt and come back to it later through the site settings.

Document Your Handler Configuration

If you're an IT administrator managing browser configurations across a fleet of machines, document your intended protocol handler policy explicitly in your browser management templates. Use a policy like RegisterProtocolHandlers to pre-configure allowed handlers rather than relying on users to approve prompts individually. This ensures a consistent experience and avoids accidental blocks.

Use Browser Profiles for Different Contexts

If you use a single browser for both work and personal tasks, consider creating separate browser profiles. You can configure strict privacy settings (which might block protocol handlers) on your personal profile while keeping a work profile with looser permissions suited to your productivity tools.

Keep Your Browser Updated

Browser vendors regularly improve how permission prompts are presented and how handler registrations are stored. Staying on the latest version of your browser ensures you benefit from these improvements and reduces the chance of running into known bugs related to handler permissions.

Audit Extensions Periodically

Do a quarterly review of your browser extensions. Remove any you no longer use and check the permissions requested by the ones you keep. Extensions with broad content script permissions can interfere with protocol handler prompts even if that's not their primary purpose.

Frequently Asked Questions

Is it safe to allow sites to ask to become default protocol handlers?

Yes, enabling the permission to ask doesn't automatically grant any site the ability to handle protocols. It simply restores the browser's ability to show you the prompt. You still have to explicitly approve each site's request. As long as you're thoughtful about which sites you actually approve (stick to trusted services you use regularly), there's no meaningful security risk.

Why does Gmail keep asking to handle mailto: links every time I visit?

This usually means Gmail's handler registration isn't sticking. This can happen if your browser is running in a guest profile, if your cookies and site data are being cleared on close, or if your Preferences file is being reset by a policy or script. Check that you're not using "Clear cookies and site data when you close all windows", that setting will also wipe protocol handler registrations since they're stored alongside site data in some browsers.

How do I remove a handler I previously approved but no longer want?

In Chrome and Edge, go to chrome://settings/handlers or edge://settings/content/protocolHandlers. You'll see a list of all approved handlers under "Allowed to handle protocols." Click the three-dot menu next to any entry and select Remove. In Firefox, go to Settings > General > Applications, find the protocol, and either change the action to Always ask or remove the web handler from the dropdown.

The setting is enabled but the prompt still doesn't appear. What's wrong?

Several things can cause this. First, check if the site has already been blocked, look in the "Not allowed to handle protocols" section of your handler settings and remove the entry if it's there. Second, disable your browser extensions temporarily and test in an Incognito window. Third, the site may be using a non-standard or deprecated method to register its handler, check the browser's developer console (F12) for errors related to registerProtocolHandler. Finally, some Chromium versions require the page to be served over HTTPS for handler registration to work.

Can a website register a handler for any protocol, like file:// or javascript:?

No. Browsers maintain a strict allowlist of protocols that websites are permitted to register handlers for. Dangerous schemes like file://, javascript:, and data: are explicitly blocked by the HTML specification and browser security policies. Websites can only register handlers for a predefined set of safelisted schemes (like mailto, webcal, irc, ircs, magnet, and others) plus any custom web+ prefixed schemes.

My setting is grayed out and I'm on a personal computer. What can I do?

Even on personal machines, browser policies can get applied accidentally, for example, by certain software installers that write browser policy registry keys. Check chrome://policy (or edge://policy) to see if any policies are active. If you see policies listed that you didn't intentionally set, you can remove them by deleting the relevant registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome or the Edge equivalent. Run a malware scan as well, some adware and browser hijackers use policy injection to lock down browser settings.

Does this setting affect how desktop apps like Zoom or Slack handle their custom protocol links?

Mostly no. Desktop application protocol handlers (like zoom:// or slack://) are registered at the operating system level when you install the app, not through the browser's web handler system. The browser permission we've been discussing only controls whether websites can register as handlers. However, when you click a zoom:// link in your browser, you may see a separate "Open application?" prompt, that's controlled by a different browser setting called "External protocol requests," not the one in this guide.

Summary: Quick Reference

Here's a fast lookup table for enabling the protocol handlers permission across browsers:

Browser	Path to Setting	Direct URL
Google Chrome	Settings > Privacy and security > Site settings > Additional content settings > Protocol handlers	`chrome://settings/handlers`
Microsoft Edge	Settings > Cookies and site permissions > Protocol handlers	`edge://settings/content/protocolHandlers`
Mozilla Firefox	Settings > General > Applications + about:config	`about:preferences#general`
Safari (macOS)	Safari > Settings > Websites + System Settings	N/A (OS-level)

Still stuck? If you've gone through all the steps above and the permission still isn't working, the most reliable next step is to create a new browser profile (not a full reinstall, just a fresh profile). Go to chrome://settings/manageProfile in Chrome or edge://settings/profiles in Edge and add a new profile. Sign into the new profile with your Google or Microsoft account to sync your bookmarks and passwords, then test your protocol handler there. A fresh profile eliminates virtually every profile-level corruption issue in one shot.