Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Screen sharing is available for Chrome and Firefox. To share screen in Chrome before 73 the extension need to build and install, in the latest Chrome versions (73 and newer), Firefox and Firefox Safari screen can be shared without extension. Today, it is not recommended to use extension.


Extension for Google Chrome with publication in Chrome Store

Source code for the extension is available by the following link:

Chrome Screen Sharing Extension

Create a Google account

1. Go to and click ‘Sign in’ button

2. On the ‘Sign in’ page, click ‘Create account’ link

3. ‘Create your Google Account’ page will be opened
Fill the required fields and click ‘Next step’ button to create the account.

Register as Chrome Web Store Developer

1. Sign in to Chrome Developer Dashboard with the created Google account
2. Pay a one-time $5 developer signup fee

Customization for your domain

Follow the procedures described below to use the extensions with your domain.
Edit manifest file manifest.json of the Chrome extension.


  • name
  • author
  • description
  • homepage_url
  • under "externally_connectable":"matches" change to your domain

Save your icons for the extension to chrome-extension directory and edit the file names in "icons" and "web_accessible_resources". (For more information, see Manifest - Icons and Supplying Images.)

Package the extension

Package files from chrome-extension folder into ZIP archive.

Publish the extension

1. Sign in to Chrome Developer Dashboard
2. In the dashboard, click ‘Add new item’ button

3. Accept the developer agreement

4. On the ‘Upload’ page, choose the file and click ‘Upload’ button

5. When the extension is uploaded, the page for editing the extension draft will be opened
Edit the extension as required and click ‘Save draft and return to dashboard’ button at the bottom of the page.

6. The extension will appear in the developer dashboard
Click ‘Publish’ link to publish the extension.

A published extension will have status ‘Published’ as on the image below.

For more information, see Chrome Web Store Publishing Tutorial.

Extension Inline Installation

Extension installation can be initiated by clicking a link on the Screen Sharing client page.
Note that the extension to be installed should be customized, published and approved before inline installation can be used.

Follow the procedures described below to use the client with your extensions.

1. When publishing, select ‘Inline Install’ option

2. Verify and add website with your domain to the extension
- Click ‘Add a New Site’

- Google Search Console page will open in a new tab
Enter URL with your domain.

- A page with the instruction for the site verification will open
Follow the procedure steps and click ‘Verify’ button.

- If the verification is passed, a page confirming successful verification will be opened

- The website will appear in the list in the extension options and the extension can be associated with the site

Configuring the client

Edit  Screen-sharing.html and Screen-sharing.js

  • In Screen-sharing.html the chrome-webstore-item parameter should point to your extension in the Chrome Store
  • In Screen-sharing.js replace the value of the chromeScreenSharingExtensionId parameter to the ID of your extension

To get the ID of the extension, click ‘More info’ of this extension in Chrome Developer Dashboard.

Media source parameters

To configure screen media source parameters, use parameters of the Configuration object passed to the init() method upon initializing of the Flashphoner API instance.

Code Block
var f = Flashphoner.getInstance();
var configuration = new Configuration();
configuration.screenSharingVideoWidth = 1920;
configuration.screenSharingVideoHeight = 1080;
configuration.screenSharingVideoFps = 10;

Parameter list




Screen media source width


Screen media source height


Screen media source framerate

These parameters set marginal values of resolution and framerate (FPS). For instance, screenSharingVideoWidth = 1080 means the width of the source video cannot be more than 1080 pixels, but can be less. (i.e. when sending a stream of an app window that has the width of 720 pixels).

System sound capture in Chrome browser

In Chrome browser, there is ability to translate audio stream from system sound source while capturing a screen. The feature is useful in screencasting, for example. To capture system sound, set "Share audio" option in Chrome extension dialog window while choosing streaming source window or browser tab:

Chrome extension code:

Code Block
        callback({sourceId: sourceId, systemSoundAccess: opts.canRequestAudioTrack});

Capture source (screen or window) management in Firefox browser

In Firefox browser, all the screen or some program window can be chosen as video stream source with parameter


Code Block
themeRDark = "screen";
    if (Browser.isFirefox()){ = $('#mediaSource').val();
        name: streamName,
        display: localVideo,
        constraints: constraints

Source selection interface example:

Program window capture

Screen capture

Screen sharing without extension

Firefox browser

Firefox browser does not use extension to share screen

Chromium based browsers

Since Chrome 73 and Flashphoner WebSDK screen sharing is possible without extension. To do this parameter should be passed when stream is created


Code Block
 if ($("#woChromeExtension").prop('checked')) { = true;

Safari browser in MacOS

Since Safari 13 and Flashphoner WebSDK screen sharing is possible without extension. To do this parameter should be passed when stream is created


Code Block
 if ($("#woChromeExtension").prop('checked') || Browser.isSafari()) { = true;

Known limits

1. In Chrome browser, picture resolution and FPS are set by source dimensions (screen, windows or browser tab) and by real picture updating speed, not by constraints/ This issue is fixed since Flashphoner WebSDK build

2. System sound capture only works starting from Crome 74

Code of the example

This example uses Flashphoner extensions for work with domain * For work with your domain, build up and publish your extensions as described above.


Code Block
<link rel="chrome-webstore-item" href="">


Analyzing the code

1. Initialization of the API.