Skip to content


Subversion checkout URL

You can clone with
Download ZIP
WebRTC audio/video call and conferencing server.
JavaScript Java Go CSS HTML Shell Other
Failed to load latest commit information.
build Make sure to build pdf js separatly.
debian 0.24.8
doc Fixed tabs and spaces.
html Load Youtube sandbox content on demand.
m4 Use autoconf macro to compare versions.
src Fixed test by initializing default room type correctly.
static Avoid to scale up screen sharing while still keep mandatory constrain…
.gitignore Don't create config.h, it's not needed for a golang only project.
.gitmodules Get rid of submodule and directly added sleepy milestone1.
.hound.yml Point hound to correct config.
.javascript_ignore Ignore vendor javascripts in hound validation.
.jshint Merge branch 'release-0.23'
.travis.yml Also run "make test" in Travis.
COPYING Added autoconf/automake support.
ChangeLog Added autoconf/automake support.
Dockerfile The Dockerfile now even works.
Godeps Update dependencies to latest versions:
LICENSE Initial public release. Added support for (gpm)[]
NEWS Added autoconf/automake support.
README Added autoconf/automake support. Add screen sharing configuration information. Added autoconf/automake support. Added support for (gpm)[]
package.json Update jed.js to 1.1.0 Added media-src to CSP example.
spreed-webrtc-server Changed name of project to Spreed WebRTC.

Spreed WebRTC

Spreed WebRTC implements a WebRTC audio/video call and conferencing server and web client.

The latest source of Spreed WebRTC can be found on GitHub. If you are a user, just wanting a secure and private alternative for online communication make sure to check out the Spreedbox, providing a ready to use hardware with Spreed WebRTC included.

Build prerequisites

Runtime dependencies

Spreed WebRTC compiles directly to native code and has no external runtime dependencies. See here for details.


Build Status

If you got spreed-webrtc from the git repository, you will first need to run the included script to generate the configure script.

Configure does try to find all the tools on your system at the standard locations. If the dependencies are somewhere else, add the corresponding parameters to the ./configure call.

$ ./configure
$ make

Build seperately

There are several make targets available. Get Go external dependencies at least once with make get, all the other targets depend on this.

$ make get
$ make assets
$ make binary

Server startup

spreed-webrtc-server [OPTIONS]


-c="./server.conf": Configuration file.
-cpuprofile="": Write cpu profile to file.
-h=false: Show this usage information and exit.
-l="": Log file, defaults to stderr.
-memprofile="": Write memory profile to this file.
-v=false: Display version number and exit.

An example configuration file can be found in


Connect to the server URL and port with a web browser and the web client will launch.


To build styles and translations, further dependencies are required. The source tree contains already built styles and translations, so these are only required if you want to make changes.

The following Node.js modules are required, these may be installed locally by running npm install from the project root. Consult the package.json file for more details.

Styles can be found in src/styles. Translations are found in src/i18n. Each folder has its own Makefile to build the corresponding files. Check the templates for available make targets.

Running server for development

Copy the to server.conf.

Build styles, javascript and binary using make. Then run ./spreed-webrtc-server

The server runs on http://localhost:8080/ per default.

HTML changes and Go rebuilds need a server restart. Javascript and CSS reload directly.

Running for production

Spreed WebRTC should be run through a SSL frontend proxy with support for Websockets. Example configuration for Nginx can be found in doc/NGINX.txt.

In addion for real world use, one also needs a STUN/TURN server configured (with shared secret support).

See for a free open source TURN server implementation. Make sure to use a recent version (We recommend 3.2). Versions below 2.5 are not supported.

Setup Screensharing


Chrome should work out of the box.


As of Firefox >= 36 you must append the domain being used to the allowed domains to access your screen. You do this by navigating to about:config, search for 'media.getusermedia.screensharing.allowed_domains', and append the domain to the list of strings. You can edit the field simply by double clicking on it. Ensure that you follow the syntax rules of the field. If you are using an ip:port url, simply append ip to the list. Also ensure that you are using https, otherwise permission will be denied to share your screen. You do not need to restart or reload in order for it to take affect.


  1. "Fork" develop branch.
  2. Create a feature branch.
  3. Make changes.
  4. Do your commits (run make fmt and make jshint before commit).
  5. Send "pull request" for develop branch.


Spreed WebRTC uses the AGPL license, see our LICENSE file.

Something went wrong with that request. Please try again.