Chrome app mode: three routes, and how to tell them apart

Chrome app mode means a Chrome window with no tab strip and no address bar, showing one site as if it were its own program. On a Mac in 2026 there are two working ways to get one. The first is the menu command Install page as app. The second is the --app= launch flag. A third route that many guides still describe, Create shortcut, now makes a launcher that opens an ordinary tab, which is why following an old tutorial so often ends with a tab instead of a window. Below: how each route works, what it leaves on disk, what changes inside the window, and the security issue that comes with the flag. The Google and Chromium pages cited here were opened and checked on October 18, 2026.

The three things people mean by app mode

	Install page as app	--app= launch flag	Create shortcut
Where to find it	More, then Cast, save, and share	Terminal or a script	More, then Cast, save, and share
Window without tabs	Yes	Yes	No, opens a tab
Listed at chrome://apps	Yes	No	No
Survives a restart as an object	Yes, an installed app	No, nothing is created	Yes, as a launcher
Documented by Google	Yes, in Chrome Help	No published list of switches	Yes, in Chrome Help
Uninstall path	From the app's own menu	Nothing to remove	Delete the launcher

The table answers most "it stopped working" questions. If the window you remember had no tabs and a Dock icon, it came from the first column. If it only appeared when a script ran, it came from the second. If a guide told you to tick an "Open as window" box and you cannot find the box, the guide was written before Create shortcut changed what it does.

Route one: Install page as app

This is the documented route. Google's Use web apps help page gives the steps:

1. Open Chrome and go to the site.
2. At the top right, select More, then Cast, save, and share, then Install page as app.
3. On some sites, an Install icon also appears at the right end of the address bar and does the same thing.
4. Follow the on-screen prompts.

The result opens in its own window, gets its own Dock icon while running, and appears in Command Tab separately from the browser. Chrome keeps a list of these at chrome://apps. The same help page says that right-clicking an app there offers Create shortcut, to put a launcher on the desktop or in menus, and Launch at startup, to open it when you sign in to the Mac.

To remove one, open the app, select More, then Uninstall followed by the app's name, then Remove. A checkbox labeled "Also delete data from Chrome" decides whether the site's stored data goes too.

What the window can do beyond hiding the tabs depends on the site. The same help page says some web apps include extra features, "like more storage to browse content offline, notifications, file system access, and icon badges", and adds that some may not work completely without an internet connection. A site built as a progressive web app gets those extras. An ordinary page installed this way gets a window and an icon, and nothing more.

Two behaviors are worth knowing before relying on this route. First, the help page says that when a web app wants to change its name or icon, Chrome notifies you and offers Update, Ignore or Uninstall. It also warns that a name or icon suddenly changing to look like a different app is a sign to uninstall. Second, the app belongs to the Chrome profile it was installed from. It shares that profile's cookies, sign-ins and extensions. Installing Gmail twice from the same profile does not give two separately signed-in windows.

Route two: the --app launch flag

The older form of app mode is a command-line switch. Passing --app= followed by a URL opens that page in a window with no tabs and no address bar. It is what most forum answers and older blog posts mean by "application mode".

On a Mac the command needs one detail. If Chrome is already running, a plain launch hands the request to the running copy and the flag is ignored. The Chromium project's page Run Chromium with command-line switches tells macOS users to quit any running instance first, for example by going to chrome://quit, and then run the binary inside the app bundle from Terminal. In practice, either of these works:

/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --app=https://example.com
open -na "Google Chrome" --args --app=https://example.com

The same Chromium page also says plainly that there is no official list of switches, because they change often. That puts the flag in a different category from the menu command. It is a developer tool that has worked for many years, not a product feature with a support page.

The flag creates nothing. No entry appears at chrome://apps, no bundle is written, and there is nothing to uninstall. For a script that opens a dashboard on a wall screen each morning, that is exactly right. For a site you use daily, it means the window disappears from memory the moment the script does.

The flag also says nothing about which profile to use. On a Mac with several Chrome profiles, a launch that does not name one opens in whichever profile Chrome treats as current, so the same command can open signed in to work one day and personal the next. Adding --profile-directory= with the profile folder name, such as Default or Profile 1, removes that variation.

