> ## Content Index
> Fetch the complete content index at: https://soundforgepro.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Surround Sound Test: Check 5.1 and 7.1 Channels
- URL: https://soundforgepro.com/surround-sound-test/
- Published: 2026-10-28T15:05:18.000Z
- Updated: 2026-10-28T15:05:18.000Z
- Description: Press a speaker and hear one channel at a time. The page reads how many output channels your browser gets, plays pink noise on each 5.1 or 7.1 position, walks around the room, and builds a 5.1 or 7.1 WAV test file for setups that only show stereo.
- Author: Erick Finn
- Tags: Audio Tools, Audio Fundamentals

A surround sound test plays one signal on one channel at a time, so you can hear whether every speaker in a 5.1 or 7.1 system answers from the spot its label promises. This page first asks your browser how many output channels the current device takes, then plays a band-limited noise burst on each channel by itself. When only two channels reach the device, it says so plainly and builds a 5.1 or 7.1 WAV test file you can play from a media player instead.

Browser tool · 5.1 and 7.1

## Check every surround channel

Sound is made on this device. No microphone, no upload. The page sees how many channels the output takes, not where your speakers stand.

!**Lower the volume first.** Tool level starts at 10%, caps at 25% and is not an SPL reading. Stop at any distortion, rattle or discomfort.

A · Channel check

Check my output 

**Not checked yet.** Press Check my output. The browser reports how many channels the current output device takes.

Layout

5.1 · 6 channels7.1 · 8 channels

**L**Ch 1 · Left*Playing* **R**Ch 2 · Right*Playing* **C**Ch 3 · Center*Playing* **LFE**Ch 4 · Subwoofer (LFE)*Playing* **SL**Ch 5 · Surround left*Playing* **SR**Ch 6 · Surround right*Playing* **7**Ch 7 · usually side left*Playing* **8**Ch 8 · usually side right*Playing* 

Your seat

Nothing playing.

Walk aroundStop

Tool level

10%

B · Test file for a media player

When the browser only gets 2 channels, make a 48 kHz, 16-bit WAV with a proper channel mask and open it in a player that sends 5.1 or 7.1 PCM to your receiver or interface. Each channel counts itself in: channel 1 clicks once, channel 3 clicks three times, the LFE thumps four times, then a noise burst plays on that channel alone. The file plays about 12 dB louder than the page at 25%, so lower the receiver first.

Make 5.1 WAV (≈12 MB)Make 7.1 WAV (≈23 MB)

Save the test file 

Ready. Press Check my output, then press a speaker or Walk around.

Pink-noise bursts band-limited to about 250 Hz–5 kHz; LFE burst below 120 Hz and 10 dB lower. Not calibrated output. Escape stops.

## How to run the surround sound test

Set up the system before the page, because a browser can only use the channels the operating system gives it. Then sit where you normally listen. A full 5.1 walk-around takes under a minute.

1. **Pick the right output.** Make the AV receiver, HDMI display or multichannel audio interface the system's default output and set its speaker layout to 5.1 or 7.1\. The Windows and macOS steps are further down.
2. **Turn the volume down.** Lower the receiver or system volume before the first press. The tool level starts at 10% and stops at 25%, and every burst fades in and out.
3. **Press Check my output.** The readout shows how many output channels the browser reports. Six or more puts the map in discrete 5.1 mode, and eight or more allows 7.1.
4. **Choose 5.1 or 7.1.** Pick the layout your speakers have. In 7.1 the buttons are numbered 1 to 8, because systems don't agree on names for the last four channels.
5. **Press each speaker from your seat.** Every burst should come from the one speaker printed on the button and nowhere else. Press the same button again, press Stop or hit Escape to end it.
6. **Run Walk around.** It steps through every channel in order for five rounds, and the line under the map names the channel that should be sounding. Point at the speaker each time; a mismatch is easy to catch by the second round.
7. **Use the test file when the count is 2.** Make the 5.1 or 7.1 WAV, save it and open it in a media player that sends multichannel PCM to your receiver or interface. Channel 1 clicks once, channel 2 twice and so on, then its noise burst plays. The file plays louder than the page, so turn the player and receiver down before you press play.

## Reading the results

A clean run is easy to recognize. Each burst comes from one speaker, the one named on the button, and the LFE burst comes from the subwoofer as a low rumble with no hiss on top. Anything else points to a short list of causes.

