fMusic Studio & Suite are here · rebuilt for Pro Tools  The new generation of fMusic, in two tiers. From €9/month, every trial is full Suite.Explore fMusic →
← All articles
Comparisons · 9 minute read

fMusic Studio vs Suite: What Each Tier Includes, Honestly

SEP 29, 2026

At a glance: fMusic Studio is the complete product: the import pipeline with instrument recognition, the visualizer, routing, strip silence and print based export. fMusic Suite adds the delivery layer: Organize, print preview, per print recipes, categories from any session element, gain staging, template matching, offline use and the mixed queue. Studio is EUR 9 per month and Suite EUR 11, billed annually, both with 2 seats, both requiring Pro Tools 2024.3 or later on macOS 13 or later. Import results are identical in both tiers. If your exports are deliverables with specs, on deadlines, for clients, Suite is built for that layer. Otherwise Studio is not a compromise.


Two tier products invite suspicion, and the suspicion is usually earned: the lower tier often exists to be grown out of. This comparison is written to be checkable instead: the exact split, what each tier costs, and the honest cases where each one is the wrong buy.

The short answer

fMusic Studio is the whole workflow fMusic has always covered, rebuilt: audio files in, an organized and routed Pro Tools session out, deliverables printed back out in batch. Nothing in Studio is a trimmed version of a Suite feature. fMusic Suite keeps all of it and adds a layer aimed at delivery work: checking prints before they render, building exports from however the session is organized, and cleaning up sessions that arrive from other people.

The launch announcement covers why the product was rebuilt, and the full old to new mapping is in what changed from fMusic. This piece only weighs the two tiers against each other.

What both tiers share

Everything on the import side that produces the session: instrument recognition with custom instrument types, naming, color coding, category grouping, stereo content verdicts shown as badges, strip silence per category, and explicit placement of the imported material. Both tiers run everything through the visualizer, fMusic's own timeline view, where you see waveforms and audition material before anything touches Pro Tools. Both export through prints, with favorites that carry across sessions and multi format rendering in one pass: WAV, AIFF and MP3, each with its own sample rate and bit depth. Both include 2 seats, and both require Pro Tools 2024.3 or later on macOS 13 or later.

The shared surface goes deeper than a feature list. Placement of imported material is explicit in both tiers: session start, at the current selection, at a marker, or spotted to a typed timecode, with track placement at the top, at the bottom, below a chosen track or inside a routing folder. Favorites behave the same way in both: a print built from your categories is saved once and reused on every project, and favorite sets can be saved and loaded. Both tiers also follow the same settings philosophy: anything that defines how the studio works, categories, naming style, stereo rules, routing mode, is configured once in Settings and shown read only inside the flows, so it cannot drift between sessions by accident.

The point worth underlining: paying for Suite does not buy better import results. Recognition, naming, routing and strip silence behave identically in both tiers, so a Studio session and a Suite session prepared from the same files are the same session.

The exact split

CapabilityStudioSuite
Import pipeline, recognition, visualizerIncludedIncluded
Routing destination modeIncludedIncluded
Track presets and match templateNot includedIncluded
Gain stagingNot includedIncluded
OrganizeNot includedIncluded
Prints, favorites, multi format exportIncludedIncluded
Per print recipesGlobal settings onlyIncluded
Category sourcesRouting sourcesAny session element
Print previewNot includedIncluded
Offline useNot includedIncluded

Three rows deserve expansion. Organize. The new third flow opens an existing Pro Tools session, reads it track by track, and applies the same identification, naming, color and order that imports get, then writes it back. It is aimed at inherited sessions and at your own sessions after three weeks of revisions. Print preview. A print can be auditioned before rendering, isolated exactly as it will bounce, which turns a wrong mix source from a redone batch into a check that takes seconds. Category sources. Studio export categories select their tracks by routing source, a bus or an output, which works if your sessions are routed consistently. Suite categories can be built from any element in the session, including VCAs and folder tracks, so the way the session is actually organized is the way exports select their content.

The queue also differs in reach: both tiers queue work, and Suite's mixed queue runs imports, organize jobs and exports together as one batch. In practice the difference shows up at the end of the day: with Suite, a night's worth of mixed work, two imports, an organize pass and three deliveries, goes through one Process all and renders unattended.

Where Studio is the right buy

