A Kobo desktop app on a Mac: your library in its own window

Forum threads about the Kobo desktop app on a Mac have been asking the same question for years, and the thread titles usually end in a question mark. Discontinued? Possibly discontinued? Kobo's own help pages give an answer, and it is more interesting than either yes or no. The application still exists and still installs on a Mac. What has changed is what Kobo thinks it is for, and for a large group of readers the recommended route is now something else entirely.

What Kobo publishes for a computer today

The help article describing the application opens with a plain definition.

Kobo Desktop is a free app that lets you read and buy eBooks using your PC or Mac. Source: help.kobo.com

The same article lists four things it does: manage ebooks on a Kobo eReader, read books purchased from Kobo, shop for books on the computer, and sync the eReader. It also lists the constraints, and the constraints are where the confusion in those forum threads comes from. Three of them will decide the answer for most readers before any download starts.

The hardware exclusions come first. The help article states that Kobo Desktop is not compatible with the Kobo Libra Colour, the Kobo Clara Colour, or the Kobo Clara BW. Those are current devices, not museum pieces, so an owner of a recent Kobo who goes looking for desktop software to manage it is looking for something that will not manage it.

The second is geographic. The same page states that Kobo Desktop is no longer available for users in Europe. A European reader following a tutorial written elsewhere will not find the download, and nothing is wrong with the browser or the account.

The third is the format gap: the article states that Kobo Desktop does not support audiobooks. A library that is half audiobooks is half invisible to it.

For anyone past those three, the Mac requirement is undemanding. The article gives the minimum for Mac users as OS X 10.9, Mavericks, or later, which covers essentially any Mac still in use. Linux and older Windows releases are excluded, and so are Chromebooks.

Kobo now leads with the browser

The install instructions are the clearest signal of how Kobo's own thinking has moved. The article about installing on a PC or Mac does not open with a download link. It opens with an alternative.

You can now enjoy your Kobo eBooks directly in your web browser using Kobo Web Reader - no download required. Source: help.kobo.com

The download instructions follow, introduced with a condition rather than a recommendation: if an older Kobo eReader needs setting up or updating, the application is still there. The same page describes the Web Reader route in four steps, which amount to signing in with a Kobo account, opening the section the page labels as the book list, and clicking a cover.

That reframing is the actual answer to the forum question. Kobo Desktop has not been discontinued. It has been narrowed into a utility for eReader owners with specific devices, and reading on a computer has been handed to the browser. Readers who never owned a Kobo eReader and bought their books to read on a laptop are, by Kobo's own instructions, browser readers now.

Choosing between them takes four questions

	Kobo Desktop	Kobo Web Reader
Install required	Yes	No
Reading ebooks	Yes	Yes
Audiobooks	Not supported	Handled separately by Kobo's apps
Sync a Kobo eReader	Yes	No
Transfer files by USB cable	Yes	No
Libra Colour, Clara Colour, Clara BW	Not compatible	Not applicable
Available in Europe	No	Yes
Mac requirement	OS X 10.9 or later	A current browser

The four questions that resolve it: is there a Kobo eReader in the house, and which model, is the reader in Europe, and does the library include audiobooks. Two of those four push toward the browser regardless of preference, and the eReader question is the only one that genuinely requires the application.

It is worth noting what the table does not say. Neither column is a reduced version of the other. Kobo Desktop can do things no browser page can, because syncing a device over USB is not something a web page is allowed to attempt. The Web Reader can be reached from a machine where nothing can be installed. These are different tools that happen to open the same library.

Why download catalogues do not settle the question

Part of the reason the forum threads never resolve is that the evidence people bring to them comes from the wrong place. Search results for a Kobo desktop app on a Mac are full of third party software catalogues, each listing a version number and a release date, and each of those numbers gets quoted in threads as proof that the application is alive or dead.

