Open In
Open current page or link in another browser
Make a Donation
Please use this Bitcoin Address:1F6Ge3GHiEqyVTJKg364WqPAnV7F9WF6bg
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 by 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.

    Availble extensions:

  2. How does "Open In" extension work?

    "Open In" uses a minimal NodeJS native client for finding 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 on 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

    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 it you have NodeJS installed in your system, make sure it is 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 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. Why do I need to give the installer script administrator permission? Is there anyway to install this script without this permission?

    Windows: the installer script does two things that need admin permission. It is possible to perform these steps manually to bypass the admin permission. Basically you need to create a registry entry to let your browser know where the actual program is located. So first place the "app" folder somewhere locally and then create the registry entry as describe in here (if you are going to use this app with a single browser just create a single registry entry). If your registry is pointed to the right location for "app", the extension should be able to detect the native client.

    Mac and Linux: in Mac and Linux script needs sudo access which is equivalent to the admin permission in Windows. To bypass this permission, place the "app" folder in a local directory and follow generating and placing the JSON identifier based on your operation system in the right directory: Chrome & Opera for Linux, Firefox for Linux, Chrome and Opera for Mac, and Firefox for Mac; for more info take a look at this code. The install.js simply copies a few files to two different locations. Since copying to both locations need sudo permission, you need to manually create and copy files.

    Note that the installer script first checks to see if you have NodeJS in your PATH environment variable. If so NodeJS executable is not being copied. So if you are sure NodeJS is present in your system, there is no need to copy this file either.

  7. 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).

  8. 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:

  9. How can I test my Open in VLC extension?

    Open in VLC 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 webpage 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.

  10. 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

  11. 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.

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

    On Windows OS we use 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.



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:

    Explore more

    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.

    Open IssuesIssuesForks

    Recent Blog Posts on