A Fidelity Mac app: the account screen in a window of its own

The search for a Fidelity Mac app runs into something more interesting than a missing download. Fidelity does not publish one app for a Mac. It publishes three separate apps for the phone, each covering a different part of the same customer relationship, and on a Mac all three of them collapse back into the same place: a browser.

That detail is the useful one. Someone with a brokerage account, a workplace retirement plan, and a health account is not looking for one window. They are looking at three sign ins that fight each other inside a single browser, and that is a different problem from a missing installer. It also has a cleaner solution.

What Fidelity ships, and where

Apple's store lists three apps published by Fidelity Investments, all free, all mobile.

App Purpose as listed Minimum OS Listed devices
Fidelity Investments Invest, save, plan in one app iOS 17.0 iPhone, iPad, Apple Watch
NetBenefits Workplace benefits iOS 17.0 iPhone and iPad
Fidelity Health Health accounts iOS 18 iPhone and iPad

The main app is a substantial piece of software. The listing shows 408.7 MB, a rating of 4.8 out of 5 from 3.3 million ratings, and a position of number 17 in Finance. Its own description points workplace plan holders elsewhere, stating that anyone looking to manage workplace benefits should download the NetBenefits app, which is why the second row exists.

None of the three is a Mac build. A Mac App Store search for Fidelity Investments returns brokerage and portfolio tools from unrelated developers and nothing published by Fidelity Investments. Apple Silicon Macs can run some iPhone and iPad apps when the developer allows it, and these listings do not appear in Mac App Store results, so that route is closed as well.

Fidelity does publish desktop trading software under its own platform pages, aimed at active traders rather than general account holders. Anyone whose actual need is streaming quotes, a multi monitor layout, or a detachable chart grid should read the system requirements on those pages first, because no wrapped web page substitutes for a native trading terminal.

The three sign in problem

For everyone else, the real friction on a Mac is not features. It is that one browser holds one signed in session per site, and Fidelity's account areas expect to be signed into separately.

The result is a familiar cycle. The brokerage account is open in a tab. The workplace plan needs checking, so that gets signed into, and something displaces something. A health account statement is needed for a reimbursement, and the cycle runs again. Each sign in carries its own two factor step, and each one happens in a tab that looks identical to the eleven other tabs in the window.

Three symptoms follow from that, and all three are worth naming because they are what actually gets fixed.

The account is not an application, so Command Tab cannot reach it and a window tidy up closes it by accident. Notifications, where a site offers them, arrive attributed to the browser rather than to the account, so they get muted with everything else. And sessions expire while a tab sits idle behind other tabs, which turns a thirty second balance check into a sign in with a code from the phone.

Route one: Safari's Add to Dock

macOS Sonoma 14 added a built in way to give a page the standing of an application. In Safari, open the account page, choose File and then Add to Dock from the menu bar, name it, and click Add.

A web app functions independently of Safari. It shares no browsing history, cookies, website data, or settings with Safari. In this way, it keeps your browsing separate, similar to using a Safari profile. What you do in a web app stays in the web app. Source: support.apple.com

For the three sign in problem, that sentence is the answer. Three web apps means three separate cookie stores, so a brokerage account, a workplace plan, and a health account can each stay signed in without displacing one another. The displacement cycle simply stops.

The app lands in the Applications folder of the home folder and opens from the Dock or Spotlight. Its settings panel accepts a custom name, a custom URL, and a custom icon, which matters when three windows from the same provider need telling apart at a glance in the Dock. There is also a switch controlling whether the toolbar shows navigation controls at all, and a Privacy tab that can clear that site's cookies and caches without touching anything else.

Apple documents an unread count appearing as a red badge on the Dock icon, on one condition: the notification permission must be granted inside the web app rather than in Safari. After that the app appears in System Settings under Notifications by its own name rather than as a URL.

Two limits apply. The feature requires macOS Sonoma 14 or later. And extension support covers Safari extensions only, so a password manager that exists only as a Chrome extension stays behind.

Route two: Chrome's Install page as app

On an older Mac, Chrome does the same job. Its help pages describe opening the site, then choosing More, then Cast, save, and share, then Install page as app.

A web app is an app built for the web that you can access on any device. You can use web apps to have a website work as an app and access it on your computer or mobile devices through the launcher or home screen. Some web apps include extra features, like more storage to browse content offline, notifications, file system access, and icon badges. Source: support.google.com

File system access is the part that matters for a financial account, since statements, trade confirmations, and tax forms all arrive as downloads.

Chrome also carries a safeguard worth knowing about. Chrome notifies the user when an installed web app wants to change its own name or icon, and states directly that a name or icon suddenly resembling a different app is grounds for uninstalling it. For an account that holds money, that is a prompt to read rather than click through.

The limitation is the profile. An installed app runs on the Chrome profile it was created from, so its session and extensions are that profile's. One account is clean. Three accounts need three Chrome profiles set up first, which relocates the work rather than removing it.

Route three: a dedicated site to app tool

A tool that turns a website into a standalone Mac app is built to keep the app identity and the full browser underneath at the same time.

