Boring Websites The Blog

WebSDR: the website that lends out distant aerials

11 Nov 2026 · By the Boring Websites editors

WebSDR is a directory of internet-connected radio receivers that let several listeners tune independently. It is worth a look because a browser becomes a window onto someone else's aerial, with all the specificity that a real place brings.

In brief

  • WebSDR's project documentation describes independent tuning by simultaneous listeners.
  • The directory offers filters for region, band, frequency coverage and mobile support.
  • The University of Twente receiver provides a useful documented example of the controls.
  • This guide checked pages and instructions, not live audio reception.

A shared aerial without a shared argument

The important word in WebSDR is independent. According to the WebSDR background page, several people can use one receiver while choosing different signals. That makes the project more interesting than a remotely operated tuning knob passed from visitor to visitor. Nobody has to finish a favourite programme before the next person can move along.

The distinction changes the social shape of the visit. A shared instrument usually suggests a queue, a booking or at least a small argument about whose turn comes next. Here the documented arrangement allows private choices within shared equipment. The visitor is borrowing a point of reception rather than taking possession of the whole apparatus. It is an unusually considerate form of remote control.

As an editorial proposition, that is the site's strongest attraction. A recording presents a finished selection. A directory presents possible destinations. WebSDR joins the latter to equipment that has an existence beyond the page. Choosing a receiver is a decision about where the listening happens, even when the person listening remains at the same desk. The browser's location and the aerial's location are separate ideas.

The project's background account dates the preliminary Twente shortwave installation to Christmas Eve 2007 and the public announcement to April 2008. It also describes an original ambition involving the Dwingeloo radio telescope and reception of signals reflected from the Moon. These are the project's own historical statements, rather than dates reconstructed from a discussion thread.

That origin gives the directory a useful character: a practical instrument can become a public place without being redesigned as entertainment. The appeal is not a promised discovery on every visit. It is permission to investigate a real system without first having to own the system. A quiet or inconclusive session still belongs to the activity. The aerial has made no appointment with a dramatic ending.

The directory is a map of choices

The WebSDR directory, inspected on 11 November 2026 through its underlying page, provides band and region selectors, a mobile-support checkbox and a frequency-coverage field. Its table separates location and address from frequency range and antenna. These headings offer a better starting point than treating every receiver as an interchangeable play button.

A sensible first visit therefore begins with one question. A visitor interested in a particular part of the spectrum can start with coverage. A visitor curious about a place can start with region. A visitor holding a phone can start with the mobile filter. Trying to answer all three questions at once makes the first choice harder than it needs to be. One clear reason for choosing a receiver is enough.

The directory's own map note says positions are approximate to a few kilometres because they come from QTH locators. That is a useful restraint on interpretation. A pin provides geographic context; it is not an invitation to infer the building, room or owner behind an installation. For this kind of browsing, knowing the broad listening location is more useful than pretending the map offers a doorstep.

The interesting comparison is between two decisions, not two scores. One choice asks where reception takes place. Another asks what range the selected installation offers. Neither is inherently superior. A narrowly focused receiver can be the right destination for a narrowly focused question. An apparently larger menu is useful only when it contains something the visitor actually wants to examine.

The WebSDR FAQ says the directory updates automatically and warns that separately maintained lists quickly become stale. For a reader returning later, that makes the main directory a better bookmark than a copied inventory inside an article. The durable part of a field guide should be the method of choosing. A frozen roll call would start ageing before the paragraph finished.

There is also a small pleasure in seeing antenna information beside an address. In editorial terms, it reminds the visitor that this is not a collection of anonymous audio files. Equipment has constraints and a location. The table treats those details as part of the destination. A website that openly acknowledges its apparatus has already supplied a more interesting introduction than a large button labelled experience.

A first visit with one variable at a time

The University of Twente receiver page supplies a concrete example: its visible interface includes a frequency field, mode buttons, volume and mute controls, a filter control and waterfall settings. The page was retrievable during research. Its presence and instructions were checked; the audio stream was not exercised, so this guide makes no claim about what a listener heard that day.

