Why Oxide, and when to play
Short answer: the manual way to clean AI stems is a long chain of steps, repeated for every stem. In Oxide you drop in a track or stems, it picks a cleanup preset for each one, and you preview against the original before you export. Keep Oxide's pick when it helps; switch the row when your ears disagree.
Oxide cleans AI music from Suno, Udio and other generators, in the browser or as a macOS and Windows app. Try Oxide Lite for free: 10 cloud cleanups a day with the full cleanup recipe. To hear it first, open the before/after demo.
The two paths look like this:
The manual way
If you clean an AI stem by hand, the work usually looks like this:
- EQ to take down harshness in the top end.
- De-ess the vocal.
- Denoise grain and hiss.
- Tame splashy cymbals.
- Soften the glassy sheen on an AI vocal.
- Check for stem-separation artefacts — another instrument in the gaps, or a part that sounds thinner than the full song.
- Repeat all of that for every stem, and again for the next track.
The problem is the length of the chain, and that you walk it again on every file. Vocals, hats and bright synths often need the most attention; bass and kick often need very little.
The Oxide way: Oxide picks, you play
Oxide collapses that chain:
- Drop in a track or a set of stems.
- Oxide picks a default cleanup preset for each stem. You can switch any row if you want, including Leave Clean when a stem is already fine.
- Preview the result against the original, then export.
Batch in Lite is capped at 3 stems. WAV export happens in the desktop app or plugin, not in the browser. Oxide Pro (£7/mo or $9/mo) and Oxide Studio (£19/mo or $24/mo) unlock 24-bit WAV export, the 5-band breakdown and folder rendering.
| The manual way | With Oxide | |
|---|---|---|
| Steps | A long chain, then the same chain again on the next stem | Drop in, review each row's preset, preview and export |
| Time | Longer, because every stem is its own pass | Shorter, especially on a batch of stems |
| Consistency | Easy to treat similar stems differently by accident | Each stem starts from Oxide's pick; you change only the rows that need it |
When to play
Oxide's pick is a starting point, not a verdict. A clean-sounding stem often gets a light touch, so the default may barely change it. Some presets are stronger, and on some sources they can add low end or squash the dynamics. Compare against the original at matched loudness, and trust your ears.
Shipped presets, from the demo:
- De-Sheen. Oxide's safe pick for clean tracks: a light 14–18 kHz polish, barely different.
- Surgical. Transparent de-fizz only. Nothing changes below 14 kHz.
- Master Bus. Light glue and air. Subtle, with a richer low end.
- Resculpt. Clears the harsh 3–6 kHz edge and the fizz.
- Drum Glue. Dense, gritty glue, best on drums and full mixes.
- Leave Clean. Leave the stem unprocessed when cleanup does not help.
The vocal sounds over-processed. If the voice loses body, or you hear words or breaths in what was removed, the pass is too strong. Switch to Surgical or De-Sheen, or Leave Clean, then de-ess and compress in the mix. See How to clean Suno vocals.
Cymbals still splash. Try Surgical for transparent de-fizz. If a harsh mid edge remains, try Resculpt and compare it with the original. If the attacks disappear, that is often a weak split — cleanup will not finish a badly split stem. See How to clean Suno stems.
The stem was already clean. Use Leave Clean, or keep De-Sheen for a light polish. Bass and kick often need little or nothing.
A full mix, or the stems. If you only have the stereo file, or the harshness is everywhere, work on the full song. Master Bus is a subtle option on a mix. If one part owns the problem — usually the vocal or the hats — clean that stem. See How to clean up an AI song.
After you change a row, listen to the cleaned stem and to what was removed. You want shimmer and fizz, not the body of the vocal or the attack of the drum. Then check the stem in the mix, not only in solo.
Hear it, and tell us if something is wrong
The before/after demo lets you switch between the original and each cleanup preset at matched loudness, on a vocal, a full mix and an a cappella clip.
Find a genuine bug in v0.3.0 and get a free month of Oxide Pro. Log it at Oxide support, with your email or handle. Genuine reports are reviewed, limited to one per person.
Your audio file stays on your computer. A scan sends a small numerical summary of the stem, not the playable file, and the cleanup runs locally.
Try Oxide Lite
Try Oxide on a track or stem, or listen first on the demo. Lite is free: 10 cloud cleanups a day with the full cleanup recipe. After today's 10, enter a licence key to keep scanning, or try again tomorrow. If Oxide already helps you, you can also share a Refer & Earn link.
Related: How to clean Suno stems · How to clean Suno vocals · How to clean up an AI song · Why does Suno sound metallic? · How to use the Oxide app
Working in a DAW? REAPER · Ableton Live · Logic Pro · FL Studio · Cubase · Pro Tools
Common questions
Why use Oxide instead of cleaning stems by hand?
The manual chain is real work, repeated for every stem. Oxide picks a preset per stem, you switch any row if you want, then you preview against the original and export.
When should I change the preset Oxide picked?
When your ears disagree with the default. Use a lighter preset, or Leave Clean, if a vocal sounds over-processed or a stem was already clean. Try Surgical or Resculpt if cymbals still splash, and stop if attacks or words start to disappear.
Should I clean the full mix or the stems?
Use the full mix when that is all you have, or when the harshness is everywhere. Use stems when you can isolate the part that sounds wrong, usually the vocal or the hats.
Does the preview sound the same as the exported file?
Treat the preview as a way to compare presets with the original. Always do a final listen on the exported file before you commit it to a mix.