If the sessions you prepare are your own productions, your exports are rough mixes and stems for collaborators rather than contracted deliverables, and your sessions start from your own template with your own routing, Studio covers the entire job. The import pipeline, the visualizer and print based export are all there, and the results match Suite exactly. The annual difference between the tiers is EUR 24, but the honest reason to stay on Studio is not the price: it is that you would be paying for features you would not open.

What Studio asks you to live without is the check before the render. Studio bounces without a preview: you render, then verify the files, which is how every DAW works anyway. Gain staging is the other Suite feature worth checking before you choose: if your studio standardizes import loudness, the LUFS target and true peak ceiling live in Suite.

Where Suite is the right buy

If your exports are deliverables with specs, on deadlines, for clients, the Suite layer is built around exactly that work. Per print recipes hold a different source, range and format list per deliverable. Print preview catches the wrong source before the batch renders instead of after. Organize absorbs the sessions other people hand you. Offline use covers rooms that keep machines off the internet, and the mixed queue turns five sessions of imports and exports into one overnight run.

Offline use is easy to underrate until a machine is kept off the internet by policy, in a writing room or on a stage; Suite runs there. The honest limit runs the other way: if you never deliver to a spec and never inherit sessions, Suite's additions sit unused, and Studio is the better spend.

Three rooms, three answers

A producer printing their own records. Sessions start from your own template, exports are stems and roughs for collaborators, and nobody hands you a delivery spec. Studio covers all of it: the import pipeline, the visualizer, favorites and multi format export, with results identical to Suite's. The Suite features you would actually open in a year are close to none.

A mix engineer delivering to spec. Stems by category, three formats, a deadline and a client. This is the work Suite's layer was built around: per print recipes hold each deliverable's source, range and formats, preview catches the wrong source before the batch renders, and the mixed queue prints everything overnight. The EUR 24 a year between the tiers is smaller than one redone batch.

A studio that inherits sessions. If sessions arrive from other rooms, Organize is the deciding feature on its own: it reads the inherited session track by track and rewrites it categorized, renamed, colored and ordered. Everything else in Suite is a bonus on top of that one habit change.

Price, terms and how to decide

fMusic Studio is EUR 9 per month and fMusic Suite EUR 11 per month, both billed annually, both with 2 seats. New users get the standard 7 day trial with no credit card, and the trial opens the full Suite, so the choice can be made from use rather than from this table. Existing fMusic users were updated free into the tier matching their plan, and the whole user base received 15 days of the full Suite at launch, so if you were already a user you have likely had every Suite feature open. Current terms are on the pricing page.

The decision is the shape of your work, not its size. A one person room delivering broadcast stems to spec is Suite work. A busy producer printing roughs for their own records is Studio work, at any scale. If you are undecided, look at the last three exports you actually shipped: if any of them carried a spec, a format list, a stem naming convention or a range that was not the whole song, you were already doing Suite work with Studio tools.

Frequently asked questions

Is fMusic Studio a limited version of fMusic?

No. Studio carries the complete workflow the product has always covered: the import pipeline with recognition, the visualizer and print based export. Suite adds a delivery layer on top; it does not improve the results Studio produces.

What exactly does fMusic Suite add?

Organize, print preview, per print recipes, categories from any session element, gain staging, match template and track presets, offline use and the mixed queue that runs imports, organize jobs and exports as one batch.

How much does each tier cost?

Studio is EUR 9 per month and Suite EUR 11 per month, billed annually, with 2 seats on every plan. Current terms are on the pricing page.

Do the tiers differ in import quality?

No. Recognition, naming, routing, strip silence and the visualizer are identical in both tiers. A session prepared in Studio and one prepared in Suite from the same files are the same session; Suite's additions all sit in the delivery layer.

Which tier do existing fMusic users land in?

Every subscriber and lifetime holder was updated free into the tier matching their plan, with presets and settings preserved, and received direct communication about their specific situation.

Do Studio and Suite work with Logic Pro?

No. Both tiers are built for Pro Tools, requiring Pro Tools 2024.3 or later and macOS 13 or later. Logic users have their own product, fMusic for Logic Pro, with its own requirements.

Can I try Suite before choosing a tier?

Yes. The 7 day free trial opens the full Suite with no credit card, and the whole existing user base received 15 days of the full Suite at launch.

fMusic Studio covers the complete import and export workflow, and Suite adds the delivery layer for people who print to spec. Both tiers are at forte-ai.com/fmusic.

Stop doing the prep by hand.

fPost imports the AAF, routes and names every track, and hands you a session that is ready to mix.

Explore fPost →

Keep reading