Help
What is AI Music Prompt Lab?
AI Music Prompt Lab is a desktop workspace for the prompts you feed to Suno and other AI music generators. You build reusable Music and Vocal style cards, combine them into Songs with lyrics, organize everything in nested projects, and generate or refine prompts with Google Gemini - then copy the result straight into Suno.
What sets it apart is that it treats your prompts as reusable building blocks rather than one-off text. One Music style and one Vocal style combine into many Songs, so you build a small library once and recombine it endlessly - and the whole thing lives in a real workspace (projects, separate environments, tags, search, lyric translation, media linking, export) instead of a flat notes file. AI generation and a song wizard are built in.
It's for people who use Suno seriously - dozens or hundreds of prompts across many projects - and want a tool that keeps up. The main things you can do: build prompts as cards, organize your library, generate with AI, link media and lyrics, and export and import - each covered below.
Build prompts as cards
Everything you create is a card. Cards are what you paste into Suno, and the core idea is to build small, reusable Music and Vocal styles, then assemble them into Songs.
Controls
| Control | What it does |
|---|---|
| New | Creates a new card - pick the type (Music, Vocal, Song, Note) from the menu. Also on Ctrl+N. With a Suno song link on the clipboard it opens already filled in - see Start a card from a Suno link. |
Start a card from a Suno link
When you already have the song on Suno, you don't have to copy its pieces across one field at a time. Copy the song's link - either the short share link or the full song address - then create a new card: AI Music Prompt Lab reads the link from the clipboard, fetches the song's page, and opens the editor with the title, style, lyrics and creation date already in place, plus the link itself saved on the card.
It closes the loop for songs that were written outside the app, and it saves the four separate copy-and-paste trips that used to stand between a rendered song and a card describing it. Because the link is saved too, the song lands directly in the created state (see Song states) instead of needing the address pasted in afterwards. Titles written as 10-Sanctus are split as you would expect - the number becomes the card's sort number and the rest becomes its name.
Nothing is lost if the clipboard holds something else, or if Suno cannot be reached: the editor simply opens empty, exactly as it always did. And when the song is already rendered and sitting on disk, the file can do the same job as the link - see Start cards by dropping tracks.
Start cards by dropping tracks
Drag audio files onto the AI Music Prompt Lab window and they become Song cards. Drop a single track and the card editor opens with it, so you can look the card over before it is saved; drop several - or a whole folder, however deeply the tracks sit inside it - and each becomes a card straight away, in the order they were dropped, in whichever project you have open. Anything in the drop that is not audio is simply ignored.
It is the fastest way to turn a finished folder of renders into a library, and it is the same journey as Start a card from a Suno link taken from the other end: there, the link tells the app which song it is; here, the file does. A track that Suno rendered carries the song's identity in its own tags, so its card arrives complete - title, sort number, style, lyrics, creation date and the suno.com link, which also puts the song straight into the created state (see Song states). A track that came from anywhere else still becomes a card, linked to the file and named from the file itself, with 10-Sanctus split into the sort number and the name exactly as a Suno title is.
One case deliberately produces nothing: a dropped track whose Suno song has since been deleted or made private. Rather than invent a card for a song that is no longer there, AI Music Prompt Lab leaves that track out and tells you how many it left out. A file carrying no Suno tags at all is a different matter entirely - that is simply a track from elsewhere, and it still gets its card.
Copy a card to Suno
Each card in the list carries three copy buttons, badged T, S, and L, so you can drop the right piece straight into Suno without opening the card.
Controls
| Control | What it does |
|---|---|
| Copy title | Copies the card's title (T). When the card is numbered, the copy is prefixed with its two-digit sort number - e.g. 01-My Song - so it matches how the audio files are named. |
| Copy style | Copies the card's style (S). For a Song, its linked Music and Vocal styles are merged into the one prompt. |
| Copy lyrics | Copies the card's lyrics (L). |
The four card types
Every item you create is a card of one of four types: Music (an instrumental style), Vocal (a voice style), Song (a title and lyrics that links one Music and one Vocal style), and Note (free-form text for ideas or references).
Splitting Music and Vocal out from the Song is the whole idea - you build a small library of styles and recombine them across many songs, instead of rewriting a full prompt every time. You pick the type when you create a card, and it decides which fields the editor shows.
Automatic versioning
When you create a card with the same name and type as one that already exists, the new card automatically gets a version number added to its name.
This lets you iterate on a single idea: keep the same name and each attempt stacks up as a version you can compare, rather than overwriting the old one or inventing a new name each time. It happens on its own - reuse a name on purpose when you want to keep variants of one style together.
Example. You have a Music card named Lo-Fi Beat. Create another Music card and name it Lo-Fi Beat again - it is saved as Lo-Fi Beat v2, leaving the original untouched.
Edit a card
Opening a card shows the fields for its type - style or lyrics, a public description, a private note, tags, external links, and which project it belongs to.
Beside the style of a Music, Vocal or Song card sit two reference fields: the artist the style is aiming at, and whatever narrows it - an album, a song, an era, a genre. They record what you were going for, and they stay separate from the style on purpose: Suno strips contemporary artist names from a style prompt, so the style has to describe the sound rather than name it, and the name is kept here instead, where it can remind you and travel with the card without ever being pasted into Suno.
Controls
| Control | What it does |
|---|---|
| Name | The card's name (its title for a Song). |
| Type | The card type - Music, Vocal, Song, or Note. |
| Style | The main style content for a Music or Vocal card. |
| Reference Artist | The artist this style evokes. Reference only - never added to the style you copy to Suno. |
| Reference Complement | What narrows the reference down - an album, a song, an era or a genre. |
| Tags | Free-form tags, comma-separated. |
| External Links | External links (a URL and a label) attached to the card. |
| Media File | The audio file linked to this card, if any. |
| Note | The private note (see below). |
| Description | The public description (see below). |
| Create Card | Saves a brand-new card. |
| Save Changes | Saves edits to an existing card. |
Description vs. private note
A card has two text fields beyond its content: a description, which shows on the card and is included in exported documents, and a private note, which is never exported and never searched.
They serve opposite audiences - the description is what you share, the note is a reminder only you see - so keeping them apart stops private remarks leaking into an export. Use the description for context others should read, and the note for personal reminders like "try a slower tempo next time".
Assemble a Song from Music + Vocal
A Song holds a title and lyrics and links to a Music style and a Vocal style, so one library of styles powers many songs. A song is also colour-coded to show where it is in your pipeline.
Controls
| Control | What it does |
|---|---|
| Linked Styles | The Music and Vocal styles this Song links to. |
| Fetch lyrics | Fetches lyrics for the Song from a supported site (Suno, Producer.ai, Tunee.ai). |
| Copy Lyrics | Copies the lyrics without the structure markers, ready to paste. |
| Link Music/Vocal | Opens the Link view - drag Music and Vocal styles onto a project's songs to link them in bulk, instead of one card at a time. A project tool (see below). |
Linking Music and Vocal into a Song
A Song links to a Music style and a Vocal style; when you copy or export the Song, those linked styles are merged with the Song's own content into one prompt.
This is what makes styles reusable - change a Music style once and every Song that links it benefits, with no copy-paste. Link styles when you build a Song, and reuse the same Music or Vocal across as many Songs as you like.
Song states (colour)
A Song is shown in one of three colours, decided automatically from the labels on its external links: undefined (no recognised link), created (a link to an AI generator), or published (a link to a music site). You control which site names count as which.
It turns a link you already paste in into an at-a-glance pipeline view - which songs are still drafts, which are generated, which are released - without a manual status field. It updates by itself as you add links; adjust the site lists once if your platforms differ from the defaults.
Example. A Song whose only external link is labelled Suno shows as created. Add a second link labelled SoundCloud and the Song turns published.
Controls
| Control | What it does |
|---|---|
| AI Sites | The link labels that mark a Song as created (defaults: udio, suno, producer, tunee). |
| Music Sites | The link labels that mark a Song as published (default: soundcloud). |
Translate a song's lyrics
A Song can carry translated copies of its lyrics in other languages, stored on the card next to the original.
Controls
| Control | What it does |
|---|---|
| Translation | The translations tab on a Song card. |
| Source Language | The language the original lyrics are in. |
| Add Translation | Adds a translation you type yourself. |
| Translate with AI | Generates a translation with AI. |
| Translate all songs | Translates the lyrics of many songs into one language in a single run: on the selection strip for the selected cards, on a project's row for all of that project's songs. Songs without lyrics, or already translated into that language, are left out. |
Lyric translations
A Song can store translated versions of its lyrics - added by typing, with one AI call, or brought in with an .amlp LP prompt file (see Import and export an LP prompt file) - alongside the original, each tagged with its language.
It keeps every language version of a song in one place, so an exported document can include the translations you choose instead of you tracking them in separate files. Add a translation when a song needs to exist in more than one language; pick which ones to include when you create a document.
Organize your library
The prompt list is where you find any card, and it stays usable at hundreds of cards. Switch between a card grid and a compact list, search, sort, and narrow the view with filters.
Search accepts simple prefixes: type a plain word to match names, or use n: for name, s: for style, and l: for lyrics. Beyond favourites, type, and tags, a set of warning filters surfaces cards that need attention - untagged cards, songs missing media, missing LRC files, missing AI links, or not yet published.
Controls
| Control | What it does |
|---|---|
| Search all cards… | The search box - n: name, s: style, l: lyrics. |
| Favorites | Shows only cards you've marked as favourites. |
| Grid view | Shows cards as a grid. |
| List view | Shows cards as a compact list. |
| Sort by date | Sorts the list by date. |
| Sort by name | Sorts the list by name. |
| Untagged cards | Filters to cards with no tags. |
| Songs without media | Filters to songs with no media file. |
| Songs without LRC | Filters to songs with no LRC file. |
| Songs without AI link | Filters to songs with no AI-generator link. |
| Unpublished songs | Filters to songs not yet published. |
Projects
Cards live in a nested project tree - a folder structure where a project can hold sub-projects as deep as you like. Drag cards or whole projects to move them, and filter the list to a project to focus on one piece of work. Two quick views sit in the sidebar whenever they apply - Unsorted (cards in no project) and Untagged (cards with no tags) - and you can unlink cards from a project to remove them from it without deleting them. Each project has its own toolbar, which appears when you hover its row (see Where the actions are).
Controls
| Control | What it does |
|---|---|
| New project | Creates a new project. |
| Edit | On a project's row (hover it): opens the project dialog to rename it, recolour it, add links and set its media folder. |
| All Cards | Shows every card across all projects. |
| Unsorted | Shows only cards not in any project. |
| Untagged | Shows only cards that carry no tags; appears in the sidebar when any exist. |
| Move to root level | Moves a nested project up to the top level. |
| Unlink from project | On the selection strip: removes the selected cards from the open project without deleting them (with a confirm). It appears only while cards are selected and exactly one project is open. |
| Delete | On a project's row: deletes that project (with a confirm). On the selection strip: deletes the selected cards. |
| Also delete all cards in this project | In the delete-project confirm: ticked, the project's cards are deleted with it; unticked, only the project is removed and its cards remain, showing under Unsorted. |
Nested projects
Projects are folders for cards, and a project can contain other projects to any depth. A card belongs to exactly one project, or to none.
They keep a large library navigable - filtering the list to a project (which also shows the cards in its sub-projects) lets you work on one piece at a time. Reach for them once you have enough cards that scrolling the whole list gets slow.
Where the actions are
Actions sit at the level of what they act on, so a button never changes meaning depending on what happens to be selected. There are three places. The left-hand bar holds the actions on the whole list: sort, new folder, sync music URLs, export to a spreadsheet and create a document. Hover a project in the tree and its own toolbar appears at the right of the row - edit, tag, translate, import a folder, move to another environment and delete - each acting on that project, which does not have to be selected first. Select cards and a strip above the list offers tag, translate, unlink from the open project, move and delete for exactly those cards; the strip is there only while something is selected.
Because each button has a single subject, you always know what a click will touch, and the dialog it opens keeps that target for as long as it is open - the tag dialog, for instance, names it in its title (12 · Project name or 3 selected). Use a project's row for whole-project jobs, and the strip for a hand-picked set of cards.
Project tools and Finalized
Three views work on a single project rather than the whole library: Link Music/Vocal (bulk-link songs to styles), Link Media (attach audio files), and Reorder Songs (sequence and renumber - covered below). Because each one acts on one project's songs, its button is enabled only when you've filtered the list to exactly one project, and greyed out otherwise. Each project also carries a Finalized checkbox that locks all three tools at once.
Finalizing a project you consider done means an accidental drag or drop can't quietly renumber or relink it - the view still opens, but greyed out and inert until you unfinalize. Select one project to use the tools; tick Finalized when a project is complete, and untick it if you need to change it again.
Controls
| Control | What it does |
|---|---|
| Finalized | Marks the project as finalized (in the project dialog), locking its three tools. |
| Finalized | The same finalize toggle, on the top bar of the Link, Media, and Reorder views. |
Tags
Put free-form tags on any card and click a tag to filter by it. Click the active tag again to clear the filter. Each tag gets a consistent automatic colour you can override. To tag many cards at once, select them and use the tag button on the strip above the list, or hover a project and use the tag button on its row to tag all of that project's cards.
Controls
| Control | What it does |
|---|---|
| Tag | Adds or removes tags on several cards at once: on the selection strip for the selected cards, on a project's row for all of that project's cards. |
| Add | Adds a colour override for a specific tag. |
Tags and tag colours
Tags are free-form labels on a card. Each distinct tag is given a consistent automatic colour, which you can override per tag.
Tags cut across projects - one click filters every card carrying a tag, wherever it lives - and the colours keep the list scannable at a glance. Tag cards however you think about them (genre, mood, year); override a colour only when you want a particular tag to stand out.
Environments - separate workspaces
An environment is a self-contained workspace with its own cards and projects, for keeping unrelated bodies of work apart.
Controls
| Control | What it does |
|---|---|
| New environment | Creates a new environment. |
| Move to another environment | Moves a project, with its cards, to another environment (on the project's row), or moves the selected cards there (on the selection strip). |
Environments
An environment is a self-contained workspace with its own cards and projects. There is always a default environment and a special Global environment whose cards are available inside every other one.
It keeps unrelated work fully apart - say two artists or two clients - while letting shared building blocks live in Global so you don't duplicate them. Reach for a second environment only when you have genuinely separate projects you don't want mixed; most people stay in one.
Reorder a project's songs
The Reorder Songs view lets you drag a project's songs into the exact order you want. When you drop a song into a new position, the whole set is renumbered 1..N so the sequence stays clean - no gaps, no duplicates. It is one of the project tools, so it works only with a single project in focus (see Project tools and Finalized).
The list scrolls by itself when you drag a song near its top or bottom edge, so carrying a song from the end of a long set to the very top takes one drag. Each song has a play button, so you can listen while you decide the order; it keeps working on a finalized project, where the rest of the view is locked.
An optional Rename media toggle carries the order through to disk: with it on, each song's linked audio file is renamed so its leading number (the NN- prefix) matches the new position, and the song's .lrc lyrics file beside it is renamed with it so the song doesn't lose its lyrics file. For a FLAC, the track number stored inside the file is rewritten to the new position too, keeping any zero-padding and any /total you had, so a player that sorts by that tag agrees with one that sorts by the file name. A file is never renamed onto a name that is already taken - the file stays as it is and the track number is still updated. Leave the toggle off to reorder inside the app only and leave your files untouched. In Settings, on the Media tab, you choose whether the toggle starts ticked each time you open the app.
Controls
| Control | What it does |
|---|---|
| Reorder Songs | Opens the Reorder Songs view for the active project. |
| Rename media | When on, reordering also rewrites each linked audio file's leading number, its .lrc file's name and a FLAC's track number to match. |
| Rename media on sort by default | In Settings, on the Media tab: sets whether the Rename media box starts ticked. It starts from this setting each time you open the app, whatever you ticked last time. |
Generate with AI
Instead of writing a style or lyrics from scratch, you can have Google Gemini write or refine it. Generation is offered in the Music, Vocal, and lyrics editors.
To use it, set a Gemini API key in Settings - get a free key at aistudio.google.com; it's stored locally and no third party sees it.
Controls
| Control | What it does |
|---|---|
| AI Generate | Runs the AI generation with your current request. |
| Gemini API Key | Your Gemini API key (required for any generation). |
| Simple | Sets Simple as the default generation mode. |
| Expert | Sets Expert as the default generation mode. |
| Music (chars) | Target length for generated Music styles. |
| Vocal (chars) | Target length for generated Vocal styles. |
| Lyrics Character Threshold | Lyrics length above which the counter turns red. |
Simple vs. Expert generation
AI generation runs in two modes. Simple takes a template and your plain-language request. Expert opens the prompt's individual blocks - Role, Rules, Style (and Structure for lyrics) - each with its own editable text and an on/off toggle.
Simple is fast for everyday use; Expert gives you exact control over how the prompt is assembled when you want to tune the result. Stay in Simple until a result isn't what you want, then switch to Expert; the default mode is set in Settings.
Presets and templates
A preset is a reusable piece of text for one block; a template is a named set of (block → preset) choices. Built-in defaults are seeded and protected from deletion; you can create, edit, and save your own.
They let you capture a phrasing that works once and reuse it everywhere, instead of retyping the same instructions into every generation. Save a preset when an Expert-mode edit gives a good result, and build a template when a particular set of blocks suits a kind of song.
Smart variables
A preset can contain placeholders written as [NAME:type:default], where the type is txt or num. Each one becomes an editable field in a Variables panel, and its value is substituted into the prompt just before it's sent.
One preset then serves many requests - you change the variable values, not the prompt body. Add variables to a preset for the parts you change often, like an artist name or a tempo.
Example. A preset containing
[ARTIST:txt:Pink Floyd]shows an ARTIST field pre-filled with "Pink Floyd". Change it to "Daft Punk" and that generation uses Daft Punk, with the preset itself unchanged.
Song Wizard
The Song Wizard builds a whole song from an artist and a subject.
Controls
| Control | What it does |
|---|---|
| Artist | The artist whose style the wizard should infer. |
| Pick a subject | The subject the song should be about. |
| Next | Advances to the next step. |
How the Song Wizard works
The wizard runs in steps: you give an artist, and it infers that artist's stylistic "DNA"; you give a subject, and it generates a matching style prompt and full lyrics, which it places into a new Song.
It turns a single idea - an artist and a topic - into a complete draft in seconds, as a starting point you then edit. Use it to bootstrap a new song fast, then refine the generated style, the lyrics, and the Vocal link afterwards.
Link media and lyrics
You can tie the finished audio to its card: link a file from a folder, play it in place, import a whole folder of tracks as songs at once, and hand a song to the LRC editor to time its lyrics. The Link Media view is one of the project tools, so it works with a single project in focus (see Project tools and Finalized); while browsing a folder you can hide the files already linked to a song to concentrate on the ones still unlinked. And when your files are named with the NN-Title pattern, a wand button links the whole set in one go instead of file by file.
Controls
| Control | What it does |
|---|---|
| Link Media | Opens the media-linking view for the active project. |
| Import from folder | On a project's row (hover it): imports every audio file in a folder as a song in that project. |
| Choose folder | Chooses the folder of media files to browse. |
| Hide linked files | Hides the folder's files that are already linked to a song, leaving only the unlinked ones. |
| Auto-link files whose number and title match a song | Links every unlinked numbered song to the folder's file whose leading number and title both match. Existing links are never touched, and when a track exists as both flac and wav, the flac is chosen. |
| Play | Plays the card's linked audio file. |
| Open in LRC Editor | Opens the song in the LRC editor to time its lyrics. Greyed out when LRC Editor is not installed on this machine. |
Linking audio files
A card can point to an audio file on disk, so you can play it in the app and hand it to the LRC editor. A project can hold a media folder, and you can import a whole folder of tracks as songs at once.
It connects each prompt to the track it produced, so the workspace holds the result, not just the recipe - and the file stays on disk, referenced by its path, never copied into the app. Link media once a song is rendered, and point a project at its media folder when its tracks live together. A path can be stored in full or relative to a media root folder, which makes moving a whole library to another drive a single change (see Stored paths: absolute or relative).
One bonus: when a linked file was rendered by Suno (its tags carry Suno's provenance), the matching suno.com song link is added to the card automatically - the very link that drives the song's colour state (see Song states), so linking the audio also marks the song as created without you pasting anything.
That same provenance works in the other direction: dropping a rendered track on the window creates the card outright instead of linking it to one you already have (see Start cards by dropping tracks). Link media when the card came first; drop the file when the track did.
A card holds one Suno link at most, because that link is the song's identity - a second one could only contradict the first. Adding another Suno link replaces the one already there, and linking a file whose tags name a different Suno song corrects the card's link to match the file, rather than leaving the card pointing at two songs and exporting as the wrong one.
The AMLP_ID tag
Suno writes a song's id into the comment of the files it renders. AI Music Prompt Lab can instead keep that id in a tag of its own, AMLP_ID, on linked FLAC files. This setting is off unless you turn it on.
A dedicated tag keeps the id apart from text meant to be read: when you make a copy of a track to share, you can strip AMLP_ID and leave the comment alone, or the reverse. With the setting on, linking a FLAC moves its id out of the comment into AMLP_ID - moved, not copied, so no stray copy stays behind in the comment. And pasting a Suno link onto a card whose linked FLAC has no id at all writes the id from that link. That is the only way a track downloaded through Suno Studio can ever be identified, because Suno removes the id from those downloads.
Only the tags are rewritten: the audio and the embedded cover art are copied through untouched, and nothing is re-encoded. WAV files are never written to. And an id already in the file always wins over a pasted link - when the two disagree, the file is left as it is, so a link pasted on the wrong card cannot overwrite a correct id. Turn it on if you keep your masters as FLAC and want every file to carry its song id in a place you control.
Controls
| Control | What it does |
|---|---|
| Use AMLP_ID tag | In Settings, on the Media tab: moves or writes the Suno song id into linked FLAC files' AMLP_ID tag. Off by default. |
Stored paths: absolute or relative
A card remembers where its audio file is, and a project remembers its media folder. AI Music Prompt Lab can store those paths in two ways. Absolute keeps the full path (M:\Music\AI\yaiol\Public LP\260218 Nha\01-Title.flac), exactly as it always has. Relative keeps only the part below a media root folder you choose (Public LP\260218 Nha\01-Title.flac) and adds the root back whenever it needs the file.
The point of Relative is moving house: if your whole library moves to another drive, you change the root once and every card and project finds its files again, instead of relinking them one by one. Stay on Absolute if you never move your files; choose Relative if you might.
Switching is never silent. Choosing Relative, going back to Absolute, or picking a different root first shows an audit: how many card paths and project folders will be rewritten, how many files are already missing today, and, for a new root, how many of your files are found under it. Nothing is written until you press Apply, and Cancel leaves everything as it was. Relative needs every path to lie inside the root, so the switch is refused while any file is outside it; the audit lists which ones, and you can choose another folder from the same dialog. Changing the root while you are already on Relative rewrites nothing - the stored paths simply resolve under the new root - so after you move your library, point the root at its new location.
A switch moves no file and repairs nothing: a file that is missing stays missing, and the audit tells you which ones so you can relink them. When you change a project's media folder, only the cards whose file is missing are re-pointed - first at the same sub-path under the new folder, so renaming a folder on disk is one edit on the project, then by file name anywhere below it. A card whose file still works is never moved by a folder edit.
Controls
| Control | What it does |
|---|---|
| Stored paths | In Settings, on the Media tab: Absolute or Relative. Every change shows an audit first and is applied only when you accept it. |
| Media root folder | Shown while the paths are Relative: the folder the stored paths start from. Pick a new one after you move your library. |
Export and import
You can get your work in and out in several formats: export prompts as JSON, a spreadsheet, or a document; export only your custom AI templates; take a full database backup; and import any of them back.
Controls
| Control | What it does |
|---|---|
| Export all | Exports your prompts and projects. |
| Export cards | Exports the current cards. |
| Export AI templates | Exports your custom (non-default) AI presets and templates. |
| Database Backup | Exports a full database backup. |
| Export LP file | Exports the current songs as an LP prompt file (see Import and export an LP prompt file). |
| Import | Imports a file, auto-detecting what's in it. |
| Create Document | Creates a formatted document (with options for images, lyrics, and translations). |
Import and export an LP prompt file
An .amlp file is an LP prompt file: a whole set of tracks in one document. Importing one turns each track into its own Song card, carrying that track's title, number, description, style, lyrics, language and date - the entire set brought in at once, instead of pasting each song by hand.
There are three ways to bring one in, and they all do the same thing: the Import button, dropping the file onto the window, or double-clicking it on the desktop once AI Music Prompt Lab is installed. Where the tracks land depends on where you are: with a project open they are added to it, and with no project open the LP brings its own, named after the file's own title. A project keeps its own environment, so importing into one never scatters its cards somewhere else.
Export writes one back out. It takes the songs you have ticked, or - when nothing is ticked - every song the current view is showing, so the search box, the active project and the filters all decide what goes in the file. Each song's style is exported the way you would actually paste it into Suno: its own style plus the styles of the Music and Vocal cards linked to it.
A file can say more than one language. The language at the top applies to every track, but a track can carry its own LANG: line when it is sung in something else, and the song gets that language instead. A track can also carry translations of itself: a TITLE (xx): and a LYRICS (xx): block, where xx is a language code, become that song's lyric translations (see Lyric translations), exactly as if you had added them in the app. The two reference fields travel too, as REFERENCE ARTIST: and REFERENCE COMPLEMENT:. Export writes all of these back out - a track's LANG: only when it differs from the file's own - so a set goes out and comes back with nothing lost.
For example, a track sung in Portuguese with an English gloss ends like this:
LANG:
Portuguese
LYRICS:
[Verse]
Saudade no porto…
TITLE (en):
Longing at the Harbour
LYRICS (en):
[Verse]
Longing at the harbour…
The translation blocks always come last in a track: LYRICS (en) runs until the next translation block or the next track.
It's the quickest way to seed a new project from a batch of prepared song prompts, and the quickest way to hand a finished set to someone else; a plain .json still imports exactly as before. One rule: because Songs can't live in the Global environment, import an .amlp into a normal environment. When an import fails, the message says why - no tracks found, or a file that could not be read as an .amlp.
What round-trips and what doesn't
JSON exports - prompts, AI templates, and full backups - can be imported back, and so can an .amlp LP prompt file, which goes out and comes back in with its languages, translations and reference fields. XLSX and DOCX are read-only formats for sharing or printing and cannot be re-imported. On import, cards are matched by name so they update rather than duplicate.
Knowing which format round-trips tells you what to use for what: JSON to move work between machines or keep backups, a spreadsheet or document when the destination is a person rather than the app. While your stored paths are Relative, a JSON export writes each card's file and each project's media folder relative to the media root, so the backup works on another machine as soon as that machine's root points at the library (see Stored paths: absolute or relative).
Appearance and language
Make the workspace yours: a dark or light theme, the interface in any supported language, a choice of font, grid or list view, and per-type card colours so the list stays scannable.
These choices live on the Settings page, which fills the window below the header, with its tabs down the left side. Everything you change applies at once, so there is nothing to save: leave with the back arrow, the settings button again, or Esc. The app stays open underneath, so a track that is playing keeps playing while you are in Settings.
Controls
| Control | What it does |
|---|---|
| Settings | Opens the Settings page, and closes it again. |
| Theme | Chooses the theme. |
| Dark | Switches to the dark theme. |
| Light | Switches to the light theme. |
| Language | Sets the interface language. |
| Cards Colors | The per-type card colours. |
| Reset | Resets the card colours to their defaults. |
Tips
- Build a Music + Vocal library first. Spend an hour creating a handful of styles you like; your Songs then reuse them in dozens of combinations.
- Use the Song Wizard for fast drafts. An artist plus a subject gives you a complete starting point in seconds - then edit it.
- Save Expert-mode tweaks as presets. When a block's phrasing works well, save it as a preset and reuse it across templates.
- Description is for sharing, the note is for you. Put what others should see in the description; keep private reminders in the note.
- Let song colours track your pipeline. Paste the generator or release link onto a Song and its colour tells you, at a glance, what's still a draft and what's out.
- Use JSON to back up, documents to share. Only JSON re-imports; XLSX and DOCX are for handing to a person.