The G0POT quick-start guide linked by Twente, dated November 2016, explains direct frequency entry and distinguishes dragging the tuning marker from dragging the display. These remain useful concepts for reading the inspected interface. Its older browser setup advice is not used here as a current installation recommendation.

The Twente frequency box is labelled kHz. As a simple unit conversion, 7.1 MHz equals 7100 kHz. That example explains the scale, not a promise that a station is transmitting at that number. A visitor arriving with a frequency written in MHz should reconcile the units before interpreting an unexpected result. Three decimal places can otherwise become a surprisingly long journey.

The same approach helps set a reasonable stopping point. A first session need not become a survey of the entire directory. Finding a receiver, identifying the basic controls and understanding the distinction between location and tuning already constitutes a useful visit. An instrument can invite further attention without making an unfinished person out of everyone who closes the tab.

A compact first-session checklist helps keep the controls distinct:

  • Choose a receiver whose listed range includes the frequency of interest.
  • Check whether the frequency is expressed in kHz or MHz.
  • Establish playback before adjusting several reception settings.
  • Keep the starting frequency and mode available for a return.

For a more detailed walkthrough, G0POT's linked guide supplies screenshots and examples. A reader should treat its sample frequencies as examples and its 2016 screenshots as historical illustrations, rather than expect an identical screen or a particular broadcast today. The guide is most valuable as an explanation of the relationship between controls, not a timetable of what the aerial must deliver.

What the controls do, and what they do not promise

The project FAQ addresses a particularly good beginner's confusion: selecting FM chooses a modulation method, rather than moving the receiver to the familiar 88 to 108 MHz broadcast range. The documented Twente hardware does not cover that range. A button's label and an installation's frequency coverage are different kinds of information.

That distinction is worth carrying through the whole visit. A setting changes how an available signal is approached; it cannot be assumed to extend the equipment beyond its documented range. The directory and receiver page answer different questions. Returning to the directory when coverage is wrong is more purposeful than repeatedly pressing a mode button in the hope that it doubles as transport.

The Twente page also labels a group of controls as advanced and advises leaving them alone without a reason to change them. That is useful interface writing, according to this guide's editorial reading. It gives a beginner permission to ignore something. A screen full of adjustable values does not imply a duty to adjust every value. Restraint is a legitimate operating technique.

G0POT's quick-start guide explains the waterfall as a view of signals across frequency that also preserves a short visual history. It distinguishes moving through the displayed spectrum from moving the selected tuning point. That distinction answers a practical beginner's question: moving the view and changing the listening frequency are separate actions, even when both involve dragging.

Zooming is useful for inspection rather than as a certificate of discovery. The visitor can first locate an area of interest and then examine a smaller part of the display. A mark in a display remains something to investigate; the visual pattern alone is not a responsible basis for declaring a station's identity. The next task is to relate the selected frequency and mode to what is actually received.

For the mode vocabulary, ARRL's Voice Modes overview distinguishes AM, which varies amplitude, from FM, which varies frequency, and explains single sideband as a descendant of AM with reduced bandwidth. The Twente interface separates LSB and USB. These labels belong to reception choices, so a frequency alone is an incomplete note for anyone trying to revisit a setting.

A tuning note is not an audio recording

A hypothetical note might read: Twente receiver, 7100 kHz, LSB, audio not yet established. It contains a place, a frequency, a mode and an unresolved check. It deliberately contains no station name or claim about a conversation. That example illustrates the difference between saving a configuration and documenting an observation. An accurate unfinished note is more useful than an impressive but unsupported conclusion.

On a return visit, the same note gives the visitor a concrete sequence: reopen the selected receiver, enter the recorded frequency, select the mode and reassess playback. These are proposed steps, not a successful test reported by the editors. The purpose is continuity. The visitor need not remember a complicated screen when a few plain details will preserve the question that made it interesting.

Silence deserves a diagnosis before a theory

