← Directory

OpenWebRX-Plus

Browser-based, multi-user software-defined radio receiver with a live spectrum and waterfall, browser audio, scanning, recording, analog modes, digital…

  • Media Applications
  • Network Services
  • Tools & Utilities
Browser-based, multi-user software-defined radio receiver with a live spectrum and waterfall, browser audio, scanning, recording, analog modes, digital decoders, and SoftMBE digital voice support.

Platform availability

Available on 1 of 6 install platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)

Also on Docker Hub and GitHub

Health score

72/100 Good

Maintained
100last commit 7 days ago
Popular
56633 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

How is this calculated?

A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). Factors without data are left out and the rest are rescaled.

Availability: platform listings confirmed today

GitHub stars
633
Open issues
1
Last commit
2026-09-28
Latest release
1.2.117
License
AGPL-3.0
Activity
steady

Checked 7 days ago - source: GitHub (luarvique/openwebrx)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 7 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Use port 8073 for the web app OpenWebRX+ listens on port 8073 by default, including the WebSocket connection used for live SDR data and control. If that port is blocked by your router or host firewall, the browser app may fail to load or lose real-time audio and spectrum data. source
  • SSL files live in /etc/openwebrx If you want HTTPS, put key.pem and cert.pem in /etc/openwebrx before starting OpenWebRX+ so the server can automatically switch to https. Without the files in that exact place, the server will not switch to HTTPS and users will need to trust a self-signed or HTTP site. source
  • Enable frequency changes in config If a client or app needs to change the center frequency over the API, set allow_center_freq_changes = True in the config before starting the server. Without that setting, frequency-change commands can be ignored even though the rest of the connection works. source

Fetched 7 days ago - each note links to its source

Alternatives (1)

  • sdrangelove - A graphical application for showing the Fast Fourier Transformation (FFT) as graph and waterfall diagram of the radio spectrum retrieved by…

Checked 4 days ago - source: AlternativeTo

Common questions

Which port must be open for the OpenWebRX+ browser app?

OpenWebRX+ listens on port 8073 by default, including the WebSocket used for live SDR data and control. If that port is blocked by the router or host firewall, the browser app may fail to load or lose real-time audio and spectrum data.

Where should the certificate files be placed to enable HTTPS?

Put key.pem and cert.pem in /etc/openwebrx before starting OpenWebRX+ so the server can automatically switch to HTTPS. Without those files in that location, the server will not switch to HTTPS.

How do I allow a client or app to change the center frequency through the API?

Set allow_center_freq_changes = True in the config before starting the server. Without that setting, frequency-change commands can be ignored even though the rest of the connection works.

Answers sourced from context7.com

Community

Collected 6 days ago - public community threads