Komoot on the desktop: planning a ride outside the tabs

Planning a route is a desktop job and navigating it is a phone job. Komoot is built around exactly that split, which is why a search for komoot desktop tends to come from someone who has already done the planning part badly in a browser: a half finished route lost to a closed tab, a map that will not scroll because another page is eating memory, or a second account that cannot stay signed in next to the first. The answer to the literal question is short. The useful part is what follows from it.

There is no desktop application, and that is deliberate

Komoot ships mobile apps and a website. The App Store listing for the komoot app is published by komoot GmbH, is free, requires iOS 17.0 or later, and carries a 4.7 rating from 9,520 ratings in the US catalogue at version 2026.38.2. What it does not carry is the entry Apple adds when a developer allows an iPhone or iPad build to run on Apple silicon. The listing's device list runs to 131 entries and none of them is a Mac. The App Store route does not exist on a Mac, no matter how recent the machine is.

Komoot's own feature page describes the arrangement plainly under the heading about using it anywhere: start planning on desktop and continue on a favourite device, with the apps named as iOS and Android alongside Garmin and Wahoo integrations and a standalone Apple Watch app. Desktop, in that sentence, means the website. The planner at komoot.com is the desktop product.

That is not a limitation worth arguing with. A route planner wants a large screen, a precise pointer and a keyboard, and a browser gives all three. The problem is not the planner. It is that a browser also gives thirty other pages, and a planning session is long enough for that to matter.

What the web planner is actually good at

The planning tools Komoot lists are the reason people plan on a computer rather than a phone. The feature page names heatmaps showing popular paths, a trail view giving a ground level preview, detailed elevation profiles, custom waypoints, a surface type breakdown, and route difficulty information. Every one of those is easier to read on a 27 inch display than on a handset, and several are close to unusable on a small screen.

The Premium tier adds items that are also desktop shaped. Multi day route planning with suggested places to stay is listed as a Premium feature, as are personal Collections for bundling saved routes and Highlights, weather along the route, sport specific maps, 3D maps, worldwide maps and navigation, live tracking, and the komoot map on compatible Garmin devices. Planning a transalp across five days is a sit down task with reference material open, not something done at a trailhead.

Komoot offers one week of Premium free, described on its own site as having no commitment and cancellable at any time. Anyone deciding whether the multi day planner is worth a subscription can answer that question inside a single planning session, which is a reasonable way to spend the trial rather than letting it run out untouched.

Research is the other half of the desktop job

The planner is the part people search for, but it is rarely the only thing open. Komoot publishes figures for the discovery side that explain why: its own pages cite more than 8 million routes worldwide, over 850 million photos and Highlights, coverage across more than 150 countries, and a community of 45 million people. Its regional guides are built on top of that, and choosing between four candidate rides in an unfamiliar area means reading several of them.

So a real planning session is not one page. It is the planner, two or three guide pages, a weather forecast, perhaps a train timetable for the return leg, and a document where distances are being noted down. That is a workspace, and it is the reason the planner ends up buried. The tab that matters is competing with tabs that were opened in service of it.

This is worth saying because the usual advice is to close tabs, and the usual advice fails here. The other pages are not clutter. They are part of the task. What needs separating is not the research from the planner but the whole session from everything else the browser was already holding, which is a different move and a more durable one.

Komoot's feature set is also split across activities in a way that rewards keeping the window open: Discover, Plan, Navigate, Share, Contribute and Record are listed as distinct stages, and the contribute stage in particular involves adding Highlights and uploading photos after a ride. That is another desktop sitting, days after the planning one, pointed at the same site.

Where a browser tab starts costing something

A route plan is not a page view. It is a working document that gets built over twenty minutes to two hours, revised, compared against a second candidate route, and then saved. That is a long time for a page to survive in a tab strip, and three specific things go wrong.

Losing unsaved work to the wrong keystroke

