Deeper creator tools: five things we shipped for the writing itself SLUG deeper-creator-tools
Last time we said the next phase would be about the writing itself: version history, a lyrics editor that understands Suno, and musical details on Prompts. All three are live, and two more things landed alongside them that weren't on the list. Here's what changed, in the order it shipped.
Every edit is kept
Your Songs and Prompts now have a History link beside Edit. Every time you save a change to the text or tags, the version you replaced is kept. Each one shows what differs from the current text and, if you want it, a word-level diff so you can see exactly which line you changed.
Restore any version and you get that text back. The version you replaced is kept too, so a restore is never a one-way door. Visibility stays as it was, and cover images and renditions aren't part of the history, because those aren't the thing you'd be sorry to lose.
For now there's no cap: every version is kept. We may add a limit later, but nothing you've written since this shipped is going anywhere.
A lyrics editor built for Suno
The lyrics box is still a plain text box, so nothing about saving or drafts has changed. What's around it has.
Section buttons for Intro, Verse, Pre-Chorus, Chorus, Bridge, Hook, Instrumental, Solo and Outro. Each drops the tag on its own line where your cursor is, and Verse numbers itself from whatever's already there. Full structure lays down a whole song skeleton to fill in.
Live counts against Suno's limits: characters, words and lines, going amber as you get close and red when you're over. The caps are 5,000 characters for lyrics and 1,000 for the style prompt, which is right for Suno v5 and v5.5. Older Suno models allow less, so if you're still on one of those, leave yourself some room.
Structure panel that lists each section with its line count and flags the usual slips: a tag it doesn't recognise, a heading used twice, an empty verse, no chorus or hook in a song that clearly wants one. They're notes, not rules. Nothing stops you saving.
Syllables per line, off by default and labelled approximate, for when you're trying to make a second verse scan like the first.
A reference prompt beside the lyrics. Pick any of your own Prompts and its body sits read-only next to what you're writing, with its own counter against the 1,000-character style limit, so the two halves of a generation stay in sight of each other.
The Prompt form gets the same style counter. And on save, section tags are tidied up so [chorus] becomes [Chorus] and [verse 02] becomes [Verse 2].
Musical details on Prompts
A Prompt can now carry genre, mood, vocal type, language, BPM and key. All of it is optional and lives in a "Musical details" section of the Prompt form. Set any of them and they show as chips on the Prompt's card and page.
They're on Prompts rather than Songs because the style is the Prompt. A Song picks them up through the Prompt behind its main rendition and shows them as "Style" chips, so you don't fill the same thing in twice. Search gets genre, mood, vocals and language filters for both Songs and Prompts, so "dark, female vocals, in Spanish" is now a query rather than a scroll.
Duplicate your own work
Forking has been there since the start, but a fork is public by design: it links back to the original and tells the creator. Sometimes you just want to branch your own half-finished Song without any of that. Now there's a Duplicate button on your own Songs and Prompts, between History and Delete.
It makes a private copy titled "(copy)" and takes you straight to its edit page to rename it. Lyrics, description, tags, cover image and musical details come along. Renditions don't, since those belong to a specific generation. No lineage, no notification, no fork counter. A copy is simply a new original, which means it takes up a slot like anything else you create.
Bulk import
If your prompts are in a spreadsheet, a notes app export, or a PromptVault export from another account, you can now bring them across in one go. It's under Settings, Your data, Import.
Upload a CSV with a header row, a JSON array, or the export zip you get from the same page. You'll see a preview first, with the columns matched by name and the option to re-map any it got wrong. Nothing is written until you click Import. Afterwards you get a per-row result, created, duplicate, failed or skipped, with links to everything it made and a results file to keep.
Two details worth knowing. A prompt column becomes a private Prompt of its own, linked to the Song, so your imported work looks exactly like work you wrote here. And it's safe to run twice: an import of the same file reports the rows as duplicates instead of creating twins, so if it stops partway you can just run it again. There's a template CSV on the page if you want to see the shape it expects.
What's next
The next phase on the roadmap is about the community around the work rather than the work itself:
Comments: threaded comments and mentions, with notifications when someone reacts to your work.
Read API: scripts and agents can read back and update your own vault, and create Prompts as well as Songs.
Charts: weekly, monthly and all-time top Songs, Prompts and creators.
Profile pins: pin a Song, feature a collection, and add a header image to your profile.
As before, the order isn't fixed. If one of those matters to you more than the others, say so on Discord or through the bug reporter on any page.
Everything is still free during soft launch, and early accounts still get Pro-level capacity. If you've been editing a lyric in a text file because you didn't trust anywhere else with it, this is the update where it's safe to stop.
— Ed the War Moose approves this message. 🫎