How to make a web app on a Mac without coding

To make a web app on a Mac without writing code, open the site in Safari and choose File, then Add to Dock. That needs macOS Sonoma 14 or later and takes under a minute. Chrome offers the same idea through its menu: Cast, save, and share, then Install page as app. A third route, a tool that turns a website into a standalone Mac app, adds things the two browsers leave out, such as a choice of browser engine and a separate sign in for each app. This guide gives the exact steps for each, what they keep separate, and how to choose. Menu names and requirements were checked on Apple's and Google's help pages on October 18, 2026.

Two different jobs share this search

The phrase "make a web app" means two things, and the results mix them.

One is building a web application from scratch: writing HTML, CSS and JavaScript, often with a framework, and either serving it on the web or packaging it with something like Electron. Electron's own prerequisites page describes it as a framework for building desktop applications using JavaScript, HTML and CSS, run in a Node.js environment, and assumes familiarity with Node. That is a developer project measured in days.

The other is taking a site that already exists, such as a mail client, a project tracker, a chat service or an internal dashboard, and giving it its own window and Dock icon so it stops getting lost among browser tabs. That takes minutes and no code. It is what Apple's support pages, Google's help pages and most of the ranking guides actually describe.

This article covers the second job. A quick test: if the site already works in a browser and the goal is to open it like an app, no programming is involved. If the site does not exist yet, the routes below are not the starting point.

Within the no code job, there are three routes on a Mac today:

	Safari web app	Chrome installed app	Site to app tool
How to create	File, then Add to Dock	Cast, save, and share, then Install page as app	Pick a preset or enter a URL
Minimum system	macOS Sonoma 14	Current Chrome	Depends on the tool
Engine	Safari (WebKit)	Chrome	A browser chosen per app
Separate from the main browser	Yes, no shared cookies or history	Runs from the Chrome profile it was installed from	Separate profile per app in most tools
Extensions	Safari extensions, per web app	Chrome profile's extensions	Varies by tool
Cost	Free	Free	Free tier or paid, depending on tool

Route one: Safari Add to Dock (macOS Sonoma 14 or later)

Apple's support article Use Safari web apps on Mac states that starting with macOS Sonoma 14, any webpage can be saved as a web app that runs independently of Safari.

The steps, using Apple's wording:

1. In Safari, open the webpage to use as a web app.
2. From the menu bar, choose File, then Add to Dock. Alternatively, click the Share button in the toolbar and choose Add to Dock.
3. Type a name for the web app, then click Add.

The web app is saved to the Applications folder inside the home folder, and opens from the Dock or Spotlight. Apple's Safari User Guide adds that if the site was already signed in, the web app is signed in too in most cases.

The defining trait is separation. Apple's article says a web app shares no browsing history, cookies, website data or settings with Safari, similar to using a Safari profile. That is useful for keeping work tools out of personal browsing, and it also means signing in once more inside the web app in some cases.

To adjust it later, open the web app, click its name in the menu bar, and choose Settings. The fields are Application Name, Application URL (with a Set to Current Page button), Icon, Show navigation controls and Show color in title bar. A Privacy tab clears the site's data, and an Extensions tab turns Safari extensions on or off for that web app.

Notifications work as well. When a site asks permission inside the web app and the answer is Allow, alerts appear in Notification Center and the Dock icon shows a red badge with the unread count. The web app then appears by name under System Settings, Notifications.

To delete one, open the home folder in Finder (Go, then Home), open Applications, and drag the web app to the Trash.

The main limit is the system requirement. A Mac on macOS Ventura 13 or earlier does not have Add to Dock.

Route two: Chrome's Install page as app

Google's help page Use web apps gives the current steps for Chrome on a computer:

1. Open Chrome and go to the website.
2. At the top right, select More, then Cast, save, and share, then Install page as app.
3. Follow the on screen instructions.

On some sites an Install button also appears at the right end of the address bar. Those are sites built as progressive web apps; Google notes that some web apps include extra features such as more storage for offline use, notifications, file system access and icon badges. For a site that is not built that way, Install page as app still creates a window for it.

Managing installed apps happens at chrome://apps. Right clicking an app there offers Create shortcut and Launch at startup, the latter opening the app automatically when signing in to the Mac. To uninstall, open the app, select More at the top right, choose Uninstall, and confirm Remove; ticking "Also delete data from Chrome" removes its data too.

