Suno features

The feature areas this guide covers

A map of the topics the toolkit is written around — song generation, style lines, personas, covers, remaster passes and playlists — with links into the matching guide pages and tools.

How to read this page

This is a guide index, not a product specification. Each block below names a topic area people work in, explains the part of the workflow this site can actually help with, and links to the pages where the detail lives.

We do not document buttons, plan tiers or limits that can change without notice. What we do document is the craft: how to phrase a style line, how to structure lyrics, how to test a change, and how to get your finished files out cleanly.

Independent project. Nothing here is an official reference, and every page is written from hands-on use rather than vendor documentation.

Song generation

The core loop: a style description plus optional lyrics goes in, audio comes out, and you judge whether the result matches what you imagined. Most of the improvement available to you happens before you press generate — in how precisely you describe genre, instrumentation, vocal, tempo and production character.

The guide breaks that description down into eight pillars so you can change one thing at a time instead of rewriting the whole prompt whenever a result disappoints.

  • Getting started — the first-hour path from blank box to a track you'd keep.
  • Prompting — anatomy of a prompt, cue selection, conflict resolution.
  • Structure — verse, chorus, bridge, and how section tags steer arrangement.
  • Prompt Builder — assemble a prompt pillar by pillar, then copy it out.

Styles and style lines

A style line is the short comma-separated description that carries genre, instruments, mood, tempo and production in one string. It is the single highest-leverage text you write, and it rewards vocabulary: concrete instrument names and production adjectives land far more reliably than praise words.

The styles library holds ready-to-paste lines organised by category and mood; the reference lists give you the raw vocabulary to build your own.

  • Styles library — searchable prompt-ready lines by category, mood and tag.
  • Genre guide — what each family actually sounds like and which cues signal it.
  • Reference lists — instruments, moods, vocals, production and tempo vocabulary.
  • Style Cleaner — dedupe tags, strip filler, trim a line to a character budget.

Personas and consistent voice

Persona work is about repeatability: getting a recognisable vocal character and production signature to survive across a set of songs rather than drifting track to track. The practical technique is to freeze the parts of your description that define identity — vocal type, tone, delivery, mix character — and vary only the song-specific parts.

Our vocal pages give you the vocabulary for that frozen block, and the testing pages give you a way to prove it is holding.

  • Vocals guide — type, tone, texture, delivery and harmony language.
  • Production guide — space, width, warmth and era character.
  • Prompt Lab — repeatable test designs for checking that a persona block holds.

Covers and re-interpretations

Cover-style workflows take an existing musical idea and re-render it in a different style. The craft problem is deciding what should stay (melody contour, lyric, phrasing) and what should change (instrumentation, tempo feel, production era), then writing a prompt that says so explicitly instead of hoping the model guesses.

Before you publish anything derived from someone else's work, check that you hold the rights you need. Our usage-policy article walks through the questions worth asking.

Remaster and revision passes

A remaster pass is any second attempt at the same song: re-rendering for a cleaner mix, extending a short take, or fixing a section that landed badly. Treated casually it becomes a slot machine. Treated as an experiment — one variable changed, both versions kept, a written verdict — it becomes a skill that compounds.

The Lab pages describe the eight-generation testing method we use for exactly this.

Stems-adjacent workflows

Once a track leaves the browser it usually enters a DAW, a video editor or a podcast timeline. That handoff is where file formats, sample rates and naming conventions start to matter, and where a tidy download habit saves hours later.

Our tools cover the parts that happen in the browser: pulling the master file, the cover art, the lyrics and the video in one pass, with predictable filenames.

Playlists and catalogues

As a catalogue grows, the interesting questions stop being about single songs. Which styles do you actually return to? How long is a typical track? How consistent is your publishing rhythm? Those answers change what you write next.

The playlist and profile tools read public pages and turn them into tables, insights and bulk exports.

If you want to…Start hereThen use
Write a better first promptPrompting guidePrompt Builder
Find a style that already worksStyles libraryStyle Cleaner
Fix a disappointing resultTroubleshootingPrompt Diff
Get your files outDownload walkthroughDownloader
Understand your own catalogueProfile DownloaderBatch parser

FAQ

Is this an official feature list?
No. It is an index of the subjects this independent guide covers. Treat the platform's own documentation as authoritative for anything about plans, quotas or interface changes.
Why is there no comparison table of plans or limits?
Those details change frequently and we would rather publish nothing than publish something stale. We focus on prompt craft and file workflows, which age far more slowly.
Where should a complete beginner start?
Read Getting started, then build one prompt in the Prompt Builder and generate twice. Everything else on this page makes more sense after you have heard your own results.
Do the tools need an account?
No. Every tool here runs in your browser, and the ones that read a public page do so through this site's own proxy. There is no sign-up and nothing to log into.