| What you hear                                                               | Likely cause                                                                  | Next check                                                                                      |
| --------------------------------------------------------------------------- | ----------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
| Each burst from the named speaker only                                      | Channel order and wiring match                                                | Move on to levels and distances in the receiver setup                                           |
| A burst from the wrong speaker, such as SL from the right rear              | Swapped speaker cables or swapped channel assignments                         | Check that pair at the receiver terminals; on a Mac, check the Channel menu in Audio MIDI Setup |
| Center from both front speakers, surrounds from the fronts                  | The output is stereo, so the page plays a fold-down preview                   | Read the channel count, then set the system layout to 5.1 or 7.1                                |
| The LFE button stays silent                                                 | A stereo fold-down drops the LFE, or the sub is off, unplugged or set to none | Check the readout first, then the sub's power, cable and the receiver's subwoofer setting       |
| One surround channel silent while the rest play                             | That speaker is set to none, a wire is loose, or the player down-mixed        | Play the same channel with the operating system's own test tone                                 |
| In 7.1, channels 5 and 6 come from the rear pair and 7 and 8 from the sides | The usual Windows order, not a fault                                          | Match the receiver's labels to the speaker that plays                                           |
| The file's click count doesn't match the speaker                            | The player or driver reorders channels                                        | Try another player, or set the device layout to match the file                                  |

### What the channel count doesn't tell you

The readout is the browser's `maxChannelCount`, which the [Web Audio specification](https://www.w3.org/TR/webaudio-1.1/?ref=soundforgepro.com) defines as the most channels the output device can take. It says nothing about which channel is the LFE or which order the speakers expect, a gap described in [an open issue on the Web Audio API repository](https://github.com/WebAudio/web-audio-api/issues/2408?ref=soundforgepro.com): a 6 could mean 5.1, 6.0 or six unrelated outputs. That's why the map follows the browser's standard 5.1 order, [L, R, C, LFE, SL, SR on channels 1 to 6](https://developer.mozilla.org/en-US/docs/Web/API/Web%5FAudio%5FAPI/Basic%5Fconcepts%5Fbehind%5FWeb%5FAudio%5FAPI?ref=soundforgepro.com), and why your ears make the final call.

### Why the LFE burst sounds quiet

