Novus Visualizers
Publishing, remixing, and the community feed
Publish a visualizer immutably, gather reactions, and let others remix it with attribution — or keep everything private, which is the default.
The community layer exists because presets are a bad way to share a look and a finished project is a good one. Publishing a visualizer lets someone open the actual document — engine, mode, layers, settings — rather than reverse-engineering it from a video.
It is entirely optional. Private-by-default ownership means nothing is published until you publish it.
Contents
Two ways to finish
Publish
Share a finished visualizer immutably, with attribution.
Remix
Open someone else's published work as a starting point.
- 1
1. Start from private by default
Assets and projects are private-by-default and scoped to your ownership. Uploads carry checksums, decode validation, and quarantine handling before they are usable, which matters on any surface where users can post files.
Nothing is visible to anyone else until you choose to publish. If you never publish, the community layer is simply not part of your experience.
- Private by default, scoped to your account.
- Uploads are checksummed, decode-validated, and quarantined.
- Publishing is an explicit act, never a side effect of saving.
- 2
2. Understand what immutable publishing means
A published visualizer is immutable — the published version stays as published. That protects everyone: someone who liked, saved, or remixed a post is not looking at something that has quietly become a different piece of work.
Keep iterating in your own project and publish again when you have something new. Treat a publish as a release rather than as a live document.
- 3
3. Publish something worth opening
The useful thing you are sharing is the document, not the video. Before publishing, make sure the project reads: sensible layer names, a coherent look, settings that make sense when someone else opens them.
A published project that is legible gets remixed. One that is a tangle of unnamed layers gets a like and nothing else.
- 4
4. Use reactions as signal, carefully
The feed carries follows, likes, saves, and comments. Saves are the most informative of the four — a save usually means someone intends to come back and build on the work, which is a stronger signal than a like.
Comments are moderated, and there is a reporting path. Community features come with moderation rather than as a bare feed, which is the correct order to build them in.
- 5
5. Remix with attribution intact
Remixes are attributed. Opening someone's published visualizer as a starting point carries the credit forward, so the lineage of a look stays visible rather than evaporating on first fork.
This is the fastest way to learn the node graph. Reading someone else's working document — how they routed an envelope, where they put a feedback edge — teaches more than a settings list ever does.
- 6
6. Know what you own
All visualizers are copyright-free and you own your exports: usable anywhere, commercially or personally, with no attribution required and no restriction. That is a property of the output, separate from the social attribution that travels with a remix inside the app.
Notifications keep track of follows, reactions, and remixes of your work, so publishing does not mean checking a feed manually to find out whether anything happened.
You are sharing a document, not a video
Publish is explicit and immutable — everything is private until you choose otherwise, and a published version stays as published. Name your layers before sharing, because a legible project gets remixed and a tangled one gets a like. Remixes carry attribution, and your exports remain copyright-free and yours regardless.
Frequently asked questions
Quick answers to common questions about this topic.
Is my work public by default?
No. Assets and projects are private-by-default and scoped to your account. Publishing is an explicit act and never a side effect of saving.
Why is publishing immutable?
So that anyone who liked, saved, or remixed a post is looking at the thing they responded to. Keep iterating privately and publish again — treat a publish as a release rather than a live document.
What happens when someone remixes my work?
The remix is attributed, so the lineage of a look stays visible. Notifications tell you when it happens.
Who owns the exports?
You do. All visualizers are copyright-free — use exports anywhere, commercially or personally, with no attribution required. That is separate from the in-app attribution that travels with a remix.