Four free tools that replaced paid ones in a working studio this month
A quick audit of the free and open-source software that is now good enough to keep in a professional chain — and the one place you should still pay.

Free software used to mean a compromise you explained to clients. This month's crop does not need explaining. Here is what earned a slot in a working chain, and what it replaced.
1. Local stem separation instead of a cloud credit plan
Open separation models running on your own machine removed the last reason to upload a client's master to a website. It is not better than the paid services — it is private, unlimited and free, which for rehearsal, reference listening and DJ edits is the whole job. Paid separation still wins on dense low end.
2. A native Linux synth instead of a compatibility layer
A major commercial synthesizer shipping a native Linux beta means Linux studios can stop maintaining translation layers that broke on every update. If you have been running a hybrid setup purely because one instrument would not load, re-check your plugin list this month — several holdouts have moved.
3. Free EQ and dynamics that hold up on a master bus
The best free equalizer and compressor plugins have been mix-grade for years. What changed is that they now have the metering to be used deliberately rather than by ear alone. Our 35 best free plugins roundup covers the specific ones.
4. Documentation as a tool
Not software: a habit. Keeping a plain-text session log — tempo, key, gear, decisions — costs nothing and saves the recall session that costs money. Everyone who has tried to remix their own track two years later understands why.
Where you should still pay
Anything that touches money or rights. Accounting, splits, registration and publishing administration are not places to save $30. A free tool that mis-registers a work costs more than every paid plugin you will ever buy.
And anything with support. When a session is due at 9am, a paid tool with a phone number is a different product from an issue tracker.
How to audit your own chain
Once a quarter, open a finished project and list every plugin you actually used. Most people find they use eight. Then check whether a free equivalent exists for each — not to save money, but because knowing the alternative exists is what stops a subscription from becoming a dependency.
How to learn more: start with the free-plugin roundup on this site, then test one substitution per project rather than rebuilding your template at once.