|82823d5da7||9 months ago|
|.github||11 months ago|
|app||9 months ago|
|resources||2 years ago|
|.eslintignore||2 years ago|
|.eslintrc.js||5 years ago|
|.flowconfig||1 year ago|
|.gitignore||5 years ago|
|.npmrc||2 years ago|
|.nvmrc||2 years ago|
|LICENSE||7 years ago|
|README.md||10 months ago|
|SECURITY.md||3 years ago|
|entitlements.mac.plist||3 years ago|
|main.js||9 months ago|
|notarize.js||2 years ago|
|package-lock.json||9 months ago|
|package.json||9 months ago|
|screenshot.png||5 years ago|
|webpack.main.js||1 year ago|
|webpack.renderer.js||1 year ago|
Jitsi Meet Electron
Desktop application for Jitsi Meet built with Electron.
- End-to-End Encryption support (BETA)
- Works with any Jitsi Meet deployment
- Builtin auto-updates
- ~Remote control~ (currently disabled due to security issues)
- Always-On-Top window
- Support for deeplinks such as
myroomon the configured Jitsi instance) or
myroomon the Jitsi instance running on
Download our latest release and you're off to the races!
|Windows||macOS||GNU/Linux (AppImage)||GNU/Linux (Deb)|
NOTE: The GNU/LInux builds are 64-bit only.
For macOS user, you can install the application using the following command:
brew install --cask jitsi-meet
Using it with your own Jitsi Meet installation
⚠️ The following additional HTTP headers are known to break the Electron App:
Content-Security-Policy "frame-ancestors [looks like any value is bad]"; X-Frame-Options "DENY"; X-Frame-Options "sameorigin";
A working Content Security Policy looks like that:
Content-Security-Policy "img-src 'self' 'unsafe-inline' data:; script-src 'self' 'unsafe-inline' 'wasm-eval'; style-src 'self' 'unsafe-inline'; font-src 'self'; object-src 'none'; base-uri 'self'; form-action 'none';";
If you want to hack on this project, here is how you do it.
Show building instructions
Install Node.js 16 first (or if you use nvm, switch to Node.js 16 by running
Extra dependencies for Windows
npm install --global --production windows-build-tools
Extra dependencies for GNU/Linux
X11, PNG and zlib development packages are necessary. On Debian-like systems then can be installed as follows:
sudo apt install libx11-dev zlib1g-dev libpng-dev libxtst-dev
Install all required packages:
Starting in development mode
The debugger tools are available when running in dev mode and can be activated with keyboard shortcuts as defined here https://github.com/sindresorhus/electron-debug#features.
It can also be displayed automatically from the
SHOW_DEV_TOOLS environment variable such as:
SHOW_DEV_TOOLS=true npm start
or from the application
--show-dev-tools command line flag.
Building the production distribution
npm run dist
Working with jitsi-meet-electron-sdk
jitsi-meet-electron-sdk is a helper package which implements many features such as remote control and the always-on-top window. If new features are to be added / tested, running with a local version of these utils is very handy, here is how to do that.
By default the @jitsi/electron-sdk is build from npm. The default dependency path in package.json is:
To work with local copy you must change the path to:
To build the project you must force it to take the sources as
npm update will
not do it.
npm install @jitsi/electron-sdk --force
NOTE: Also check the jitsi-meet-electron-sdk README to see how to configure your environment.
- Create release branch:
git checkout -b release-1-2-3, replacing 1-2-3 with the desired release version
- Increment the version:
npm version patch, replacing
- Push release branch to github:
git push -u origin release-1-2-3
- Create PR:
gh pr create
- Once PR is reviewed and ready to merge, create draft Github release:
gh release create v1.2.3 --draft --title 1.2.3, replacing v1.2.3 and 1.2.3 with the desired release version
- Merge PR
- Github action will build binaries and attach to the draft release
- Test binaries from draft release
- If all tests are fine, publish draft release
A warning will show up mentioning the app is unsigned upon first install. This is expected.
On macOS Catalina a warning will be displayed on first install. The app won't open unless "open" is pressed. This dialog is only shown once.
If after downloading it, you can't execute the file directly, try running
chmod u+x ./jitsi-meet-x86_64.AppImage
On Ubuntu 22.04 the AppImage will fail with a fuse error (as AppImage uses libfuse2, while 22.04 already comes with libfuse3 by default):
dlopen(): error loading libfuse.so.2
To fix this, install libfuse2 as follows:
sudo apt install libfuse2
Under wayland, experimental native wayland support can be enabled with the command-line switch
--ozone-platform-hint set to
Note that screensharing is currently not supported under wayland, eg. the permissions prompt may loop endlessly.
In case you experience a blank page after jitsi server upgrades, try removing the local cache files:
rm -rf ~/.config/Jitsi\ Meet/
NOTE for old GNU/Linux distributions
You might get the following error:
FATAL:nss_util.cc(632)] NSS_VersionCheck("3.26") failed. NSS >= 3.26 is required. Please upgrade to the latest NSS, and if you still get this error, contact your distribution maintainer.
If you do, please install NSS (example for Debian / Ubuntu):
sudo apt-get install libnss3
The json files are for all the strings inside the application and can be translated here.
New translations require the addition of a line in index.js.
Localize desktop file on linux requires the addition of a line in package.json.
Please search for
Comment[hu] as an example to help add your translation of the English string
Jitsi Meet Desktop App for your language.
Apache 2. See the LICENSE file.
Jitsi is built by a large community of developers, if you want to participate, please join community forum.