How to make audio low quality

What “low quality” audio means

You make audio low quality by carrying less detail in the signal, or by feeding the microphone a weaker, noisier, or more distorted sound. The usual controls are sample rate (how many times per second the sound is captured), bit depth (how finely each sample is stored), bitrate or codec (how aggressively a file or stream discards data), input gain, microphone distance and placement, and processing such as noise suppression or compression. Microphone detection (the system listing a device), input activity (a meter moving when you speak), and intelligible sound (speech a listener can understand) are separate. A selected mic with a moving meter can still sound poor.

Quiet is not the same as low fidelity. Lowering playback volume or muting output makes the sound smaller; it does not by itself muffle, hiss, distort, or add compression artifacts. If you only need it quieter, reduce output level or input gain. If you need it to sound worse, change capture settings, device, distance, or processing. A saved file, a system recording path, and a live call are also different: export settings affect a file you can play back locally, while a call still passes through the app’s own codec and the other person’s speakers or headset.

What to do

Decide first whether you are degrading a file, the computer’s microphone input, or live call audio. You need a way to listen (headphones or speakers) and, for a call, a preview or a short test meeting with yourself or a willing listener. No verified input-level target or bitrate threshold was supplied for this setup, so there is no single number that means “low quality” on every device. Use the meter to confirm the mic is still working, and use your ears for the quality change.

• Choose the path: convert or export a file at lower quality; change the microphone, gain, and operating-system input; or change whatever audio options the call app actually exposes.
• For a file, export or convert with a lower sample rate, a lower bit depth, and a lower bitrate, or with a more aggressive lossy codec. That shrinks the file and typically dulls highs, adds fuzz, or introduces warble and pumping.
• For a live microphone, use a weaker source if you have one (for example a laptop’s built-in mic rather than a headset boom), sit or hold the mic farther from your mouth, and lower input gain until the level meter still moves when you speak but the voice is thin, noisy, or distant.
• If cleanup is restoring too much clarity, turn off noise suppression, echo cancellation, automatic gain, or similar “enhance audio” options when those controls exist. If you want robotic or pumping artifacts rather than muffling, leave aggressive processing on and speak in a way that triggers it.
• Leave camera access and video capture out of this check. Changing audio does not show whether the camera is allowed, whether video is sending, or how the picture looks.
• Listen to the file, the system monitor, or a short test call and compare it with the original path.

How you will know it worked

It worked when playback or the far end of a test call is clearly worse in the way you intended—muffled, hissy, distorted, or compressed—while the correct microphone is still selected and the input meter still responds when you speak. If the meter does not move, you have a detection, mute, device-selection, or permission problem, not a quality setting. If the meter moves but speech is no longer understandable, you have gone past low quality into unusable audio.

This check does not prove how the same voice will sound on a real network, on another person’s headset, or after a call app’s codec. It also does not establish any exact decibel, sample-rate, or bitrate target; none was verified for this setup. If the operating system or app does not show sample rate, bitrate, or processing toggles, do not assume those controls exist. Use device choice, distance, and gain instead.