WVR is a ready-to-use, open-source sample player and audio framework built around the ESP32-WROVER-B. It is more than a bare ESP32 module: its browser-based interface lets you load audio over Wi-Fi, assign notes, configure inputs and manage firmware, while GPIO and companion hardware support external controls and audio projects.
What WVR is—and what it is not
The WVR project describes itself as an Arduino-compatible, ESP32-based sample player and audio framework. The complete platform combines hardware with firmware, a browser interface, downloadable firmware binaries and related hardware projects. In other words, buying or sourcing a bare ESP32-WROVER-B does not by itself give you a WVR: the player depends on the project’s board design, software and supporting components.
WVR is aimed at playing assigned sounds from a compact embedded board and letting users control playback through physical inputs. The project also provides paths for people who want to modify its firmware rather than use it as supplied.
How WVR handles audio and control
Audio, storage and wireless
Around 2020, Hackster.io reported that WVR supports WAV, MP3, OGG and AAC, and has 8 GB of eMMC storage. The same overview estimated capacity at “over 12 hours” of 16-bit stereo audio at 44.1 kHz. Treat these as Hackster’s product description, not a guarantee for every firmware revision or for every mix of file formats and sample lengths.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitches#1 Best Overall
- FLASH: QSPI 4MB Flash / 8MB PSRAM
- SRAM :520 kB SRAM
- Size :91.10mm*32.75mm*19.90mm
- Standard :FCC/CE/TELEC/KCC/SRRC/NCC(esp32 chip)
- protocol meet bluetooth v4.2BR/EDR and BLE standard
Hackster also describes Wi-Fi, dual-mode Bluetooth, 4 MB of flash and 14 GPIO pins. Espressif’s WROVER-B datasheet documents capabilities of the underlying module, including a dual-core 32-bit LX6 processor running at up to 240 MHz, 802.11b/g/n Wi-Fi, Bluetooth 4.2 BR/EDR and LE, I2S, ADC, DAC and capacitive-touch support. Module specifications describe the chip platform; they do not mean that every capability is exposed or used identically by every WVR board or firmware build.
Physical inputs and expansion
The WVR documentation supports assigning pins to trigger or control playback. Hackster reports eight analog inputs and four capacitive-touch inputs among the board’s 14 GPIO pins. A trigger can be configured for a falling edge; with a pull-up, grounding the input can act like pressing a key. This makes the board suitable for external switches or other control circuits, subject to the pin-specific limitations below.
Set up and load samples through the browser
- Power on WVR and join its Wi-Fi network. Connect to the network named
WVRusing the password12345678. - Open the device interface. For firmware 3.9.0 and later, browse to
192.168.4.1. Instructions for older firmware refer to192.168.5.18; use the address that matches the installed version. - Upload and audition audio. Select an audio file in the browser interface and audition it there before assigning it.
- Assign notes and configure inputs. Map notes to the sounds you want and set the relevant pins’ playback behavior. For a grounded switch-style trigger, configure the pin for a falling edge and use an appropriate pull-up.
The browser workflow is also used to manage firmware. The project README describes storing up to 10 firmware images in the interface and selecting a slot to boot. That is a device-side slot feature, not an assurance that every binary is compatible with every hardware configuration.
Update firmware or develop custom code
Install a project firmware binary
Download the appropriate binary from the WVR binaries repository and upload it through the browser’s firmware menu. The README distinguishes wvr_basic for a standard WVR from wvr_usb for a board equipped with the USB MIDI host add-on. Choose based on the board’s hardware, rather than treating the two filenames as interchangeable.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Build or modify the firmware
The documented Arduino IDE setup uses ESP32 board support version 2.0.8, the WVR library, Adafruit NeoPixel, ESPAsyncWebServer and AsyncTCP. Select ESP32 Wrover Module as the board. The project also provides examples for Arduino CLI and PlatformIO.
Rank #2
- Embeds ESP32-WROVER-E, 8 MB flash, 8 MB PSRAM
- Please contact [email protected] if you have further business or technical questions.
Do not upload custom code without a working USB-to-TTL FTDI setup. The README recommends this connection: WVR D0 to adapter RX, WVR D1 to adapter TX, and GND to GND. To enter FTDI boot mode, ground D6 and the WVR boot pad before resetting the board. The FTDI adapter is useful for programming, serial logging and recovery if a browser-installed firmware build does not work as expected.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Pin limitations to account for in a build
- D6 is GPIO0, a boot-strapping pin. Holding it low during startup puts the ESP32 into bootloader mode. Avoid wiring a normal control that could unintentionally hold it low at power-on.
- D6 and D13 use ADC2. The WVR README warns that readings from these pins are inconsistent while Wi-Fi is active. Do not rely on them for stable analog control during wireless operation.
- D7–D10 are input-only and lack internal pull-ups. Add external pull-ups if the circuit needs them; these pins are not suitable where an output or internal pull-up is required.
WVR boards and related projects
The project ecosystem includes the basic WVR, Makers Board, Dev Board, USB Backpack and Thames. Their roles differ:
- Makers Board: Hackster describes it as a battery-powered audio board with audio and power jacks, a 3 W-per-channel speaker amplifier and convenient GPIO breakout. The amplifier rating is from that overview, not a measured output guarantee for every speaker or operating condition.
- Dev Board: An experimentation-oriented board for development and prototyping.
- USB Backpack: Uses a Microchip SAM D21 to add full-speed USB and USB MIDI host functionality. The
wvr_usbfirmware is intended for a WVR fitted with this add-on. - Thames: A related USB MIDI host and virtual-instrument engine in a stomp-box enclosure.
These companion boards extend or package the platform; they are not interchangeable descriptions of the basic WVR board.
Is ESP32-WROVER-B a good choice for a new design?
For an existing WVR build, the module remains the basis of the documented platform. For a new product design, lifecycle status matters: Espressif’s WROVER-B datasheet, revision 2.4 dated September 16, 2026, labels the module “Not Recommended For New Designs” (NRND). NRND is a warning to consider availability and future supply before committing to a new design; it does not, by itself, say that existing WVR hardware has stopped working or that current stock is unavailable.
If adapting WVR for a new project, assess module supply, the project’s firmware and board compatibility, and whether the required controls, storage and audio outputs are available on the hardware you plan to use. A generic ESP32 audio board or a DIY sampler may differ in storage, workflow, GPIO and MIDI expansion, amplification, toolchain support and lifecycle status; those differences need to be checked board by board rather than inferred from the ESP32 name alone.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
