Editorial standards
Suno changes fast, advice about it goes stale fast, and plenty of sites fill the gap with confident guesses. This page is the set of rules we hold ourselves to instead. They're written to be realistic for a small independent publication, which means we'd rather promise less and keep the promise.
Where our advice comes from
Every claim in a guide traces to one of four sources, and we treat them in this order:
- Suno's official documentation and announcements. The baseline for what a feature is supposed to do.
- Direct hands-on use. What actually happens when we use the feature to make real songs. When a guide gives settings or workflows, this is where they come from.
- Repeatable community findings. Techniques widely reported by other creators that we find credible. We treat these as useful signal, not established fact.
- Informed speculation. Sometimes nobody outside Suno knows why the model behaves a certain way. When we're guessing, we label the guess.
Those categories stay separate in the writing. "The documentation says," "in our use," "creators report," and "our best guess" are different sentences, and we try to make clear which one you're reading.
Version-dependent advice
Model behavior changes between Suno versions, sometimes without notice. Guides that depend on version-specific behavior carry a version label, and guides that receive meaningful revisions carry a visible updated date. If you're reading advice with no version context and it seems off, assume the model moved before we did, and tell us.
How guides are updated
When Suno ships a change that affects a published guide, the guide gets one of three treatments: revised to match the new behavior, annotated with what changed, or taken down if the technique no longer works. We would rather have a smaller library than a stale one. Feature-review articles are checked against the current release when new versions ship.
Corrections
If something in a guide is wrong, or a technique has stopped working, email hello@tinystudio.fm with the guide's address and what you observed. Suno version and a description of what you tried make the report much more useful.
Here's what happens next: we try to reproduce the problem, fix the guide if the report holds up, and mark meaningful corrections with an updated date on the article. Small fixes like typos are corrected quietly. If a correction changes the guide's actual advice, the change gets noted rather than silently swapped in.
Rights and money content
Guides on the Rights & money workbench explain rules in plain English, and plain English is all they are: not legal advice, and no substitute for reading the current terms yourself or talking to a professional for decisions that matter. This territory changes more often than any other part of the site, which is why those guides emphasize checking dates and primary sources.
Affiliates and sponsorship
tinystudio.fm currently has no affiliate relationships and no sponsors. Nobody pays us to recommend anything, and Suno has no involvement in this site. If that ever changes, the relationship will be disclosed on this page and inline wherever it's relevant, before you'd have any reason to wonder.
AI-assisted writing
It would be strange for a site about making music with AI to pretend otherwise: AI tools assist with research and drafting here. Every guide is directed, shaped, and edited by the site's writer, and the techniques come from real use, not from a model's imagination. AI assistance never gets to invent test results, sources, or community consensus, and when we haven't verified something ourselves, the writing says so.
What we won't do
No fabricated tests, no invented statistics, no fake testimonials, no "guaranteed" results, no pretending to insider knowledge of Suno's roadmap or model internals. If a guide can't be honest and useful at the same time, it doesn't get published.
Questions about any of this? hello@tinystudio.fm.