Supported hardware

Gqrx uses the gr-osmosdr library as input source and supports the SDR hardware listed below. (Italics) means that it the hardware has not been tested by Gqrx developers due to lack of hardware.

Funcube Dongle Pro

Funcube Dongle Pro+

Universal Software Radio Peripheral (USRP)

Osmocom rtl-sdr and rtl_tcp

Note that the rtl-sdr driver will by default transfer data from the device in large chunks. In gqrx this can have the side effect of reduced time resolution in the waterfall or slow update rate of the pandapter. If you experience this you can try adjusting the buffer size in the device string by adding buflen=xyz, i.e. if you current device string is rtl=0 the new device string becomes rtl=0,buflen=xyz.

On the other hand, you always want to use the largest possible buffers because they often give the best performance (lowest CPU load). Buffer sizes that work for me at various sample rates:

  • 250 ksps: buflen=16384
  • 1024 ksps: buflen=32768
  • 2048 ksps: buflen=65536
  • 2400 ksps: buflen=131072

HackRF Jawbreaker

RFspace SDR-IQ, SDR-IP and NetSDR



  • 0.1 – 3800 MHz transceiver from Lime Micro.
  • 12 bit ADC with up to 50 Msps.
  • Supported through SoapySDR using device string: soapy=0,driver=lime
  • List of known issues.

Nuand bladeRF


  • 100 kHz to 2 GHz receiver from SDRplay.
  • 12 bit ADC with up to 10 Msps.
  • Requires binary only drivers and gr-osmosdr compiled with “non-free” option, see gr-osmosdr web site.
  • Alternatively, one can use it through the SoapySDR backend using device string soapy=0,driver=sdrplay
  • Support through SDRplay community.

I/Q file source