Last Updated: August 2026

The Composer's Guide to Effects Plugins (2026)

An effect earns its place in a cue by doing something the recording could not. A delay that pushes a solo cello into a larger room, a saturator that gives a synth bass the harmonics to survive a laptop speaker, a modulated chorus that widens a string pad without thinning it. These are judged on that basis: how they behave on real orchestral and hybrid material, what they cost in CPU when a template is already full, and whether the character they add is something you can still take back out later.

Start here

New to Effects? These are the roundups worth reading first.

Frequently Asked Questions

What is the difference between an effect and a mixing plugin?

A mixing plugin corrects: EQ, compression, level. An effect adds something that was not in the recording, such as a delay tail, a modulated width or a saturated harmonic. The line is blurry in practice, and a saturator used to fix a thin stem is doing both jobs at once.

Should effects go on the instrument or on a send?

Sends, for anything time-based. One reverb or delay shared across the strings, brass and woodwind keeps them in the same space, which is the whole point of a scoring template. Put the effect as an insert only when it defines the sound rather than places it, as with a filtered synth or a saturated bass.

Do effects belong in a scoring template at all?

Yes, but printed sparingly. A director's note can arrive after the cue is approved, and a stem soaked in a delay you cannot separate is a stem you cannot revise. Keep the wet signal on its own bus so it survives being asked for.

How much CPU should I budget for effects?

Less than you expect to need. An orchestral template already spends its headroom on samples, so an effects chain that is comfortable on an eight-track session can stall a hundred-track one. Where a plugin is expensive to run, we say so on the page.

Browse other categories