Classic Editor vs Creator Studio: Which Should You Use?

Novus ships two editors: the guided Classic editor and the node-based Creator Studio. The obvious question — which one should I use? — has a slightly surprising answer, because they are not competing products. Both are free, both export identically, and both open the same document. The real question is when each one earns its keep. Here is the honest comparison.

What Classic is

Classic is a guided path: upload a track, pick a template from the gallery, tweak, export. The tweaking happens through the shared control set — Color Mode (duo, gradient or full rainbow spectrum), Beat Response, Pulse Intensity, Shake Amount, Rotation Speed, glow and chromatic aberration — which is deliberately small enough to learn in one sitting. And because all 54 looks in the catalog ship as templates, starting points are never the bottleneck. Classic is optimized for finishing: there is always an obvious next step, and the distance from a blank page to an exported MP4 is minutes, not hours.

What Studio is

Studio trades the guided rail for a workbench: a layer stack where each layer draws its own engine, a node graph where signals — audio-source, math, merge (with its a/b inputs), LFO, remap, random and effect nodes — are wired into any parameter, an inspector for whatever is selected, and an assets area for project files, including logo uploads. Studio is optimized for control: if you can describe a behavior, you can usually wire it.

The part people miss: one document

Because both editors open the same document, choosing is never a commitment. Start a project in Classic, open it in Studio to add a second layer, hop back to Classic to nudge colors before export — nothing is converted, exported or lost along the way. Switching editors is walking between two rooms of the same workshop, not migrating between apps. That single fact should lower the stakes of everything else in this post.

A month in the life of one project

A concrete example. A podcaster starts in Classic: upload episode one, open the stacked-bands template from the Bars engine, set a duo Color Mode to the show's two colors, ease the Shake Amount down, export a 16:9 for YouTube. Twenty minutes, done, repeat weekly. A month in, the show wants a signature look — so they open the same project in Studio, drift a Particles layer behind the bars, add an LFO for a slow breathing motion no slider offered, and finish with a glow effect node. From then on, weekly production happens back in Classic — swap the audio, re-export — while the Studio wiring keeps working underneath. Neither editor could have carried that workflow alone.

Choose by task

• Your first visualizer ever — Classic. Learn what the controls feel like before you wire them.
• A template plus color and beat tweaks — Classic. The shared controls cover it with room to spare.
• Two engines in one frame — Studio. Layering is a Studio-only superpower.
• A parameter that moves on its own, or reacts on a custom curve — Studio. That is LFO, remap and math territory.
• A logo video — start in Classic with the logo-crown template; move to Studio only if you want extra layers behind the ring.
• A words-on-screen video — either: the Character Motion engine's word-wave mode has an editable Display Text field that works from Classic, while Studio lets the words share the frame with more layers.
• A deadline in ten minutes — Classic, no contest.

Signals it is time to graduate

Most people should start in Classic and stay until it pinches. The pinch is easy to recognize:

• You keep wishing a control would move on its own instead of holding one value.
• You want engine A drifting quietly behind engine B.
• You want an effect — a glow, an aberration — on one element instead of the whole frame.
• You are fighting a slider to approximate a behavior you can describe precisely.

Each of those sentences is a node graph asking to exist. When you hear yourself say one, open the same project in Studio and build the thing directly — our first-composition walkthrough covers the exact wiring.

What does not change

Everything that defines the output is identical in both editors. The full catalog — 9 engines, 6 modes each, 54 looks — is available to both. Beat sync behaves the same: a discrete, visible hit on every beat, computed deterministically. Export is the same in-browser render at up to 4K on desktop and 1080p on phones, as MP4 or WebM, free and watermark-free — and in both editors the preview matches the export exactly. Nobody can look at a finished video and tell which editor made it.

Three misconceptions worth clearing

• “Studio is the paid tier.” No — both editors are free and neither watermarks exports. Studio is a different interface, not a different license.
• “Classic makes lesser videos.” The render pipeline is identical; a Classic-only project exports at the same quality and resolution as a graph-heavy Studio one.
• “I'll have to export from one and import into the other.” Never — it is one document. Opening the other editor is navigation, not migration.

Bottom line

Classic is for finishing; Studio is for inventing. Ship your everyday videos through Classic's guided flow — the full walkthrough takes you upload-to-export — and graduate individual projects to Studio the moment they need layers or motion that sliders cannot express. Same document, same export, two speeds.