From Template to Finished Export in Ten Minutes

This is a walkthrough with a stopwatch. Novus runs entirely in the browser — nothing to install, no account gate, no watermark bargaining — so the honest distance between “I have a track” and “I have a finished video file” is about ten minutes. Here is exactly where those minutes go.

You need one thing before starting: an audio file of your track on the device you are using. Everything else is already on the page. A pair of headphones helps too — you will be making taste calls against the mix, and a phone speaker lies about the low end.

Minutes 0–2: pick a template, not a blank canvas

Start at the template gallery, not an empty editor. There are nine engines — particles, trails, bloom, character motion, radial, spectrum, bars, tunnel and waveform — and every card previews live when you hover it, so one slow scroll down the page is genuinely the fastest shortlisting tool. You are choosing a personality here, not final details: does your track want something that erupts, something that flows, or something that breathes?

Minutes 2–4: audition the modes

Open a template page and it starts playing immediately — every template demos with one of three short loops Novus composed in-house (at 124, 92 and 140 BPM), so you can judge how the scene reacts to real audio before uploading anything. Each engine has six modes, and you can switch between them right on the page; the mode is tracked in the URL, so when you find the one, the link itself remembers it.

Two minutes is enough. If you are torn between two modes, take the simpler one — simple survives compression, small screens and short attention spans better. The runner-up is not lost, either: keep its URL and give it an export of its own another day.

Minute 4: open it in the Classic editor

Send your pick into the Classic editor. Classic is the guided one — a canvas plus a focused set of controls — and it is the right choice for a first video. The node-graph Creator Studio is the deep end; save it for the day you want layers and custom signal routing.

Minutes 4–5: upload your track

Drop in your audio file. Analysis happens in your browser — the track is not sent to a server — and the moment you press play, the scene reacts to your music instead of the preview loop. Watch and listen for thirty seconds before touching anything, because every tweak that follows should be a reaction to what you see here.

What you are looking for in that first watch: do the big hits land where your ears expect them, does the motion feel too busy or too sleepy against the mix, and does the default palette fight your cover art? Those three observations map one-to-one onto the three tweaks below — which is exactly why you watch before you touch.

Minutes 5–8: the three tweaks that matter

1. Color Mode. Cycle duo, gradient and rainbow spectrum until the palette matches the song's temperature — most people can hear whether their track is a two-color track or a rainbow track. If you have cover art, steal its palette with a duo or gradient. Sixty seconds.
2. Beat Response and Pulse Intensity. This pair decides whether the scene taps its foot or throws its whole body. Play the chorus, raise Beat Response until the hits feel like the drums, then use Pulse Intensity to size the reaction. If your genre has a known recipe, the modes-by-genre guide lists starting points.
3. Glow and Shake Amount. The polish pass. A touch of glow softens edges; a touch of shake adds impact on the biggest hits. Both are seasoning — if you notice them constantly, halve them.

Minutes 8–10: export

Open export, pick MP4 or WebM, pick your resolution — up to 4K on a desktop, 1080p on a phone — and let it render. Because the renderer is deterministic, the file matches the preview byte for byte: the beats you approved land on the identical frames, so there is no anxious re-watch to see whether the render “took.” It is free, there is no watermark, and the file is simply yours.

And if the result surprises you anyway — a color that reads differently at full size, a shake that felt subtler in a small window — change one control and render again. Iteration is the real workflow here: exports cost nothing and nothing queues behind a server, so the second attempt follows the first within minutes.

Where the ten minutes actually go wrong

• Auditioning all 54 looks. Shortlist from the gallery hover previews, cap yourself at three template pages, and commit.
• Tuning controls against the built-in preview loop instead of your own track. Upload first, then tweak — the loop is for choosing a scene, not calibrating one.
• Exporting before watching one full pass in preview. A three-minute watch now beats a re-render later.

That is the entire path. When the ten-minute version leaves you wanting platform-perfect sizing — vertical crops, 4K, bitrate — the next read is export settings for YouTube, Shorts and TikTok. And when you outgrow Classic, Creator Studio is waiting with layers and a node graph.