Open In
Open current page or link in another browser
Make a Donation
Bitcoin Address: 1sM2BrTH8BRgt3quiASK8TmYSafutNvDo
Ether Address: 0xCf9eaAc56992e12EB61fD46342172d4EEff5C8e4
Download Links
"Open In" adds a toolbar button to your browser which allows you to open the current page in another browser of choice. A context menu item is also appended when right-clicking over links. This item allows you to open links in other browsers.


  1. What is "Open In" extension and how does it work?

    "Open In" aims to provide a simple solution to open links in another browser as simple as clicking a toolbar button. These set of extensions allow you to basically transfer any link in Chrome, Opera, and Firefox browsers to another browser of choice. Currently, link opening supports Firefox, Opera, Safari, Yandex, Microsoft edge, and Internet Explorer.


    Photo Editors:

    Media Players:

    General Purpose:

    PDF Readers:

    If you would like support for another browser or application, please leave a comment in the review section to discuss its possibility.

  2. How does "Open In" extension work?

    "Open In" uses a minimal NodeJS native client to find your browser of choice and transferring the link to this browser. After installation, upon first link opening, you will get directed to a page containing instruction on how to install the native client. This native client is mandatory for the extension to operate. Note that no extension has access to an external process (another browser in this case); hence the extension needs a native client (bridge) to call native commands. The installation process of the native client is very simple. Please follow FAQ3 for the steps.

  3. How can I install the native client?

    Open in a browser tab. Find the latest released version of the client for your OS and download it. Once the download is completed, extract the downloaded file in a local directory.

    On Windows OS, find "install.bat" file and right-click over it. Select "Run as administrator" and wait for the script to copy files

    On Linux and Mac OSs, open a terminal window at the root directory of the downloaded file and run ./ Wait for the script to copy files and print the successful message

    The installer script basically generates a manifest.json file for you and place it in two different places so that Opera, Chrome, and Firefox browsers can find the location of the native client

    The native client itself is a minimal NodeJS application. This small application is a bridge between the "Open In" and native environment. Note that by default, the script tries to use the installed NodeJS. If NodeJS is found in your system, the attached NodeJS executable is not going to get copied. If no NodeJS instance is detected, however, the packaged NodeJS executable will be used. So if you have NodeJS installed on your system, make sure it is the current version.

  4. How does the extension detect and open links in another browser?

    It really depends on your operation system. In Mac, the extension uses open -a firefox link to open link in for instance Firefox browser. In Linux, browser name along with URL of the link is called. In Windows OS, the extension looks for the browser in "%ProgramFiles%" directory and the executable is called with URL as the argument.

    If for any reason the application throws an error, you will get an alert box in Chrome and Opera. In Firefox you will get an error message in the console. To open the browser console in Firefox hit (Ctrl + Shift + J).

  5. What's new in this version?

    Please check the Logs section.

  6. Is it possible to send links to a new browser with a mouse-keyboard combination?

    As of version 0.1.4, all the "open in" extensions will support custom keyboard-mouse-click combination for opening in another browser. For instance, you can send links to Firefox browser by defining a custom keyboard-mouse-click combinations in the options page of this extension. Note that this feature is disabled by default to prevent conflict with the built-in keys. Enabling this will disable the default action (if it is defined).

  7. How can I install the native client?

    Instruction on how to install the native client will be displayed once the toolbar button is clicked. If you want to see it in action watch these two short tutorials


    Linux and Mac:

  8. How can I test my "Open in VLC" extension?

    "Open in VLC" add-on provides two UI elements. One is the page action button which is basically a toolbar button only appears on pages where it is supported. In Chrome browser, the toolbar button is always on the toolbar but it is disabled if the page is not supported. So if you are on a web page that the extension detects media, the toolbar should appear or in Chrome, the icon should be colorful. If the toolbar button is enabled, click on the toolbar button to open the media in VLC player. Example page If the toolbar button is not active, right click on the media player inside the page and there should be an item to open the media on VLC player. Note that this option is only available if URL of media can be detected. Example: open in a browser tab and right-click over the player.

  9. Can I build the native client project instead of using the releases?

    Yes, Take a look at .travis.yml file to see how to build the native client *.zip files. You can also check the log file of the actual build process (latest release of GitHub) here

  10. Open in "Internet Explorer" extension opens links in a new window instead of opening them in new tabs. How can I fix this?

    Open your IE browser then open options page (press the gear icon). Now in the general tab click on "Change how webpages are displayed in tabs" button and change "Open links from other program in" setting. Now restart your Windows for this change to take place.

  11. Is this important whether I use x86- or x64-bit system when installing the native client?

    On Windows OS we use the 32-bit version of NodeJS which works fine on both 32- and 64-bit systems. On Mac and Linux only 64-bit are supported by default. If you have a 32-bit system make sure you have NodeJS installed before installing the native client. This way the system NodeJS executable will be used.

    If you already have installed the native client, simply open the container folder and paste the right NodeJS executable there.

  12. During native client installation, when I pasted the command into "terminal" I got the message: "No such file or directory". What am I doing wrong?

    You need to switch your terminal directory to the root of the extracted folder. You can do this by using cd directory-path-here command. In Mac OS, type cd followed by a space. Now drag the folder and drop it in the terminal application and press the Enter key. To verify current directory is changed, type pwd and press the Enter key. This command prints the current directory in the terminal. Now follow the instruction one more time.

  13. What is "Open in PDF viewer" add-on and how does it work?

    "Open in PDF viewer" add-on adds a context menu item to right-click menu over links if URL has at least one PDF keyword. When this item is selected, the extension downloads the PDF file and then execute your default external PDF viewer application with a reference to the downloaded file. This way PDF files are opened directly in the external application instead of the browser's default PDF viewer. Note that most of the external PDF viewer like Adobe Acrobat Reader does not support direct URL opening. That's the reason why PDF file is downloaded before sending the link to the external application. Like other my "Open in" extensions, this one also needs the native-client wrapper. Follow the video tutorial to install the native-client before using this extension.

    This extension also supports toolbar button when the top-level URL has a PDF keyword. By pressing the toolbar button, top-level URL is sent to the external PDF viewer. Note that the extension executes the external PDF viewer only if the downloaded file is actually a PDF file. If not, based on the file mime type another default application is called (this is similar to double-clicking on a file when download is finished).

  14. Can I use this extension on Chrome OS?

    Unfortunately, not. Chrome OS does not allow installation of the native client and hence these extensions are not operational.

  15. Is it possible to automatically send links that match a pattern to an external browser?

    The new release of open-in extensions will have a new list in the options page to define hostnames that you prefer the extension to open them in the destination browser with just left-clicking on the links. Define the comma-separated list of domains and when you click on a link that its domain matches with an entry in the list, the link will be opened in the destination browser.

  16. What is the newly introduced managed storage and how can I use it?

    Managed storage is used by administrators to set the default list of hostnames and URLs to be opened by the external browser on all computers on this network. For instance for the "Open in Chrome" extension that is installed on Firefox browser to open "" hostname in Google Chrome browser, create "{086f665e-6a55-4107-9147-f9a14e72b137}.json" file with the following content and place it in the "ROOT_DIR/ManagedStorage" directory. To find the root directory for your operating system see WebExtensions/Native_manifests.

      "name": "{086f665e-6a55-4107-9147-f9a14e72b137}",
      "description": "managed storage for Open-in-Chrome extension",
      "type": "storage",
        "hosts": [""],
        "urls": []

    Note: “{086f665e-6a55-4107-9147-f9a14e72b137}” is the GUID of the extension for Firefox browser.

  17. Why the destination browser closes itself when I close my Firefox (the browser that the link is sent from)? This only happens if the link is sent from the Firefox browser and when the destination browser is not already opened.

    Firefox opens the backend NodeJS as a child process and if NodeJS is a child process, whatever executable that is initiated by this NodeJS process is still a child of the parent executable which basically is your Firefox executable. So if the destination browser is not open and Firefox initiated it, when you close your Firefox, all the child processes that belong to this process will get closed by your operating system. This issue only happens if you start a process that is not already initiated from Firefox on Windows OS. I am not sure if there is any workaround to resolve this issue.

Matched Content


Please keep reviews clean, avoid the use of improper language and do not post any personal information.HTML tags
  • <a> Defines an anchor.

    Example: <a href="">a sample link</a>

  • <pre><code> Syntax Highlighting (Supported languages: Bash, JSON, HTML, JavaScript, and CSS).

    Example: <pre><code class="javascript">var foo = 'bar';</code></pre>

  • <strong> Defines bold text
  • <blockquote> Defines a long quotation
  • <caption> Defines a table caption
  • <cite> Defines a citation
  • <em> Defines italic text
  • <p> Defines a paragraph
  • <span> Defines a section in a document
  • <s> Defines strikethrough text
  • <strike> Defines strikethrough text
  • <u> Defines underlined text
  • <br> Defines a single line break; can be used alone and don't need an ending tag


What's new in this version

Change Logs:
    Last 10 commits on GitHub

    Need help?

    If you have questions about the extension, or ideas on how to improve it, please post them on the support site. Don't forget to search through the bug reports first as most likely your question/bug report has already been reported or there is a workaround posted for it.


    Recent Blog Posts on