Dialpad on a Mac: what the download gives you, and the other way

A Dialpad Mac download sounds like one file. It is four different things, and picking the wrong one is how a business phone line ends up ringing in a window nobody is looking at. There is a native installer with two variants, a separate installer for meetings, a Chrome extension, and a progressive web app. Each of them solves a different half of the problem, and the half that matters depends on whether the job is answering calls or reaching numbers that appear on other people's web pages.

What the download page actually offers

Dialpad's own download page is organised in tabs labelled Mac, Windows, Mobile and Other, which is already a hint that the answer is not a single file.

Under the Mac tab there are two products, each with two buttons. Dialpad offers Download for Apple Chip and Download for Intel Chip, and Dialpad Meetings offers the same pair separately. The files behind those buttons are .pkg installers rather than disk images, which means the macOS Installer runs through a sequence of screens rather than the familiar drag into the Applications folder.

Two details follow from that shape and both are worth knowing before clicking.

The first is that the chip choice is manual. There is no universal build that decides for itself, so a Mac bought in the last few years takes the Apple Chip file and an older machine takes the Intel one. Taking the wrong one is recoverable but wastes a download of real size.

The second is that meetings are a separate application. Calling and messaging live in one app, scheduled video meetings live in another, and installing one does not install the other. Anyone whose day involves both ends up with two icons in the Dock from a single vendor, which is a reasonable thing to know in advance rather than discover.

Under Mobile, the iOS build comes from the App Store and the Android build from Google Play. Under Other sit the two pieces most people never find, and they are the interesting ones.

The two routes that are not an installer

The Chrome Web Store listing is called Dialpad Chrome CTI, published by Dialpad, Inc. At the time of writing it shows version 0.1.45, updated on 14 September 2026, at 993 KiB, with around 60,000 users and a rating of 3.1 out of 5 from 15 ratings. What it does is narrow and useful: hover a phone number on a web page to call or text it, with a dialer, call history and contacts reachable without leaving the tab. It works on a preset list of sites, and other domains can be added from Dialpad settings.

The second route is a progressive web app. Dialpad publishes an install page whose heading is Dialpad Progressive Web App, and the page installs it directly rather than handing over a file. That is the same mechanism a Chromium browser uses to turn any page into a standalone window, applied to Dialpad by the vendor.

The existence of that page settles a question people otherwise ask sideways. Running Dialpad as a browser based window is not a workaround that someone invented in a forum. It is a shape Dialpad ships on purpose.

The mobile listing, and what it rules out

The App Store listing is worth checking because it closes off a route that gets suggested often on Apple silicon.

Dialpad is published by Dialpad, Inc, it is free, and it sits in the Business category at 351.1 MB. The rating is 4.6 out of 5 from around 4,600 ratings, and the current build shown is version 69.0.1 from 16 September. The compatibility section names iOS 17.0 or later on iPhone, iPadOS 17.0 or later on iPad, and visionOS 1.0 or later on Apple Vision.

macOS is absent from that list. On Apple silicon a developer can choose to make an iPhone or iPad build available on the desktop, and when that happens the listing says so by naming macOS in its compatibility section. This one does not, so installing the mobile app on a Mac is not an option, and the Mac route is the .pkg installer or the browser.

Where the tab actually costs something

A phone system in a browser tab has a specific failure mode that a document or a dashboard does not share, and it is worth being precise about it.

The cost is not loading time. A Dialpad tab left open all day is already loaded. The cost is that a tab has no fixed position, no entry of its own in Cmd+Tab, and no name in Spotlight. Reaching it means bringing the browser forward first and then finding it among everything else the browser is holding. For a document that is a small annoyance. For an inbound call it is the difference between answering and not.

There is a second failure mode that only applies to long lived tabs. A tab open for days gets closed during a tidy up, or disappears into the middle of a restored session after the browser is restarted for an unrelated reason. Twenty restored tabs restores the phone somewhere in the pile, still signed in, no longer findable by position, and the habit of reaching for it by muscle memory is broken until the strip settles again.

The third is notification permission. A browser holds one notification permission per site per profile, and that permission was granted to the browser rather than to a phone. Anything that quietens the browser quietens the phone with it.

The routes, side by side

