← Back to FAQ overview

macOS & Linux

Setting up the browser add-on on macOS (as of version 19)

This guide describes how to set up the browser add-on for the macOS client of Password Depot as of version 19. This configuration is not required for the Windows version. The macOS client communicates with the browser add-on via Native Messaging (NMH, Native Messaging Host); you set up this connection once before first use, in three steps. Important: The browser add-on and the macOS client must match – use the add-on for version 19 together with a macOS client version 19 or later.

Step 1: Install the add-on in your browser

Install the Password Depot add-on from your browser's extension store. The add-ons are available for Chrome, Microsoft Edge, and Firefox; the installation works the same way as on Windows.

Step 2: Save the Native Messaging manifest

  1. In the macOS client, open Help → Add-ons → Save Native Messaging Manifest.

  2. Select the browser for which you want to install the manifest. You can install the manifest for multiple browsers, but only for one browser at a time – repeat the process for each browser.

  3. The add-on ID is usually prefilled – do not change it.

  4. Click Save. When the file save dialog appears, click Save again without changing the file name or path.

Important – additional step for Firefox: The "NativeMessagingHosts" folder is not created automatically for the Firefox add-on and must be created manually before saving the manifest – in one of the following locations:

  • System-wide (all users): /Library/Application Support/Mozilla/NativeMessagingHosts/

  • Per user (current user only): ~/Library/Application Support/Mozilla/NativeMessagingHosts/

(The ~ character represents your personal home folder.)

Step 3: Register the XPC service

Open Password Depot → Settings → "Browser" tab and click Register next to XPC Service status. Make sure the status changes to "Registered".

The browser add-on is then fully set up, and you can use your credentials directly in the browser.

Note: The add-on and client versions must match. The browser stores update the add-on automatically. During the generation change to version 19 (new Native Messaging interface), the add-on could therefore temporarily be newer than the installed macOS client – the connection failed until the matching client update for macOS became available. If the add-on connection suddenly stops working, first check whether an update of the macOS client is available and install it. Then repeat steps 2 and 3 if necessary.

Related topics:

Problem not solved?

Our support team is happy to help – report a bug, suggest an improvement, or schedule an appointment.

Contact support