Profile isolation is the part that does the work here. Each app receives its own browser profile, and cookies, sessions, history, and cache stay inside it. Three account areas become three permanently signed in windows, and adding a fourth for a spouse's account or a trust changes nothing about the arrangement.

Space Mode is the alternative worth considering for exactly this case. Several sites combine into one application with a sidebar of icons for one click switching. Rather than three Dock entries, a single window holds brokerage, workplace plan, and health account, switched with one click and sharing nothing between them. For a set of screens that all belong to the same yearly review, that reads better than three icons.

Extensions come from the Chrome Web Store and switch on or off per app, so a password manager can run inside the account windows and nowhere else. The engine is selectable across Chrome, Chromium, Brave, Microsoft Edge, Vivaldi, Opera, and Chrome Canary, which occasionally matters when a financial site behaves differently in one engine. The tool also repairs its apps after a browser update, which was the failure mode that ended most older wrapper utilities: the browser updated, the wrapped app stopped launching, and nothing explained why.

Support goes back to macOS 12, four major versions earlier than Safari's Add to Dock reaches. The features page covers the rest, and the supported services list shows which sites arrive as presets out of more than three hundred, with anything else entered as a URL.

The three routes side by side

Safari Add to Dock Chrome install as app Site to app tool
macOS required Sonoma 14 or later Whatever Chrome supports macOS 12 or later
Three accounts signed in at once Yes, three web apps Needs three Chrome profiles Yes
All accounts in one window No No Yes, with sidebar switching
Extensions inside the window Safari extensions only Chrome extensions from that profile Chrome Web Store, per app
Custom icon per window Yes Follows the site Yes
Cost Included with macOS Free Free for up to three apps

One account on a recent Mac points at Safari, and it costs nothing to try this evening. An older Mac points at Chrome. Three account areas, or a preference for one window instead of three icons, points at the third route.

Four things to test before relying on it

A financial account does paperwork as well as display balances, and paperwork is where a stripped down window can fall short. Ten minutes settles it.

Download a statement. Tax forms and confirmations usually arrive as a PDF that opens in a new tab or triggers a download, and a window with no tab bar needs somewhere to send that. Many tools hand such links to the default browser, which is normally the preferred outcome.

Print a confirmation. Keeping a printed or saved record of a transaction is routine, and print dialogs behave slightly differently outside a full browser.

Check anything that opens a second window, such as a help chat, a document signing flow, or a detachable chart. Sites built for a full browser sometimes call for a popup, and a locked down window can refuse it silently.

Sign out and sign back in. That confirms the session survives a restart of the app, and reveals whether a device trust prompt reappears every launch, which would make the window worse than the tab it replaced. The guide covers the settings involved.

What does not change

The page inside the window is the same web platform Fidelity serves to a browser, with the same balances, the same order tickets, and the same research. Wrapping it adds no market data and no trading features, and session timeouts stay exactly as Fidelity sets them, which for an account holding money is correct behaviour rather than a limitation.

What changes is narrow. Each account gets an icon, a place in Command Tab, a notification identity of its own, and a window that no browser tidy up can close by mistake. For an account checked twice a week that is a convenience. For three accounts checked in rotation, it removes a sign in cycle that ran several times a month.

What to change first

Check the macOS version, because that alone decides between the first two routes. Then build one window for whichever account gets opened most, sign in once including the two factor step, and leave it a fortnight before touching the others. Kagemusha is free for up to three apps, which is exactly the number Fidelity's own set of mobile apps suggests is needed.

Frequently asked questions

Is there a Fidelity app for Mac?

Not from Fidelity. The three apps published by Fidelity Investments in Apple's store, Fidelity Investments, NetBenefits, and Fidelity Health, are all listed for iPhone and iPad, with the main app also supporting Apple Watch. No Fidelity Investments app appears in Mac App Store results, and the Apple Silicon route of running an iPad app on a Mac is not available for them either.

Why does Fidelity have three separate apps?

Each covers a different part of the relationship. The main Fidelity Investments app describes itself as a way to invest, save, and plan, and its own description directs anyone managing workplace benefits to download the NetBenefits app instead. Fidelity Health covers health accounts. On a Mac all three are reached through the browser, which is where the competing sign ins come from.

Does making the account a standalone window improve anything about trading?

No. The screen inside the window is the same web platform the browser loads, so balances, research, and order entry are identical. What improves is access: a Dock icon, a place in Command Tab, a separate notification identity, and a window that survives a browser tidy up. Anyone needing streaming data or a multi monitor layout should read the requirements for Fidelity's own desktop trading software.

Can a brokerage account and a workplace plan be signed in at the same time?

Yes, with the right route. Apple's documentation states that a Safari web app shares no cookies or website data with Safari, and a dedicated site to app tool assigns each app its own browser profile, so each window holds its own session. A Chrome installed app inherits the profile it was created from, so separate Chrome profiles would be needed first.

Is it safe to run a brokerage account inside a wrapped window?

The window is the same browser engine loading the same site over the same connection, so the security model is the browser's. Two habits are worth keeping: grant the notification permission inside the window rather than in the browser so alerts are attributable, and take Chrome's warning about an installed app changing its own name or icon seriously rather than dismissing it.

Back to all posts