OpenWebRX-Plus
Browser-based, multi-user software-defined radio receiver with a live spectrum and waterfall, browser audio, scanning, recording, analog modes, digital…
Platform availability
Available on 1 of 10 platforms
- Unraid
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?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). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
70/100 Good
- Maintained
- 100last commit 22 days ago
- Popular
- 56649 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- 404 GB minimum RAM, runs on ARM
- Security check
- 85no serious findings, tests
Availability: platform listings confirmed today, links checked 43 days ago
- GitHub stars
- 649
- Open issues
- 4
- Last commit
- 2026-10-30
- Latest release
- 1.2.117
- License
- AGPL-3.0
- Activity
- declining
Checked 19 days ago - source: GitHub (luarvique/openwebrx)
Resources & Compatibility
Minimum requirements: 4 GB RAM. ARM (e.g. Raspberry Pi) is supported.
Checked 54 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 54 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
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
- Any experience with OpenWebRX? : r/RTLSDR - Reddit (reddit)
- OpenWebRX+ | TXITY - Transmit legally for free (forum)
- OpenWebRX - Reddit (reddit)
- Installing and Running OpenWebRX+ - RadioReference.com Forums (forum)
- OpenWebRX+ on Pi 400 and LAN - RadioReference.com Forums (forum)
Collected 53 days ago - public community threads