We're looking for a user researcher to understand the needs of developers and designers. Is this you or someone you know? Check out the post: https://mzl.la/2IGzdXS

The AudioNode interface is a generic interface for representing an audio processing module. Examples include:

Note: An AudioNode can be target of events, therefore it implements the EventTarget interface.


The audio routing graph

AudioNodes participating in an AudioContext create a audio routing graph.

Each AudioNode has inputs and outputs, and multiple audio nodes are connected to build a processing graph. This graph is contained in an AudioContext, and each audio node can only belong to one audio context.

A source node has zero inputs but one or multiple outputs, and can be used to generate sound. On the other hand, a destination node has no outputs; instead, all its inputs are directly played back on the speakers (or whatever audio output device the audio context uses). In addition, there are processing nodes which have inputs and outputs. The exact processing done varies from one AudioNode to another but, in general, a node reads its inputs, does some audio-related processing, and generates new values for its outputs, or simply lets the audio pass through (for example in the AnalyserNode, where the result of the processing is accessed separately).

The more nodes in a graph, the higher the latency will be. For example, if your graph has a latency of 500ms, when the source node plays a sound, it will take half a second until that sound can be heard on your speakers (or even longer because of latency in the underlying audio device). Therefore, if you need to have interactive audio, keep the graph as small as possible, and put user-controlled audio nodes at the end of a graph. For example, a volume control (GainNode) should be the last node so that volume changes take immediate effect.

Each input and output has a given amount of channels. For example, mono audio has one channel, while stereo audio has two channels. The Web Audio API will up-mix or down-mix the number of channels as required; check the Web Audio spec for details.

For a list of all audio nodes, see the Web Audio API homepage.

Creating an AudioNode

There are two ways to create an AudioNode: via the constuctor and via the factory method.

// constructor
const analyserNode = new AnalyserNode(audioCtx, {
  fftSize: 2048,
  maxDecibels: -25,
  minDecibels: -60,
  smoothingTimeConstant: 0.5,

// factory method
const analyserNode = audioCtx.createAnalyser();
analyserNode.fftSize = 2048;
analyserNode.maxDecibels = -25;
analyserNode.minDecibels = -60;
analyserNode.smoothingTimeConstant = 0.5;

You are free to use either constructors or factory methods, or mix both, however there are advantages to using the constructors:

  • All parameters can be set during construction time and don't need to be set individually.
  • You can sub-class an audio node. While the actual processing is done internally by the browser and cannot be altered, you could write a wrapper around an audio node to provide custom properties and methods.
  • Slightly better performance: In both Chrome and Firefox, the factory methods call the constructors internally.

Keep in mind that Microsoft Edge does not yet appear to support the constructors; it will throw a "Function expected" error when you use the constructors.

Brief history: The first version of the Web Audio spec only defined the factory methods. After a design review in October 2013, it was decided to add constructors because they have numerous benefits over factory methods. The constructors were added to the spec from August to October 2016. Factory methods continue to be included in the spec and are not deprecated.


AudioNode.context Read only
Returns the associated BaseAudioContext, that is the object representing the processing graph the node is participating in.
AudioNode.numberOfInputs Read only
Returns the number of inputs feeding the node. Source nodes are defined as nodes having a numberOfInputs property with a value of 0.
AudioNode.numberOfOutputs Read only
Returns the number of outputs coming out of the node. Destination nodes — like AudioDestinationNode — have a value of 0 for this attribute.
Represents an integer used to determine how many channels are used when up-mixing and down-mixing connections to any inputs to the node. Its usage and precise definition depend on the value of AudioNode.channelCountMode.
Represents an enumerated value describing the way channels must be matched between the node's inputs and outputs.
Represents an enumerated value describing the meaning of the channels. This interpretation will define how audio up-mixing and down-mixing will happen.
The possible values are "speakers" or "discrete".


Also implements methods from the interface EventTarget.

Allows us to connect the output of this node to be input into another node, either as audio data or as the value of an AudioParam.
Allows us to disconnect the current node from another one it is already connected to.


This simple snippet of code shows the creation of some audio nodes, and how the AudioNode properties and methods can be used. You can find examples of such usage on any of the examples linked to on the Web Audio API landing page (for example Violent Theremin.)

const audioCtx = new AudioContext();

const oscillator = new OscillatorNode(audioCtx);
const gainNode = new GainNode(audioCtx);




Specification Status Comment
Web Audio API
The definition of 'AudioNode' in that specification.
Working Draft  

Browser compatibility

FeatureChromeEdgeFirefoxInternet ExplorerOperaSafari
Basic support14 Yes25 No156
channelCount141225 No156
channelCountMode141225 No156
channelInterpretation141225 No156
context141225 No156
numberOfInputs141225 No156
numberOfOutputs141225 No156
connect141225 No156
disconnect141225 No156
FeatureAndroid webviewChrome for AndroidEdge mobileFirefox for AndroidOpera AndroidiOS SafariSamsung Internet
Basic support Yes14 Yes2615 ? Yes
channelCount Yes14 Yes2615 ? Yes
channelCountMode Yes14 Yes2615 ? Yes
channelInterpretation Yes14 Yes2615 ? Yes
context Yes14 Yes2615 ? Yes
numberOfInputs Yes14 Yes2615 ? Yes
numberOfOutputs Yes14 Yes2615 ? Yes
connect Yes14 Yes2615 ? Yes
disconnect Yes14 Yes2615 ? Yes

See also

Document Tags and Contributors

Last updated by: sansb,