How to Make a Phone Call From Your Browser (No App, No Install)

You can call from your browser the same way you'd open any website: type an address, click a button, talk. No download, no install, no admin rights, no SIM card. Every modern browser ships with the technology to do this, and it has for over a decade. What most people are missing is not software but a clear picture of how a browser phone works, what it can reach, and where the free options stop being free.

This guide covers all of that: what a web dialer actually is, the step-by-step process of making a call from your browser, how to fix the microphone problems that cause most failed calls, and how to judge whether a browser calling site is trustworthy before you give it your mic.

What a browser phone actually is

A browser phone, sometimes called a web dialer or web phone, is a website that behaves like the dialer app on your mobile. It shows you a keypad, you enter a phone number, and when you press call, your voice travels from your computer's microphone over the internet to the service's servers, which connect the call onward.

Where the call goes from there splits into two very different cases:

Browser to browser. Both people are on a website or app, and the audio never touches the phone network. This is what happens on a Google Meet link or a FaceTime web link. It costs the provider almost nothing, which is why it's usually unlimited and free.
Browser to phone number. You dial a real landline or mobile number, and the service hands your call to the traditional phone network. This crossing costs the provider real per-minute fees, which is why it is never unlimited and free at the same time.

Most of the confusion around browser calling comes from mixing these up. A site can honestly offer "free calls" and still charge you to reach your bank's support line, because those are two different products under the hood. If you want the full landscape of options beyond the browser, the overview of every way to call from your computer compares them side by side.

WebRTC in plain words

The reason no install is needed is a browser feature called WebRTC, short for Web Real-Time Communication. It has shipped in Chrome and Firefox since around 2013 and in every major browser since, and it gives websites three abilities, each gated behind your permission:

Capture audio from your microphone, only after you explicitly allow it for that site.
Encode it into a compressed, packet-friendly format in real time, using codecs built into the browser.
Send and receive those audio packets directly, with encryption that is mandatory, not optional.

That's the whole trick. The website provides the interface and the connection to the phone network; your browser provides the actual audio machinery. It is the same plumbing that powers Google Meet, Discord in a tab, and FaceTime links, so it is heavily tested and maintained by the browser vendors themselves. If you're curious what happens to your voice after the browser encodes it, the deeper explainer on how internet calling works follows a call packet by packet.

One useful consequence: because WebRTC is a browser standard and not a plugin, a web dialer that works in Chrome on Windows works the same in Chrome on a Mac, a Linux machine, or a Chromebook. The operating system stops mattering.

How to make a call from your browser, step by step

The process takes under a minute on any web dialer:

Open the calling site in Chrome, Edge, Firefox, or Safari. Check that the address bar shows HTTPS. Browsers refuse to hand microphone access to plain HTTP sites, so a dialer without HTTPS cannot work at all.
Allow microphone access when the browser asks. The prompt appears near the address bar. This permission is per-site, so allowing it here does not let other websites listen.
Enter the number in international format. Start with the country code: +1 for the US and Canada, +44 for the UK, +49 for Germany. Web dialers usually can't guess your country the way your mobile can, so a number without a country code often fails or connects to the wrong place.
Press call and wait for ringing. Connection usually takes a couple of seconds longer than on a mobile, because your call is being routed through the provider's servers into the phone network.
Talk through a headset if you can. Laptop mics work, but they pick up fan noise and echo. Any earbuds with an inline mic will sound noticeably better to the person on the other end.

That's it. No account is needed on some services for a short trial call; others ask you to sign up first. Either way, the calling part is identical.

Fixing microphone problems

When a browser call fails, it is almost always the microphone, and it is almost always one of these four things, in this order:

The site permission is blocked. Click the icon to the left of the address in the address bar and check the microphone entry. If you dismissed or denied the prompt earlier, the browser remembers, and the site cannot ask again until you reset it. Set it to Allow and reload the page.
The browser picked the wrong microphone. If you have a webcam, a headset, and a built-in mic, the browser chose one of them, possibly an unplugged one. Look for a device picker in the site's settings, or change the default input device in your system sound settings and reload.
The operating system is blocking the browser. On macOS, System Settings, then Privacy and Security, then Microphone must show your browser toggled on. On Windows, Settings, then Privacy, then Microphone has the same switch. This layer sits above the browser, so no amount of clicking Allow in Chrome helps if it's off.
Another app is holding the mic. A running Zoom, Teams, or recording app can claim exclusive access on some systems. Quit it and reload the tab.