The WebSDR FAQ's troubleshooting guidance separates browser sound problems from network problems and points to WebAudio support and audio-start restrictions. These are documented troubleshooting categories, not faults observed in this research. The FAQ contains older browser-specific instructions too, so its version lists should not be treated as a freshly tested compatibility matrix.

A proportionate response begins locally: check the device's volume, the page's mute state and any visible audio-start control. Those are reasonable diagnostic suggestions, rather than a claim that they solve every silent visit. Once basic playback has been considered, the question can become narrower. Does the page load? Is the expected interface present? Is the problem confined to this receiver?

A useful diagnostic note separates three observations: whether the page loads, whether its display appears active, and whether audio is audible. None automatically proves the others. This suggested checklist gives a question enough detail to be useful later, while avoiding a premature diagnosis. It is more informative than recording only that the radio did not work, which leaves every stage of the visit inside one unhelpful sentence.

The FAQ also discusses firewalls and proxies as possible reasons that some receiver sites work while others do not. That possibility matters for interpretation: two different outcomes in one browser need not mean the visitor has misunderstood every control. It remains a possibility from the documentation, not a diagnosis of the reader's connection. Troubleshooting works better when suggestions retain their conditional nature.

A short return visit can also begin with a saved tuning link. The project FAQ documents a tune parameter combining a frequency and mode in the address. That is a way of preserving a selection, not preserving the sound. A bookmark can carry an instruction to the receiver; it cannot make tomorrow's reception identical to today's.

Research for this article stopped short of audio playback and interaction testing. That limits the recommendations to the documented arrangement, inspected interface and a suggested visiting method. It rules out claims about sound quality, reliability or which signals are currently intelligible. The limitation is material: a functioning page and a successful listening session are two different checks, and only the former was performed here.

A public instrument with a small social footprint

The Twente page's chatbox instructions reserve discussion for the receiver's operation and received signals, and ask participants to remain civil. That local rule suits the nature of the place. The instrument is the reason people have arrived. A useful message should make sense to someone who has opened the page to investigate the same equipment.

A useful question in that setting would identify the receiver, frequency, mode and whether the issue concerns playback or interpretation. The question can then describe what remains uncertain. This is suggested visiting etiquette, not a report of community responses. Nobody was contacted for this guide, and no chat testimony has been used as evidence of reliability or reception quality.

The social restraint is part of what makes WebSDR fit a collection of small, unusual websites. It has a clear reason to exist, even though its subject can become technically deep. The site does not have to collapse that depth into a single reassuring outcome. A visitor may leave with a better question. That is a respectable result for a website, and an underappreciated one.

There is a useful family resemblance to The Bureau of Very Slow News: both invite attention that does not need an immediate payoff. The comparison is editorial rather than a claim of shared operation. WebSDR's particular contribution is access to an instrument elsewhere, while the Boring Websites network supplies other small reasons to spend time noticing something.

The most rewarding expectation is consequently a modest one. Choose a location, establish what the selected page offers, and investigate one question. A spectacular discovery would be a bonus, not a requirement written into the visit. WebSDR is interesting because its controls refer to something beyond the browser. The tab is small. The point of reception is somewhere else.

FAQ

What is WebSDR?

The WebSDR project describes internet-connected software-defined receivers with independent tuning for simultaneous listeners. Its directory helps visitors choose an installation rather than presenting one fixed station stream.

Does selecting FM find ordinary FM broadcast stations?

Not automatically. The official FAQ distinguishes modulation from frequency coverage. A receiver must cover the desired frequency range; changing the mode does not supply missing coverage.

Was live reception tested for this guide?

No. Research checked the directory, project documentation and Twente receiver page on 11 November 2026. It did not test audio playback, identify stations by listening or measure reception quality.

Where should a first visit begin?

The main WebSDR directory is the useful starting point. This guide suggests choosing one receiver for a clear reason, establishing playback and changing one setting at a time, with the project's FAQ available for documented limitations.