Because the switch belongs to Chromium rather than to Chrome alone, other Chromium-based browsers accept it too. Change the application name and the same command works with Edge or Brave. A script copied from a forum that seems broken in Chrome is often just pointing at a different browser.

Route three: what Create shortcut does now

The third route causes the most confusion, because the label stayed the same while the result changed. Google's current help page, Create shortcuts for websites in Chrome, describes a dialog with a single field: a name, then Create. There is no window option. The shortcut opens the site in a normal browser tab.

The window behavior that the old Create shortcut dialog offered through its "Open as window" checkbox now sits under Install page as app. The checkbox was not moved into settings. The choice it controlled became its own menu item.

So if a tutorial says to use Create shortcut and tick a box, use Install page as app instead. If you already have shortcuts made the new way and want them as windows, install the same pages as apps and delete the old launchers.

What changes inside an app mode window

The visible change is the missing tab strip and address bar. The changes in behavior take longer to notice.

Tab shortcuts stop doing anything useful, because there are no tabs to switch to. The shortcut that focuses the address bar has nothing to focus. Anyone who moves around by typing URLs has to use links on the page instead.

Links that stay inside the site stay in the window. Links to other sites are passed to an ordinary browser window, which comes to the front. For a dashboard that rarely links out, this is invisible. For mail or chat, where most clicks open something on another domain, it happens all the time. A Reddit thread among the top results for this search is about exactly that: stopping new windows from opening.

Extensions still run, because the window is still Chrome running on the same profile. A password manager or content blocker installed in that profile works in the app window as it does in a tab. That is a real advantage over Safari's Add to Dock, which uses Safari extensions only.

The security catch with the flag

In October 2022, BleepingComputer reported a phishing technique built on the flag (Web browser app mode can be abused to make desktop phishing pages, October 3, 2022). The report explains that a window opened with --app= hides the address bar, so a fake sign-in page can look like a desktop program's login prompt. It also notes that application mode exists in all Chromium-based browsers, naming Chrome, Edge and Brave.

That does not make app mode unsafe to use. It does change two habits:

• Do not run a shortcut or script someone else sent you if it launches a browser with --app=. Open the link in a normal tab, where the address is visible.
• For sites where you type passwords, prefer Install page as app over a script. An installed app is visible at chrome://apps and Chrome warns you if its name or icon changes.

An app mode window has no address bar to check, so the only way to know where it points is to know how it was created. That is one more reason to keep daily-use windows in a form you can list and inspect.

When app mode is not enough

Chrome's two routes leave two gaps for Mac users.

The first is accounts. Installed apps share their profile, so running two accounts of the same service side by side means maintaining two Chrome profiles and remembering which app came from which. The second is control. The Use web apps help page lists no per-app setting to keep links inside the window, restrict which domains it can visit, or decide how pop-ups behave.

A tool that turns a website into a standalone Mac app fills these gaps by building a separate application with its own browser profile. Taking one published product as an example, its Guide documents per-app settings that line up with the gaps above:

Gap in Chrome app mode	Setting in that tool	Default
Shared profile and sign-in	Each app is assigned its own profile automatically	Always on
No guard against an accidental Command Q	Quit Confirmation dialog	Off, can be turned on per app
Pop-ups open unpredictably	Window Handling: Block All, Smart or Allow All	Smart
No limit on where the window goes	URL Rules with an allow list or block list	No rules
Address bar and tabs are all or nothing	Tab Bar toggle per app	Off

The Features page lists seven supported browser engines and per-app extension switches. The Pricing section showed, on October 18, 2026, a free tier of up to three apps and a one-time Pro price of $24.99. Because these apps run on the browser installed on the Mac, extensions from the Chrome Web Store still work, which is the property most people want to keep when leaving app mode.

What to change first

Open chrome://apps and see what is there. Anything listed is a proper installed app. Anything you open with a script or a shortcut that ticked a box is the flag or an old shortcut, and the sites you use daily should be reinstalled through Install page as app. If a site needs its own sign-in, a quit confirmation or a fixed set of domains, build it as a separate app instead; Kagemusha is one tool that does that.