Two traits shape the choice. The installed app uses the Chrome profile it was installed from, so it shares that profile's sign ins rather than having its own. And it needs Chrome on the Mac, though not a particular macOS version beyond what Chrome itself supports. For someone who already lives in Chrome, this is the fastest route with nothing extra to install.

Route three: a tool that turns a website into a standalone Mac app

The third route is a dedicated app whose only job is wrapping websites. These tools vary widely. Some bundle their own copy of Chromium, some use Safari's engine, and some build on a browser that is already installed. It is worth reading each tool's feature page for four things: which engine it uses, whether each app gets its own profile, whether browser extensions work, and how pricing works.

As one concrete example, the Mac tool behind this site lists the following on its features page and setup guide, checked on October 18, 2026:

• macOS 12 or later, on Apple silicon and Intel Macs.
• Seven browser engines to build on: Chrome, Chrome Canary, Chromium, Brave, Microsoft Edge, Vivaldi and Opera. Only installed browsers appear as choices.
• A separate browser profile for each app, so cookies and sign ins never mix, which lets two Google accounts stay signed in at once in two apps.
• Chrome Web Store extensions, turned on or off per app.
• More than 300 service presets with the URL, icon and name filled in, plus a Custom option for any URL.
• A free plan for up to 3 apps with every feature, and a $24.99 one time Pro purchase for unlimited apps, per its pricing section.

The steps there are short. Click Create New in the sidebar, search for the service or choose Custom and enter the URL and a name, choose a browser engine, and click Create App. The app is saved in its own folder inside Applications and launches from App Manager or the Dock.

This route is mainly useful in three cases: a Mac below macOS 14 that has no Add to Dock, a site that works better in a Chromium browser than in Safari, and work that needs several accounts on the same service signed in side by side.

Choosing the route by situation

The table at the top lists features. In practice the decision usually comes down to one question each.

Which macOS is the Mac on? On Sonoma 14 or later, Safari's Add to Dock is built in and free. Below that, it is Chrome or a separate tool.

Which browser does the site work best in? Some web services are built and tested mainly against Chrome. If a site misbehaves in Safari, wrapping it in Safari will not help. The Chrome route or a tool that uses a Chromium engine avoids that.

How many accounts on the same service? Safari web apps are separated from Safari, and Chrome apps follow their Chrome profile. Running two accounts of the same service side by side means two Safari web apps for two sites, two Chrome profiles, or a tool that gives each app its own profile.

Which extensions must come along? Apple's settings include an Extensions tab per web app for Safari extensions. Chrome apps use the extensions of the Chrome profile. A password manager or ad blocker that exists only for Chrome points to the Chrome based routes.

Should it open at login? All three routes can do this, in different places. Apple's article says a Safari web app can be added as a login item, which is set in System Settings, in the Login Items list. Chrome's help page describes right clicking the app at chrome://apps and choosing Launch at startup. A tool that produces ordinary .app files can use the same Login Items list as any other app. For a mail client or team chat that should be ready the moment the Mac starts, this one setting often matters more than the choice of route.

How many sites? Two or three sites are easy to manage by hand in any route. Ten or more is where presets, consistent icons and a launcher start to save real time.

Sites that gain the most, and the ones that do not

Not every bookmark is worth turning into an app. The sites that gain the most are the ones kept open all day and checked many times: email, calendars, team chat, task trackers, AI assistants and admin dashboards. For those, a Dock icon, a Command Tab entry and notifications with a badge remove the time spent hunting for a tab.

Sites read once and closed, such as news or reference pages, gain little. A web app window has a simplified toolbar. Apple's article notes that for bookmarks or tabs, the Share button offers Open in Safari, which is a sign the web app is meant for one site, not general browsing.

A practical way to start is to look at the tabs that are open right now and pick the two or three that are always there. Turn those into apps first. Apple and Google both make deletion easy, so trying a route costs nothing.

What to change first

Pick the one site that is open in a tab all day. On macOS 14 or later, try Safari's File, then Add to Dock; if the Mac is older, or the site needs Chrome extensions or a second signed in account, build it with Kagemusha and compare.