A Beginner's Guide to Listening to Seattle Scanner Traffic
Published May 7, 2026 · 11 minute read
Scanner listening is one of those quietly popular hobbies that thousands of Seattleites have without ever telling anyone they do. Reporters use it. Off-duty firefighters use it. Curious neighbors who heard a siren and want to know what was happening use it. This article is a brief introduction for someone who has heard the term "scanner" but never actually tried to listen. It covers what you can listen to, how to do it for free, what is encrypted, what is legal, and where the etiquette lines are.
The short version
You can listen to most Seattle Fire dispatch traffic, most surrounding county fire traffic, and a smaller portion of Seattle Police traffic, for free, in your browser, right now, with no special hardware. The fastest path is to visit Broadcastify or OpenMHz, search for "Seattle," and click into whichever feed you want. That is the whole answer for most people. The rest of the article is the explanation of why some traffic is missing, what it sounds like, and how to make sense of it.
Why public safety radio is public
For most of the twentieth century, U.S. public safety agencies communicated over analog VHF and UHF radio frequencies that anyone with a $40 scanner from RadioShack could tune into. The frequencies were public, the broadcasts were unencrypted, and listening to them was a long-established hobby. That openness was partly a design choice — it allowed mutual-aid agencies to coordinate without interoperability problems — and partly a practical limitation of the technology at the time.
In the 2000s and 2010s, most metropolitan public-safety agencies migrated to digital trunked radio systems, often using the APCO Project 25 (P25) standard. P25 is digital but does not encrypt by default. It is more efficient with spectrum than analog and it provides better audio quality and coverage, but the traffic remains publicly listenable with the right hardware or software.
The wave that is currently changing things is encryption — specifically AES-256 encryption applied at the radio level. When a talkgroup is encrypted, the digital signal is scrambled with a key known only to authorized radios, and a scanner without that key receives only digital noise. Most agencies have begun encrypting at least some channels (typically tactical and surveillance channels). In 2026 both SPD and Seattle Fire did so: they encrypted their tactical channels while keeping their dispatch channels open to the public.
What you can hear in Seattle today, as of 2026
The current landscape is roughly:
- Seattle Fire Department — dispatch channels 4 and 5, which carry the incident type, address, and dispatched units, remain unencrypted and publicly listenable. Since August 31, 2026, Seattle Fire's other channels — 1, 2, 3, 6, 7, and 8 — have been fully encrypted, so much of the on-scene radio traffic is no longer audible.
- Seattle Police Department — dispatch channels, which show when and where incidents are occurring, remain open to scanners. Under a plan SPD announced in June 2025, channels used for tactical communications and for sensitive information such as names and building access details became encrypted in the second quarter of 2026.
- King County Sheriff's Office — partially encrypted. Some patrol channels remain in the clear; tactical and special-investigation channels are encrypted.
- Other King County fire departments — many encrypted select channels in August 2026, but many are keeping dispatch and some tactical channels unencrypted.
- Washington State Patrol — most channels unencrypted, with a few investigative channels encrypted.
- King County Metro / Sound Transit security — mostly unencrypted.
- Marine VHF — the public marine channels used by boaters and the Coast Guard, including distress channel 16, are unencrypted.
So in practical terms: you can hear the great majority of fire and EMS activity in Seattle and the surrounding cities. You can hear SPD dispatch but not its tactical channels. You can hear King County Sheriff patrols selectively. You can hear most of the smaller agencies' day-to-day work.
How to listen, for free, with no hardware
Broadcastify (broadcastify.com) is the largest aggregator of streamed scanner feeds in North America. It is community-run: volunteers operate physical scanners or software-defined radios in their homes and stream the audio to the Broadcastify servers. Anyone can listen for free. A premium subscription (a few dollars a month) buys higher audio quality, no ads, and access to the archive of past broadcasts. The premium tier is useful if you want to go back and listen to a specific incident later.
OpenMHz (openmhz.com) is a younger, free, community-run service that organizes recordings by talkgroup. Instead of a live continuous stream, OpenMHz captures each radio transmission as a discrete audio file you can play. This is the format embedded in the Seattle Breaking live feed when the operator has configured a specific system. OpenMHz coverage tends to be very good for the Pacific Northwest because the volunteer network here is active.
If you want a starting point: search Broadcastify for "King County Fire" for unified fire-dispatch traffic across the region. Search OpenMHz for King County or the Puget Sound Emergency Radio Network (PSERN), the regional system most local agencies use. Both will let you listen immediately.
If you want your own hardware
For most people, web-based listening is plenty. If you want your own scanner, the practical entry points are:
- Uniden BCD436HP or SDS100 — handheld digital scanners that can decode P25 systems out of the box. These are the gold-standard consumer scanners. They are expensive ($400 to $700) but they work.
- RTL-SDR USB dongles plus software — a $30 USB stick that, with free software (SDRTrunk, OP25, or Unitrunker), turns your computer into a full digital trunked radio scanner. Steep learning curve but the cost of entry is low.
Hardware scanners cannot decode AES-encrypted traffic. There is no consumer scanner that can. If a talkgroup is encrypted, you simply cannot listen, regardless of equipment.
What it sounds like, and how to read it
If you have never listened to public-safety radio, the first few minutes can feel impenetrable. The traffic is fast, terse, and full of acronyms. A few orientation notes:
- Most transmissions are short — under five seconds. The radio is treated as a precious resource and operators are trained to be efficient.
- Each transmission usually begins with the speaker identifying themselves and the recipient: "Engine 22, Battalion 5." That's the captain of Engine 22 calling Battalion 5.
- Standard phrases get repeated constantly. "En route" (responding), "on scene" (arrived), "in service" (available again), "out of service" (unavailable), "PD requested" (asking for police backup). Once you learn maybe fifteen of these, you'll catch the gist of 90 percent of traffic.
- The dispatcher will read the address twice. This is not a mistake — it's a deliberate redundancy to prevent any unit from getting the wrong location.
- Numbers are sometimes read in radio fashion — "one-two-three-four" instead of "twelve thirty-four" — because radio audio is noisy and individual digits are less ambiguous.
If you want a primer specifically on the Seattle Fire Department's vocabulary, the dispatch traffic uses many of the type strings discussed in our fire-response-codes article. Once you can recognize "AID Response" and "Auto Fire Alarm" by ear, the rest fills in quickly.
Is this legal?
Listening to unencrypted public-safety radio is legal in Washington state. There is no federal or state prohibition on receiving broadcasts in the clear. Recording them for personal use is also legal. Re-broadcasting or publishing them is a more complicated area under federal communications law — consult a lawyer if you are planning anything beyond personal listening.
What is illegal: using radio traffic to commit a crime (for example, listening to police channels to evade detection while committing one), and trying to get around the encryption on public-safety channels without authorization. The first one is obvious. The second one is mostly theoretical for consumer-grade equipment, since the hardware capable of decrypting AES-256 channels in real time is not commercially available.
Owning a scanner does not require a license. Operating a transmitter (i.e., a two-way radio used to broadcast) requires either an amateur radio license, a GMRS license, or operating within license-free services such as FRS. Scanners only receive — they don't transmit — so they fall outside the licensed-transmitter rules.
Etiquette and ethics
A few unwritten norms among scanner listeners:
- Do not show up at a scene because you heard about it on the scanner. Even if you mean well, you are interfering with operations. If you are a journalist, you have separate credentials and protocols. If you aren't, stay home.
- Do not contact families of incident subjects based on what you heard. The protections that exist on the data we publish on this site — no names, no identifying details — exist for good reasons. Even when names slip through in radio traffic, treat them as if you had not heard them.
- Do not post audio of cardiac arrests, suicides, or other personal medical emergencies to social media. The audio belongs to the people involved as much as to the public airwaves. Listening privately is fine. Broadcasting another person's worst moment for engagement is not.
- If you hear something you genuinely think the responding agency would want to know, call the non-emergency line, not 911. SFD non-emergency: 206-386-1400. SPD non-emergency: 206-625-5011. Do not call to ask questions about an incident you heard.
Scanner listening is a long tradition in cities like Seattle and most of the people who do it take these norms seriously. The hobby works because it is mostly invisible — listeners listen, learn about their city, and stay out of the way. If you decide to try it, that is the model to follow.