Why autoplay starts quietly
A video can begin playing as soon as it appears in a feed, but sound is different: it can interrupt a conversation, a meeting, or a quiet room. Making autoplay videos muted by default lets a timeline move without making every scroll a surprise broadcast. People can choose to turn the sound on when they want it.
That small default also fits how feeds are used. People often browse in public, with headphones unplugged or their phone volume set for another task. Silent motion can still catch the eye, while unexpected audio can make someone close the app or stop scrolling altogether.
A compromise between attention and control
Autoplay helps platforms show more of a video without asking users to press play. But sound adds another demand: it competes for attention and can make the feed feel intrusive. Starting silently preserves the quick, continuous experience while leaving the decision to listen with the viewer.
The default can also reduce unnecessary mobile data and battery use. Video already requires the phone to download and display moving images; streaming audio adds more data, and playing sound uses the device’s audio hardware. Muting does not eliminate video’s resource use, but it avoids spending extra resources on sound many people may not want.
Why the default matters
Defaults shape behavior because most people do not change every setting. A muted start is therefore more than a convenience: it lets platforms keep videos moving through the feed while reducing the chance that playback will annoy users or expose what they are watching to everyone nearby. The result is a deliberate middle ground—the video can begin automatically, but the sound waits for permission.
