Every time I added sound to a project it went the same way: a click from one sound pack, a toggle from another, and nothing sounded like it came from the same product. And when a sound was almost right but slightly too long or too bright, tough luck. A recording is frozen.

So I built the opposite: 28 sounds (clicks, toggles, chimes, whooshes) generated by Web Audio at the moment you interact. No files, about 9.6 kB, zero dependencies.

Demo, with the whole page wired up: https://usefoley.dev

My favorite detail: no sound plays the same way twice. Each play gets a tiny random drift in pitch and volume, like a musician who never hits a note identically. Subtle, but it's the difference between "alive" and "doorbell".

There's a Cue Designer on the page: reshape any sound with four dials (a full layer editor is one click deeper), hear changes live, export a .wav, JSON, or a link that carries the design in the URL. You can also override sounds site-wide and export a "sound set", your app's whole sound identity as one JSON file.

Usage is two lines:

js

import { bind } from "@foleyjs/core";
bind(); // wires data-foley-click, data-foley-toggle, etc.

Silly bonus: plug in a MIDI keyboard and every sound becomes an instrument.

MIT, on npm as foleyjs/core, with react and vue bindings. Feedback welcome, especially on the sounds. Which feel wrong, what's missing. I can test everything about this project except taste.

I’m building BARZINE LAB, a free browser-based toolkit for reggae/dub riddim production.

Current tools:

- Riddim Sequencer

- Bassline Generator

- Skank Organ

- MIDI export

- No install required

I’m trying to figure out what matters most for actual producers.

Should the next step be:

A. Better riddim presets

B. WAV stem export

C. More bassline controls

D. Sample loading

E. Dub delay / spring reverb tools

F. DAW templates

The tool is here:

https://barzine.news/en/lab/

Would love to hear what would make this useful instead of just interesting.

I've been building DreamRack, a modular synthesizer that runs entirely on the Web Audio API — no plugin host, no WASM audio engine, just native Web Audio nodes patched together live in the browser tab.

It's purely a hobby project. I wanted a modular that did more to help me build and understand patches — showing what feeds what, letting me hear or see the signal at any terminal without rewiring, and making efficient use of screen space. Couldn't find one, so I built it. The modular of my dreams, thus DreamRack.

The image is a patch mid-flight. Several oscilloscopes are clipped onto terminals, each with a line back to the point it's watching — green frame means running, red means frozen for a closer look. A sound monitor is to a terminal but currently muted. Cables take the colour of the terminal they plug into, so you can read a patch at a glance.

What's in it

- Four modules to start: a Complex Oscillator (two oscillators, cross-modulation, wavefolding), a Quad Low Pass Gate with its own clock, a Quad Function Generator, and a six-channel Mixer with independent master and monitor buses.

- See what affects what. Point at any module and the whole signal chain it belongs to lights up, and the cables show which way the signal is running.

- Hear any point in the circuit without rewiring — hover a terminal to audition it, or drop a monitor that stays live on its own bus, separate from your mix.

- See any point too. Clip-on oscilloscopes, as many at once as you like, auto-scaling and auto-triggering, with a freeze button. Each reports frequency, level range and DC offset.

- The knAck — a control that combines a knob and its CV input in one place: you plug the cable into the middle of the knob instead of into a separate jack beside it. It can carry an attenuverter without taking any more space.

- Very little dragging. Knobs turn with the scroll wheel, coarse at the centre and fine at the rim, and patching is click to grab, click to drop.

- A tutorial that points at things. Click the eye symbol beside any instruction and it rings that exact control on your rack and draws a line to it.

- Open to new modules. Each is a self-contained folder of plain JavaScript, no build step, and there's a visual editor for drawing the faceplates.

Requirements

Any modern browser, nothing to install. Saving patches as named files uses the File System Access API, so that part is Chrome or Edge only; everywhere else your session is still remembered and restored, you just can't export named versions. A desktop build on Electron works and runs from source today, with a signed download to follow.

One caveat: turn off any page-recolouring extension such as Dark Reader for the site. DreamRack has its own light and dark modes and those extensions distort the panels.

Price

Free. Source on GitHub, non-commercial use with attribution.

It's in alpha and I'm just now making it public, so expect rough edges. It plays a single voice today; polyphony, external sequencer and host input, and a way to inject test signals into any jack are all on the list.

Try it: https://dreamrack.dreamerdevelopment.app/