Cmd+W closes the frontmost tab. On a busy browser, the frontmost tab is often not the one the hand intended, and a route under construction is exactly as easy to close as a search result. Nothing about the planner is at fault here. The container simply treats a two hour task and a throwaway page identically.

Maps compete for memory and lose

A vector map with heatmaps and a 3D view is one of the heavier things a browser renders. It wants GPU time and memory, and it is asking for them alongside every other open page. The symptom is a map that stutters while panning, or an elevation profile that takes a beat to redraw. Reducing what shares the window is the direct fix, and it is faster than any setting inside the planner.

Two accounts cannot share one browser profile

A browser profile holds one signed in session per site. Households and clubs frequently have two komoot accounts, and switching between them in one browser means signing out and back in each time, or keeping one in a private window that forgets the login on close. This is the friction that grows rather than shrinking, because it recurs every time rather than once.

The comparison that actually applies

The decision is not between an app and the web, since no app exists for a Mac. It is between leaving the planner in the tab strip and giving it a window.

	Planner in a browser tab	Planner in its own window
Reached by	Finding the tab, or reopening it	Dock icon, Spotlight, Cmd+Tab
Cmd+W risk	Closes it among many tabs	Closes one known window
Shares memory with	Every other open page	Whatever else is in that window, which is nothing
Signed in session	One per browser profile	One per window
Survives a browser restart	Only if the tab is restored	Reopened deliberately
Cost	None	None for the built in route

Nothing in the right hand column improves the route. All of it improves the odds that a planning session finishes in one sitting, which is the actual complaint behind the search.

The route macOS already provides

Since macOS Sonoma 14, Safari can save any page as a standalone application, and Apple is specific that the result is not a bookmark.

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

The path is File then Add to Dock from Safari's menu bar. The same documentation states that the web app is saved to the Applications folder of the home folder, so Spotlight finds it and Cmd+Tab reaches it directly. Its settings panel allows the name, the icon and the opening URL to be changed, which means the window can open straight onto the planner rather than the marketing homepage. The navigation controls in the toolbar can be hidden so the window stops resembling a browser, and the window can be added as a login item so it is already there at the start of the day.

For one komoot account on a Mac where Safari is already the signed in browser, that is the first thing to try and it costs nothing. Set the URL to the planner, hide the navigation controls, and the two hour session stops living next to thirty other pages.

Where the built in route runs out

The independence Apple describes cuts both ways. Because the window shares no cookies with Safari, the first launch needs a sign in, which is a one time cost that catches people expecting the window to inherit the browser session.

Two cases reach past what Safari alone covers. The first is the second account, since two Safari web apps for the same site share one underlying engine and one extension set, which works for two logins but gets awkward when the two setups genuinely differ. The second is engine choice: a heavy vector map behaves differently across rendering engines, and a window built on the Chromium browser already installed on the Mac keeps whichever extensions and rendering behaviour the site was tested against. A site to app tool covers both, with a session per window and a choice of which installed browser sits underneath. The supported services list shows the shape of the pattern across the sites people most often pull out of a tab strip, and map heavy planning tools sit in the same family as mail and calendars, which are the other things that get lost in a tab strip at exactly the wrong moment.

Two checks worth ten minutes

Before trusting the arrangement with a real trip, plan a short throwaway route in whichever window the planner ends up in, save it, quit the window outright, and reopen it. That confirms the session persists and that the saved route reached the account rather than the browser.

Then open the same route on the phone. The whole point of planning on a desktop is that the result travels, and a route that saved correctly appears in the mobile app without further action. If it does not, the problem is the account the window is signed into, not the window, and that is a five minute fix rather than a discovery made at a trailhead. The guide covers the mechanics of setting the window up once the choice is made.

What to change first

Put the komoot planner into its own window today, set its opening URL to the planner rather than the homepage, and hide the navigation controls so it stops behaving like a tab. If a second account needs to stay signed in alongside the first, or the map runs better on the Chromium browser already installed, Kagemusha is one way to get that window.