Those catalogues mirror installers. A version number on a mirror says when that mirror last refreshed its copy, which is a fact about the catalogue rather than a fact about Kobo. A stale listing looks like abandonment. A recently refreshed listing looks like active development. Neither one can tell a reader whether the application will work with the eReader on the desk, whether it is offered in their region, or whether it handles the audiobooks in their library, and those are the three things that actually decide the outcome.

Kobo's own help pages carry all three answers, and they carry them in the same paragraphs as the download links. That is the source worth checking before installing anything, not because mirrors are untrustworthy but because a mirror cannot know which region the reader is in.

There is a second reason to start at the help pages. Kobo documents a separate route for public library loans, filed under Adobe Digital Editions and Libby rather than under the desktop application, so a reader whose books come from a library is following a different set of instructions from the start. Beginning at a download page hides that fork entirely, and a reader can spend an evening troubleshooting an application that was never the right tool for borrowed books.

The reading window is the part left unsolved

A reader who lands on the Web Reader has the library, the books, and the reading settings. What is missing is not a feature. It is the container.

An ebook is the longest thing most people keep open in a browser. A chapter runs half an hour, a novel runs a week, and for that whole time the page is meant to sit undisturbed, holding a position. Browsers are built for the opposite pattern: many short lived pages, most of them closed within minutes, with the front tab treated as the only one that matters.

One keystroke closes it

Cmd+W shuts the frontmost tab without asking. In a strip of twenty tabs the frontmost is often not the intended one. Kobo syncs reading position, so the book survives, but the window and its arrangement do not.

It becomes hard to find

Twenty tabs deep, a book is a few pixels of cover art. Returning to it means scanning the strip or typing the address again, which is an odd amount of effort to reach something already open.

Nothing separates reading from everything else

The point of a reading session is that attention settles. A window holding a novel, a work thread and a shopping cart is a window that invites attention to leave. That is the friction a separate window actually removes, and no amount of reading settings inside the book will touch it.

The route macOS already provides

Apple added a documented way to give any page its own application, and it costs nothing.

Starting with macOS Sonoma 14, you can use Safari to save any webpage as a web app, so that you can use it independently of Safari. Source: support.apple.com

The path in Safari is File then Add to Dock. Apple's page states that the result is saved to the Applications folder of the user's home folder and can be opened from the Dock or from Spotlight, which makes it a real item on disk rather than a decorated bookmark.

Two details in that documentation matter for a reading window. The first is separation.

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

Its own cookie store means its own Kobo sign-in, held apart from whatever the browser is signed in to. For a household where two people buy books on two accounts, that is the whole mechanism.

The second is the settings panel. Apple lists what can be adjusted: the application name, the URL the window opens, the icon, whether the toolbar shows navigation controls, and whether the title bar takes its colour from the site. Turning navigation controls off is the change worth making, because a window whose only job is to show a page of text has no use for a back button. Apple also notes that a web app can be added as a login item so it opens at sign-in, which is the difference between a habit and a thing to remember.

Where the free route stops

For one Kobo account on a Mac that already keeps Safari signed in, Add to Dock is the first thing to try and frequently the last thing needed. It runs out in predictable places.

It is Safari only, so a Kobo session living in Chrome or Firefox has to be established again somewhere new. It produces one window per URL, so a second account means a second web app built and named and given an icon by hand. The behaviour of the window is limited to the switches Apple exposes, and the icon is whatever image gets pointed at.

A site to app tool covers the ground past that line: a window with its own session regardless of which browser holds the main one, a second window for a second account on the same host, a prepared icon rather than a screenshot, and control over how the window behaves. The supported services list shows the same pattern applied across the sites people most often pull out of a tab strip, and reading sites sit there alongside mail and chat for the same reason, since all three are long sessions that nobody wants to hunt for.

What to change first

Check the three constraints on Kobo's help page against the actual situation: the eReader model, the region, and whether the library includes audiobooks. If the browser is the route, open the Web Reader in Safari, choose File then Add to Dock, and turn off the navigation controls so the window stops looking like a browser. Where a second account or a non-Safari session is in the way, Kagemusha handles the same idea with the session separation built in.