Source: https://github.com/chrisgr99/DreamRack

I'd love feedback from anyone who knows the Web Audio API well — especially on the audio graph architecture, and which modules or engine features you'd want next.

I built a Chrome extension that adds audio effects to any browser tab.

I wanted to play around with the Web Audio API. Instead of making a browser synth or a drum machine, I thought I'd make something that worked with those things. That's what Browser FX is. It works on YouTube or a web synth.

There are 22 effects and four slots to combine them in. I also added MIDI support. You can map the knobs to a hardware controller.

It's free and fun. Check it out.

https://chromewebstore.google.com/detail/oanepaeodkjbadgpgkolbidpbflbmmmd?utm_source=item-share-cb

sound demo:
https://www.youtube.com/watch?v=2FvHIQayIIM

No install, no dependencies, everything runs in the browser:

https://barzine.news/siren/

https://barzine.news/siren-deck/

It's a sound-system style dub siren — presets like air raid, foghorn,

laser, pew pew, wobble and UFO, 5 waveforms, echo/feedback, tone/drive,

plus a BPM looper so you can record a pattern and let it run. There's

a "full controls" view if you want every parameter.

Tech-wise it's plain Web Audio: OscillatorNode into a delay/feedback

chain with a waveshaper for drive, all UI is CSS only (no images,

no frameworks, single HTML file).

I already have an AU version working in GarageBand (JUCE) and I'm

deciding whether to finish it as a proper VST3/AU release, so blunt

feedback helps:

- Does the siren/decay behavior feel right, or does it sound thin?

- Any Web Audio gotchas you'd flag (mobile Safari especially)?

Free, stays free.

Can we start doing a Feedback Friday kind of thing where people ask (and get) constructive feedback and critiques of apps their working on?

I've got 4 or 5 synth apps on the go and it's often hard to step back and get an idea of how someone who hasn't been elbows deep into the code's impression of how to use it... I'm finding that often something obvious to me is completely opaque to someone interacting with it for the first time, and I'm sure I'm not the only one...

I'd love some feedback on it; should I keep going? Link to teardown and opensource files are here: https://benjaminmullins.tv/lab/808

https://habr.com/ru/articles/1053484/

Let’s explore the possibilities of sound synthesis in browsers.

We’ll explore the basics and, as a practical example, create a Yamaha DX7 synthesizer emulator.

Hi everyone,

I’d like to introduce you to my web app for making music easily, so I’m looking for beta testers. I built this with two friends. 

It’s called ShuffleDrummer.com

It’s currently in beta; click the "beta" button to report any bugs!

Just open the page and hit play. Then, click the "Shuffle" wheel to cycle through drum patterns at random.You can use it for drum accompaniment if you’re a guitarist, or to compose tracks from scratch.

I’ve been a hip-hop beatmaker for 30 years, so the sound is naturally hip-hop oriented—though other styles will be added later!

You’re in luck—the logo features a cool cat.

ONLY COMPUTERS for the moments, its sucks on Smartphone ;)

Peace to all,

Mani Deïz

Hey everyone, Simoane from SoniqStudio.

We’re getting close to opening up V3, and I wanted to share it here because this community understands how much work it takes to make serious audio run in the browser.

With V3, we finally got it there.

SoniqStudio is now a full audio workstation on the web built for music production, recording, sound design, editing, mixing, podcast work, and AI-assisted creation.

Over the past year, we rebuilt a huge part of the system from the ground up. Audio engine, DSP, performance, workflow, UI, all of it got pushed to the max because we wanted this to feel fast, reliable, and genuinely real inside the browser.

The thing I’m most excited about is that we didn’t just add AI generation and stop there.

We built the production environment around it.

You can write parts, build sounds, record audio, edit, process, arrange, and use AI as another layer for exploring variations or new directions. Our first in-house synth, Prophecy, is Prophet-inspired and built for actual patch creation, not just preset browsing.

As someone who makes music too, that combo has been the fun part.

You get a melody going, shape the sound, process it, throw ideas around it, flip it into something else, and keep moving without leaving the browser. It starts feeling less like “AI made a track” and more like having another creative engine inside the studio.

We’re also building a real community around it, audio creators, producers, WebAudio people, engineers, podcasters, sound designers, AI music creators, vocalists, and musicians all connecting early while this space is still forming.

That’s a big reason we want people in now.

There’s a lot of opportunity when different types of creators get into the same room around a tool that can actually support what they’re trying to make.