LFE is a low-frequency effects channel, not a subwoofer feed. [ITU-R BS.775-4](https://www.itu.int/dms%5Fpubrec/itu-r/rec/bs/R-REC-BS.775-4-202212-I!!PDF-E.pdf?ref=soundforgepro.com) gives it a 20–120 Hz range, records it with a 10 dB offset and expects the playback system to add those 10 dB back. The page follows the same convention: the LFE burst sits below 120 Hz and 10 dB under the other bursts in RMS level, so a receiver that applies the usual +10 dB LFE gain brings it back level with them. A plain interface feeding an active sub adds no such gain, so there the burst stays 10 dB down.

Bass management is a separate path. The same ITU text says a subwoofer "is not related in any way to the LFE channel", and [Dolby's Atmos installation guidelines](https://www.dolby.com/siteassets/technologies/dolby-atmos/atmos-installation-guidelines-121318%5Fr3.1.pdf?ref=soundforgepro.com) ask for bass management settings that match what the speakers can reproduce. The main bursts here are high-passed at 250 Hz on purpose, so bass management has little to redirect and each burst stays on its own speaker.

A quiet sub on everyday TV isn't proof of a fault either. The ITU recommendation notes that many television and radio programs leave the LFE channel silent, and [Microsoft's multichannel audio notes](https://msdn.microsoft.com/library/Dn653308%28v=VS.85%29?ref=soundforgepro.com) warn that LFE content may not play on the speaker it was sent to. I'd check the sub with the LFE button first and judge it on films after that. To hear what it does across its range, the [bass test](https://soundforgepro.com/bass-test/) plays tones from 20 to 200 Hz.

### When a speaker sounds in the wrong place

Some direction errors are placement, not wiring. The ITU layout puts the front left and right speakers at the ends of a 60° arc, 30° either side of center, and the 5.1 surrounds anywhere from 100° to 120° from the front, with the note that precise location isn't necessary. That sector sits slightly behind your shoulders, so a surround burst that seems to come from beside you can still be in the right place.

![5.1 speaker layout around a listening seat: L channel 1 and R channel 2 at 30 degrees either side of center for a 60 degree front arc, C channel 3 at center, SL channel 5 and SR channel 6 in zones 100 to 120 degrees from center, and the LFE channel 4 subwoofer with flexible placement.](https://soundforgepro.com/content/images/2026/10/surround-sound-test-layouts.webp)

The test follows the 5.1 channel order L, R, C, LFE, SL, SR; the surrounds belong anywhere in the 100–120° zones, and the subwoofer can sit wherever bass sounds even.

The front pair is the one worth measuring. The [speaker placement calculator](https://soundforgepro.com/speaker-placement-calculator/) works out the distances for a 60° stereo triangle, the same angle the ITU layout uses. The subwoofer is the exception, since [Dolby's speaker setup guide](https://www.dolby.com/about/support/guide/dolby-atmos-speaker-setup/?ref=soundforgepro.com) points out that bass isn't directional and the sub can go almost anywhere in the room.

## Which setups play real 5.1 or 7.1

Three things have to line up: a browser that exposes the channels, an output device that takes them and a connection that carries them as separate channels. Break any one and the test falls back to two speakers.

Browsers start in stereo. Web Audio's default output is 2 channels, so a page has to ask for more, and only a device that reports 6 or 8 can grant them. Some online surround tests never ask; they pan a stereo signal between your left and right speakers to suggest positions, which can't tell you anything about a fifth or sixth speaker. This page asks for 6 or 8 discrete channels and routes each burst to one channel index.

Support for the channel count itself is old in Chromium. A [2013 Web Audio developer thread](https://lists.w3.org/Archives/Public/public-audio-dev/2013Mar/0012.html?ref=soundforgepro.com) announced that a Chrome Canary build exposes the real number of hardware channels, and [MDN's compatibility data](https://developer.mozilla.org/en-US/docs/Web/API/AudioDestinationNode/maxChannelCount?ref=soundforgepro.com) lists Chrome 27, Edge 12, Firefox 25 and Safari 14.1\. Safari 7 through 14.0 always returned 0, a bug [fixed in WebKit in September 2020](https://trac.webkit.org/changeset/266559/webkit?ref=soundforgepro.com); the tool treats a 0 as unknown and plays the stereo preview.

Firefox on a Mac is the shakiest case. A bug where [multichannel interfaces only worked on channels 1 and 2](https://bugzilla.mozilla.org/show%5Fbug.cgi?id=1559622&ref=soundforgepro.com) was closed as won't-fix in 2020, and a June 2024 comment reported it again in Firefox 127.0.2\. A related [wrong-channel bug on macOS multichannel interfaces](https://bugzilla.mozilla.org/show%5Fbug.cgi?id=1474175&ref=soundforgepro.com) was fixed for Firefox 128\. When Firefox on a Mac plays only the front pair, I'd try Chrome or Safari before touching a single cable.

On the hardware side, an AV receiver over HDMI, a multichannel USB interface or a sound card with separate analog outputs can take 6 or 8 channels when its driver offers that layout. Laptop speakers and headphones normally appear as a 2-channel output, and the readout settles the question either way. When it does say 2 and you only want to confirm a stereo pair, the [left and right speaker test](https://soundforgepro.com/left-right-speaker-test/) is the faster check.

## Set up Windows and macOS for 5.1 or 7.1

Set the speaker layout in the operating system first, then press Check again on this page. Both systems also have their own per-speaker test, which makes a useful cross-check.

### Windows: Speaker Setup

Microsoft's route to the classic Sound panel in Windows 11 is [Start, Settings, System, Sound, then More sound settings under Advanced](https://support.microsoft.com/en-us/windows/hardware/audio/fix-sound-or-audio-problems-in-windows?ref=soundforgepro.com), which opens the Playback tab. Select your receiver or interface and click Configure. Speaker Setup lists the layouts the device offers, such as 5.1 Surround or 7.1 Surround, and [How-To Geek's walkthrough](https://www.howtogeek.com/696744/how-to-test-surround-sound-speakers-on-windows-10/?ref=soundforgepro.com) shows the Test button and the clickable speaker diagram that play each channel in turn. Finish the wizard, keep the device as the default output and press Check again here.

I'd run the Windows test first and this page second. When the Windows tone comes from the right speaker but the browser burst doesn't, the wiring is fine and the problem sits between the browser and the system output. When Speaker Setup offers only Stereo, look at the connection before the browser; an ARC or optical link can't carry six PCM channels, as the soundbar section explains.

### macOS: Audio MIDI Setup

On a Mac, open the Audio MIDI Setup app, select the multichannel device and click Configure Speakers. [Apple's Audio MIDI Setup guide](https://support.apple.com/guide/audio-midi-setup/set-external-speakers-stereo-surround-sound-ams1005/mac?ref=soundforgepro.com) then has you choose a configuration such as 5.1 Surround or 7.1.4 from the Configuration menu, assign a channel to each speaker from its Channel menu, check each one with its Test button and click Apply. A home 7.1 system with three front speakers plus side and back pairs matches what that guide calls 7.1 Rear Surround, three front and four rear speakers; its 7.1 Surround is for five front speakers and two rear ones.

The Channel menu doubles as the software fix for a swapped pair. When SL plays from the right rear in every app, swap the two assignments or the two speaker cables, then run Walk around again. macOS lists 7.1.4, but this page drives eight channels at most and no height speakers.

## Soundbars, TVs and HDMI ARC

Run a computer through a TV into a soundbar or receiver and the link between them decides what you hear. HDMI Licensing says [eARC carries uncompressed 5.1 and 7.1](https://www.hdmi.org/spec2sub/enhancedaudioreturnchannel?ref=soundforgepro.com), and [Sony's BRAVIA help guide](https://helpguide.sony.net/tv/lusltn1/v1/en-003/04-04%5F04.html?ref=soundforgepro.com) lists 7.1-channel linear PCM in eARC mode. In plain ARC mode the same guide lists two-channel linear PCM, with surround only as Dolby Audio, Dolby Atmos or DTS bitstreams. The [Yamaha SR-B20A manual](https://manual.yamaha.com/av/20/srb20a/en-US/9035719947.html?ref=soundforgepro.com) shows the same split for that soundbar's TV, optical and ARC inputs: 2-channel PCM, with surround as Dolby Digital or DTS.

Web Audio works in linear PCM, and the test file is PCM too. Through ARC or optical, six channels from this page arrive as stereo, so the surround buttons can't prove anything on that chain. For a real channel check, I'd connect the computer straight to the receiver's HDMI input or use eARC from end to end. On an ARC or optical chain, the soundbar's or receiver's own test tone, where it has one, is the way to hear each speaker; a Dolby Digital or DTS test clip also works when the player passes the bitstream through untouched.

## Dolby Atmos and height speakers

Atmos layouts add a third number. Dolby's speaker setup guide counts height speakers in that third place, so 7.1.4 means seven main speakers, one subwoofer and four overhead or height speakers, and up-firing modules reflect sound off the ceiling back down to the seat. In the same guide, 7.1 is 5.1 plus a rear pair.

This page covers the ear-level bed: 5.1 or 7.1 with one LFE. Web Audio's defined layouts stop at 5.1, and the 8-channel mode is numbered rather than named for that reason. Height speakers sit outside both, so I'd check them with the receiver's own speaker test, if it has one, or with Atmos material played through a chain that decodes Atmos.

## Safe level and calibration

Start quiet. At the default 10% level the main bursts leave the page at about −35 dBFS RMS, and the 25% cap holds them near −27 dBFS RMS, before any system or receiver volume. The LFE burst sits another 10 dB lower. The WAV file ignores the tool level: its main bursts sit near −15 dBFS RMS with peaks around −3 dBFS, about 12 dB above the 25% cap and 20 dB above the default, so turn the player and receiver down before the first play. The tool level isn't an SPL reading, so the same setting can be soft on one receiver and loud on another. Stop at any distortion, cone rattle or discomfort, and leave the sub's own gain where it was.

Calibration is a separate, metered job. Dolby's Atmos installation guidelines set reference level with pink noise at −20 dBFS RMS and a target of 79–82 dB SPL, C-weighted, at the listening position, depending on room size. That's a job for a sound level meter, not a browser slider. Fix the wiring and channel order here first, then calibrate, since a calibration run on a swapped pair only measures the wrong speaker.

## How the page builds the signals

Everything is made in your browser after you press a button. Each burst is pink noise filtered to about 250 Hz–5 kHz for the main speakers and below 120 Hz for the LFE, matching the ITU LFE band. A Web Audio merger node feeds that one mono burst into one output channel, and the output runs with [discrete channel interpretation](https://www.w3.org/TR/webaudio-1.1/?ref=soundforgepro.com#ChannelInterpretation), which maps channels by index with no speaker-aware up-mix or down-mix. On a 2-channel device, the preview folds down the way MDN describes the standard 5.1-to-stereo mix: center and each surround join their side at 0.7071, and the LFE is dropped.

The WAV file uses the [WAVE\_FORMAT\_EXTENSIBLE header](https://learn.microsoft.com/en-us/windows/win32/api/mmreg/ns-mmreg-waveformatextensible?ref=soundforgepro.com), whose channel mask names the speakers and fixes the order of the interleaved channels. The 5.1 file uses [mask 0x60F](https://learn.microsoft.com/en-us/windows-hardware/drivers/ddi/ksmedia/ns-ksmedia-ksaudio%5Fchannel%5Fconfig?ref=soundforgepro.com) (FL, FR, FC, LFE, SL, SR), and the 7.1 file uses [mask 0x63F](https://learn.microsoft.com/en-us/windows-hardware/drivers/audio/channel-mask?ref=soundforgepro.com) (FL, FR, FC, LFE, BL, BR, SL, SR), which is why the back pair comes before the side pair. Both are 48 kHz and 16-bit: the 5.1 file runs 20.75 seconds at about 12 MB, the 7.1 file 29.5 seconds at about 23 MB. Players don't always agree on the names, and [FFmpeg's channel layout list](https://ffmpeg.org/ffmpeg-utils.html?ref=soundforgepro.com) shows why: its "5.1" uses back speakers, while "5.1(side)" uses side ones.

## Documented support at a glance

This summary counts the independent documents behind each point, from specifications and browser compatibility data to bug trackers and hardware manuals.

| Point                | What the documents say                                                                                    | Sources |
| -------------------- | --------------------------------------------------------------------------------------------------------- | ------- |
| Chrome               | Real hardware channel count since Chrome 27 (2013)                                                        | 2       |
| Edge                 | Channel count since Edge 12                                                                               | 1       |
| Firefox              | Channel count since Firefox 25; macOS multichannel bugs, one fixed for 128, one reported again in 127.0.2 | 3       |
| Safari               | Real count since 14.1; versions 7 to 14.0 returned 0                                                      | 2       |
| HDMI eARC            | Uncompressed 5.1 and 7.1 PCM                                                                              | 2       |
| HDMI ARC and optical | 2-channel PCM; surround only as Dolby or DTS bitstream                                                    | 2       |
| 5.1 angles           | Front pair 60° apart; surrounds 100–120° from center                                                      | 1       |
| LFE channel          | 20–120 Hz, recorded 10 dB down, restored on playback; dropped in a stereo down-mix                        | 2       |
| Reference level      | 79–82 dB SPL(C) from −20 dBFS RMS pink noise, depending on room size                                      | 1       |

My verdict: trust the readout first and your ears second. A count of 6 or 8 with every burst on its own speaker means the path from browser to speaker is wired and mapped correctly, while a count of 2 means a browser test can't prove anything about surround, and the WAV file through a multichannel player is the honest next step. Once the channel order checks out, I'd run the [speaker polarity test](https://soundforgepro.com/speaker-polarity-test/) on the front pair, and the general [speaker test](https://soundforgepro.com/speaker-test/) covers rattles and output checks on any single speaker.

## Surround sound test FAQ

### How do I test 5.1 surround sound on a PC?

Set the output device to 5.1 Surround in Windows Speaker Setup or macOS Audio MIDI Setup, then use a test that drives six separate channels. On this page, press Check my output; a count of 6 or more puts the map in discrete 5.1 mode, and each speaker button plays a noise burst on that channel alone.

### Why does a surround test only play from two speakers?

The signal is reaching the speakers as stereo. The causes worth checking are a stereo layout in the operating system, an ARC or optical link that carries only 2-channel PCM, a browser that reports 2 channels, and a test that pans a stereo signal instead of using separate channels.

### Why is my subwoofer silent during a surround test?

On a stereo output the fold-down drops the LFE channel, so the subwoofer gets nothing from the LFE button. On a real 5.1 or 7.1 output, check the sub's power and cable and whether the receiver has the subwoofer switched on. The LFE burst also plays 10 dB below the other channels in RMS level, following the ITU convention for that channel.

### Can a browser test 7.1 surround sound?

Yes, when the output device reports at least 8 channels. The 7.1 mode labels buttons by channel number because Web Audio doesn't define a 7.1 layout. In the usual Windows order channels 5 and 6 are the back pair and 7 and 8 the side pair, and a receiver may name them differently.

### Does a surround sound test work through a soundbar?

Over HDMI eARC, a soundbar or receiver can take multichannel PCM, so a browser test can reach each channel. Over plain ARC or optical, documented inputs take 2-channel PCM and carry surround only as Dolby or DTS bitstreams, so a browser test arrives as stereo.

### How do I fix swapped surround speakers?

Swap the two speaker cables at the receiver, or on a Mac swap the two channel assignments in Audio MIDI Setup, then run Walk around again. A swap that shows up with every source is wiring; a swap in only one player points to that player's channel order.

### Does this test check Dolby Atmos height speakers?

No. It drives the ear-level 5.1 or 7.1 bed with one LFE. Height speakers need Atmos material and a playback chain that decodes it, or the receiver's own speaker test.