A quick way to isolate the problem: open any browser mic test page. If the test hears you, your hardware and OS are fine and the issue is the calling site's permission. If it doesn't, the problem is below the browser.

Why free browser calls are always limited

Every free web dialer caps you somewhere: minutes per call, calls per day, or reachable countries. This is not stinginess, it's arithmetic. When your call leaves the internet and enters the phone network, the provider pays a termination fee to the carrier that completes the call. It's a fraction of a cent to a few cents per minute depending on the country and whether the destination is a landline or mobile, but it is greater than zero on every single call.

A provider giving away unlimited calls to phone numbers would be paying carriers an unbounded bill on your behalf. So free tiers exist as trials and goodwill, funded by the users who upgrade, and they are limited by design. The honest mental model: browser-to-browser audio can be genuinely free forever, while browser-to-phone-number calls are always metered somewhere, even if the meter starts at zero. If free is the priority and you're flexible about how you reach people, there are several genuinely free ways to call online worth comparing before paying anyone.

Which browsers support calling

All of them. As of today, Chrome, Edge, Firefox, and Safari all ship full WebRTC support, including the audio processing that makes calls usable: echo cancellation so the other person doesn't hear themselves, and noise suppression that filters fans and keyboard clatter. The differences that remain are edge cases, but they're worth knowing before you troubleshoot:

Browser	WebRTC support	Echo cancellation	Noise suppression	Notes
Chrome	Full	Built in, on by default	Built in, on by default	The reference platform. Web dialers are built and tested here first.
Edge	Full	Built in, on by default	Built in, on by default	Same engine as Chrome, so effectively identical behavior.
Firefox	Full	Built in, on by default	Built in, on by default	Rarely, a site's device picker behaves differently than in Chrome.
Safari	Full	Built in	Built in	Arrived years after the others (2017) and is stricter: audio often needs a user click to start, and background tabs get throttled harder.
Anything on iOS	Full, via Safari's engine	Same as Safari	Same as Safari	Every iOS browser uses Safari's engine underneath, so Safari's rules apply everywhere on iPhone and iPad.

Safari's reputation as the problem child is mostly historical at this point. It was the last major browser to adopt WebRTC, and for years guides warned people off it, but current versions handle browser calls fine. What survives of that era is a stricter interpretation of the rules: Safari insists on a user gesture before audio starts, which is why some dialers show an extra "tap to enable audio" step on iPhones, and it suspends background tabs more aggressively, which can mute a call you've tabbed away from.

Practical advice: if a dialer misbehaves in Safari or an older browser, try Chrome or Edge before concluding the service is broken. And keep the calling tab in the foreground on laptops with aggressive battery saving, since some systems throttle backgrounded tabs enough to degrade audio.

Calling without a phone number of your own

One thing that surprises people: making outbound browser calls requires no phone number on your side at all. No SIM, no carrier, no number registered to you. The service places the call from its own infrastructure, and your browser is just the microphone and speaker on one end of it. If your phone is lost, your SIM is dead, or you simply never had a number in the country you're sitting in, none of that stops you from dialing out.

Two consequences follow from that, and both matter before you rely on it. First, caller ID: the person you call sees the service's number or a number from its pool, not anything identifying you. That's fine for calling a hotline or a hotel, but a friend seeing an unknown foreign number may not pick up, so say who you are quickly or warn them by message first. Second, direction: having no number means nobody can call you. Outbound is free of the whole number system; inbound is impossible without one. If you need people to reach you back, that's what renting a virtual phone number solves, and it's a separate product with a separate (usually monthly) cost.

Security: what to check before you dial

A website you allow microphone access to deserves a moment of scrutiny. The risks are modest but real, and the checks are quick:

