Browser add-on already set up to work in Edge?

Last I heard, to make the browser add-on work in Edge we had to jump through a very small hoop and copy the appropriate .json file from the Chrome application support folder to the corresponding Edge folder.

In fact, I was reminded about this just yesterday in the thread about 1PX beta integration with the desktop app going away for now.

Anyway, because I moved to Edge and like it (it was that DAI with 1PX that got me to move), I went ahead and deleted 1PX and installed the browser add-on and went to copy the .json file over--but I found that the file was already in place in the Edge application support folder.

In fact, I found this to be the case on two separate Edge installations on two separate computers.

I know I didn't do that. Is that something 1PX did? Or is that new overall with 1P beta? Anyway, removing 1PX and installing the standard browser add-on worked perfectly for me with only a browser restart. I was expecting a tad more drama.

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided


  • rudyrudy

    Team Member


    I'm not sure who gave you instructions to copy the json file over, but 1Password for Mac has been maintaining that file for the release version of Edge (if you have Edge installed and have run it at least once) since 1Password for Mac 7.4.2.

  • OK, thanks.

  • rudyrudy

    Team Member


    It doesn't however maintain files for Edge Beta/Edge Dev/Edge Canary. It only maintains files for the release versions of FireFox/Chrome/Edge at the following paths:

    ~/Library/Application Support/Mozilla/NativeMessagingHosts/
    ~/Library/Application Support/Google/Chrome/NativeMessagingHosts/
    ~/Library/Application Support/Microsoft Edge/NativeMessagingHosts/

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file