Route	Setup	Dock and Cmd+Tab	Separate session per window	Chrome extensions inside	Suits
Native .pkg installer	Installer, chip specific	Yes	One account at a time	No	One account, heavy call volume
Browser tab	None	No	No	Yes, browser wide	Occasional use
Dialpad progressive web app	Install from the vendor page	Yes	Follows the browser profile	Follows the profile	One account, daily use
Chrome, install page as app	Three clicks	Yes	Follows the Chrome profile	Follows the profile	Already committed to Chrome
Safari, Add to Dock	Two clicks	Yes	Yes	No	One account, no extension needed
Site to app tool on a Chromium engine	Pick the URL, build once	Yes	Yes, per app	Yes, per app	Several organisations or numbers

The Safari route is genuinely free and takes two clicks, through File then Add to Dock.

A web app functions independently of Safari. It shares no browsing history, cookies, website data, or settings with Safari. Source: support.apple.com

That isolation is exactly what a phone wants, and the same Apple documentation notes that the number of unread notifications appears as a red badge on the window's Dock icon, with one condition: the notification permission has to be granted inside the window rather than in Safari for the window to appear in Notifications settings at all. For a phone line that condition is the entire feature.

The limitation of the Safari route is the extension. A Safari window cannot load Dialpad Chrome CTI, because that build is for Chrome. Anyone whose actual complaint is that phone numbers on a CRM page are not clickable needs a Chromium engine, not a Safari one, and the general shape of what a dedicated window covers is set out on the Features page.

Chrome's equivalent, and the profile problem underneath

Chrome installs a page as an application from the three dot menu, then Cast, save, and share, then Install page as app, with installed items listed at chrome://apps.

A web app is an app built for the web that you can access on any device. Source: support.google.com

For one Dialpad login this is enough and takes three clicks. The constraint is the unit of separation. A window created from a Chrome profile signs in as whatever account that profile holds and keeps sharing that session, and extensions belong to the profile as well, so Dialpad Chrome CTI has to be installed in each profile that needs it.

That becomes a real cost in exactly the situation where a business phone gets complicated. An agency answering for three clients, or a contractor given a seat in a customer's Dialpad, has genuinely separate accounts rather than separate numbers on one account. A browser holds one session per site per profile, so the usual workarounds are a private window that forgets everything on close, a second browser to remember, or signing out and in. Each of those is how a call gets answered with the wrong company's greeting. A tool that turns a website into a standalone Mac app gives every app its own isolated profile and its own icon, which is why the separation holds without any switching, and the common services already set up this way are listed on the Supported services page.

Progressive web app or purpose built window

Since Dialpad publishes a progressive web app itself, it is fair to ask what a separate tool adds. The answer is narrow and it is about ownership of the container rather than about capability.

A progressive web app is installed by the site, and what it can do is set by what the site asked for: its name, its icon, its starting address, its scope. That is the right arrangement when a vendor has thought carefully about the window, and Dialpad evidently has.

What stays outside the site's control is the profile the window runs in, the browser engine it runs on, and whether extensions are available inside it. Those three belong to the browser, so a vendor installed window inherits them rather than choosing them. A window built by a separate tool is the other way round: the tool picks the engine, assigns an isolated profile per app, and decides whether extensions load, and the site simply runs inside whatever it is given.

For one account the two are close to equivalent and the vendor's own version is less work. The gap opens at the second account, and it opens entirely because of the profile.

What to check in the first week

Five checks are worth running deliberately, because a phone exercises parts of the browser that reading sites never touch.

Microphone permission first. Grant it inside the new window, then place one real outbound call and one inbound call. A window that can dial but cannot be heard is the most common and most embarrassing result of skipping this.

Second, notifications. Confirm an incoming call raises something visible while the window is behind other windows, not only while it is in front.

Third, sign in survival. Restart the Mac, then let a macOS update through, and check the window still opens signed in.

Fourth, the transfer and hold controls under load. These are the parts of a softphone that use browser features most aggressively, and a quiet Tuesday is a better time to find a problem than a busy Monday.

Fifth, audio device switching. Plug in a headset while a call is live and confirm the audio follows. The setup steps for a window of this kind, including how the name, icon and starting URL are set, are in the Guide.

What to change first

If the work is high call volume from one account and nothing else, take the native installer, matching Apple Chip or Intel Chip to the Mac, and accept the second icon for meetings. If Dialpad is one of several services already living in tabs, build it a window on a Chromium engine instead, grant microphone and notification permission inside that window on day one, and leave the installer alone. For more than one organisation, a purpose built Kagemusha app per account is what keeps each line answering as itself.