HTTPS only, always. The browser enforces this for mic access anyway, but it bears stating: never enter payment details or a phone number you care about on a calling site without the padlock.
Permission hygiene. Grant the mic to sites you actually call from, and revoke it when you're done with a service you won't use again. In Chrome this lives under Settings, then Privacy and security, then Site settings, then Microphone. A site with a standing permission can only listen while you have it open, but there's no reason to leave grants lying around.
Be wary of dialers demanding odd permissions. A web phone needs your microphone and nothing else. Requests for notifications are common and harmless, but a calling site asking for your location or contacts is overreaching.
Know what the recipient sees. Your call arrives with the service's caller ID or a number it assigns, not your personal number. That's a feature for privacy, but it also means some recipients screen or reject unknown numbers. If you need a stable identity people can call back, that's a job for a virtual phone number of your own rather than an anonymous dialer.

When a browser call beats an app

Installed apps have their place, but the browser wins cleanly in a handful of situations:

Locked-down machines. Work laptops and school computers often block installs entirely. A browser tab needs no privileges.
One-off calls. Installing, signing up, and verifying a phone number to make a single two-minute call is absurd overhead. A web dialer does it in the time the app store would take to load.
Borrowed or public computers. Close the tab, revoke the permission, and you've left nothing behind. An installed app with a logged-in account is a different story.
Your phone is dead, lost, or abroad. The classic emergency case. Any computer with a mic becomes a phone in under a minute.
Cross-platform consistency. The same tab works on Windows, macOS, Linux, and ChromeOS, which no installed calling app can claim.

Three of these come up often enough to spell out. The locked-down corporate laptop is the classic: IT has disabled installs, the app store is blocked, and getting a calling app approved means a ticket and a week of waiting. A browser tab sidesteps the entire process, because it needs exactly the privileges a website needs, which is none. You're not circumventing policy either; you're using the browser IT already sanctioned, and the mic permission prompt works the same as it does for the video meetings they expect you to join.

The second is the traveler on a machine that isn't theirs. A hotel business center, a library terminal, a friend's laptop abroad: your SIM is roaming or dead, the machine has no calling software, and you need to reach an airline or confirm a booking on a local number. Any browser on that machine becomes a working phone in under a minute, and when you close the tab and revoke the mic permission, you've left no account logged in and nothing installed on hardware you'll never see again.

The third is the support or sales agent working from home. Call-center software used to mean provisioned desk phones or heavyweight installed clients; browser-based calling means an agent needs a laptop, a headset, and a URL. This is the same WebRTC plumbing described above, which is exactly why so much modern contact-center software runs entirely in a tab. If you've ever called a company and reached someone in their home office, there's a decent chance their end of the call was a browser.

Where an app still wins: daily heavy use, incoming calls while the browser is closed, and tight integration with contacts and notifications. If you're calling every day, compare the best apps to call from your computer instead of living in a tab.

Frequently asked questions

Can I make a phone call from my browser for free? Browser-to-browser calls (Meet links, FaceTime links) are free without real limits. Calls from a browser to a real phone number are free only within a capped trial or free tier, because the provider pays the phone network per minute. Expect a few free minutes, then a paid rate.

Why can't the other person hear me on a browser call? In order of likelihood: the site's microphone permission is blocked, the browser selected the wrong input device, or the operating system is denying mic access to the browser entirely. Check the address bar permission first, then the device picker, then the OS privacy settings.

Does calling from a browser work on Safari and iPhone? Yes. Safari has supported WebRTC since 2017, and every iOS browser uses the same engine. Safari is stricter about starting audio without a click and throttles background tabs, so keep the calling tab active during the call.

Is a browser phone safe to use? The audio itself is encrypted, since WebRTC requires it. The practical risks are the site operator's trustworthiness and your own permission hygiene: stick to HTTPS sites, grant the mic only where you call, and revoke permissions you no longer use.

Can I receive calls in my browser too? Only with a service that assigns you a number, like Google Voice or a virtual number provider, and usually only while the tab is open. Anonymous web dialers are outbound-only, so if receiving matters, you'll want a service that gives you a number of your own.

A browser call is the fastest path from "I need to dial a number" to a ringing phone. Keep a web dialer bookmarked for the emergency case, and if calling becomes routine, graduate to one of the installed options compared above.