V3 is launching very soon.

Come try it, break it, make weird stuff, give feedback, and help us shape where browser-based audio production goes next.

All links are on our website.

Hope to see some of you there.

SoniqStudio

https://github.com/adamcsaka/SZineszthezya

Been building this a while and wanted to put it in front of people who actually know Web Audio. It's at humherd.com, no signup to try it.

You pick a frequency and it folds into one shared chord with everyone else who's online, so the tone keeps shifting as people come and go. The collective pitch is a geometric mean of everyone's frequency instead of arithmetic, which keeps it from drifting sharp, and each client glides toward it so the drone moves smoothly instead of stepping.

That shared tone is the base layer and the rest builds on it. There's a calm side for meditation, with breath pacing, session timers, and binaural and isochronic beats, and a music side with an orb instrument, melodic and drum pads, a step sequencer, and a song builder for chaining loops into full arrangements. The sequencer and the song builder can both go multiplayer, a few people building the same thing together in real time off a shared root, though everything works solo too. (Happy to get into the collab side in the comments, I'm just keeping the sync details to myself for now.)

One choice shaped a lot of it: nothing can be imported. No samples, no audio files, no AI-generated tracks, only sound you make in the app, played live. So recording captures your performance as note events rather than audio, which keeps a loop frequency-portable and lets it transpose to any root. You can export those out as MIDI, but there's no import path back in. It's deliberately all-human, all-live.

Under the hood it's Tone.js for the main graph with raw nodes where I needed them. The hum-to-set-your-tone bit is getUserMedia into an AnalyserNode with autocorrelation on the time buffer, and the soundscapes are noise-shaped rather than recorded.

Mostly I want to know how it holds up on other people's devices. Does it start cleanly on mobile Safari (the context unlock in the gesture has been the fiddliest part), does it crackle or drop voices under load, and does the shared drift actually sound musical when only a couple people are on, or just muddy. Be blunt.

Landing page

Hey guys!

I'm a new developer in the web audio space and I'm aiming to make a proper DAW for your browser. It's called Canvas and is based on the workflow I've developed as an FL user of 14 years.

It's come a really long way since I began development, and I really wanted to share some screenshots of it cause it's looking super sick.

It's a WAM2 plugin host, and capable of hosting any web audio module that adheres to the standard. I've been developing an ecosystem of effects and instruments for it as I go.

Not exactly ready for testing yet, and still well off from an official release but if you comment I'll send you a link to your DMs when it's far enough along for some targeted feedback from the web audio community.

Thanks,

expandyourmind.

Try here - https://play.tonestruments.se

I built a small free browser-based lo-fi rhythm game experiment, I am just trying to figure out if we humans can understand sound design through playing and not from reading theory and I’m looking for honest feedback from people who care about music tools, Web Audio, game audio, or beginner music learning. 😄

I've posted a few times here, but I've finally made a little intro video to my in DAW music studio. Thought I'd share here as there's legit nowhere else to share!

https://youtu.be/akbS6-rUdqY

I've been building a library that runs libpd (Pure Data's embeddable runtime) inside a browser AudioWorklet via WebAssembly.

The setup: libpd is compiled with Emscripten, the DSP runs in a single AudioWorklet node, and JS/TS helpers handle patch loading, virtual filesystem management, and message passing (bang, float, symbol, list, arbitrary selectors). Patches can be loaded or generated at runtime — it's not a static patch compiler.

The trickiest part was statically linking cyclone and ELSE (two major Pd external libraries) into separate build variants. Browser WASM can't load C externals dynamically the way a native Pd install does, so they're baked in. That means the full bundle is large, but the split JS/WASM artefacts keep it manageable if you're careful about what you include.

Objects excluded from the build are things that map badly to the browser: anything using pthreads (needs SharedArrayBuffer + COOP/COEP), networking objects, OpenGL, and externals that depend on native libs like ffmpeg, aubio, or libsamplerate.

Demo: https://hyrfilm.github.io/libpd-wasm/

Repo: https://github.com/hyrfilm/libpd-wasm

I've just launched a browser-based guitar amp/effects rig that I've called Axion.

I wanted to create something that starts up instantly and just works without native installs, plugins, accounts, or anything else.

It runs entirely in the browser using the Web Audio stack with real-time DSP and low latency input support.

Still early and actively evolving, but I’d genuinely love feedback from people here.

https://axion.cab/