What is the HTML Muted Attribute?
The HTML muted attribute is a Boolean attribute that initializes an audio or video element with sound disabled. Its presence represents true regardless of the textual value assigned to it.
How the HTML Muted Attribute works
On an HTML media element, muted is a content attribute that sets the initial default-muted state during parsing. Boolean attribute syntax is presence-based, so muted="false" still requests muting; removing the attribute expresses false. Runtime playback state is exposed separately through the element’s muted property and can be changed by script or user controls. The setting participates in browser autoplay policy and in the accessible design of video playback, but it is not a security boundary.
Key facts
- 1The HTMLMediaElement.defaultMuted property reflects the muted content attribute, whereas HTMLMediaElement.muted represents the current audio-muted state.
- 2For a Boolean HTML attribute, muted="false" and muted="0" are both present and therefore true; code must remove the attribute to express false.
- 3Muting affects rendered audio output, not the encoded track: downloading, recording, or remuxing the resource can still preserve its sound.
When the HTML Muted Attribute matters
Set muted on autoplaying video because browsers commonly restrict autoplay with audible sound. Provide an accessible way to enable audio, and do not assume the attribute permanently prevents script changes.
Common use cases for video
These examples cover video broadly, not specifically the HTML Muted Attribute.
- Preparing uploaded video for web, mobile, connected-TV, social, or editorial playback.
- Creating clips, thumbnails, captions, alternate aspect ratios, and adaptive renditions.
- Normalizing camera, screen-recording, and user-generated files into predictable outputs.
Working with video
This guidance covers video broadly, not just the HTML Muted Attribute.
A demuxer separates tracks from the container, decoders turn compressed streams into frames or samples, and filters apply spatial or temporal changes. Encoders compress the transformed tracks before a muxer writes the chosen output container.
Video compatibility is the product of codec, container, profile, level, frame rate, color, audio, and subtitles. Validate the complete output on target devices because a playable file on one decoder may fail or look different on another.
What you gain
- Standardized derivatives make diverse source files playable on target devices.
- A retained master can feed many resolutions, aspect ratios, codecs, and channels.
- Automated inspection and transformation make large upload volumes consistent.
What it costs
- More efficient codecs can lower bitrate at similar quality but usually cost more compute and may have narrower support.
- Higher resolutions and frame rates preserve more detail and motion while increasing processing and delivery requirements.
- Fast encoding settings improve throughput but can produce larger files or lower quality than slower analysis.
Before production
- 1Inspect codec, container, dimensions, frame rate, color, audio, and subtitle tracks.
- 2Test visual quality and playback support across the slowest and oldest target devices.
- 3Preserve a suitable master before applying lossy, destructive, or delivery-specific changes.