How Mureka takes direction
Mureka V9.5 takes a short descriptive prompt, a comma-separated styles list, and lyrics. The prompt sets the scene and the arrangement; the styles list is what the model matches on; the lyrics carry the words with section tags. Treat the prompt as intent and the styles as specification — the same reason a brief works better than a wish.
Layer by layer
- Prompt for intent, styles for match. "A late-night drive song, restrained and wide" plus "synthwave, analog pads, 96 BPM" says more than either half alone.
- Order the styles list. Genre first, then instrumentation, then vocal type, then tempo. Early tags carry more weight.
- Write lyrics before styling if the song sings. Syllable count in the chorus shapes the melody more than any tag can.
- Keep the vocal type in styles. "Female lead vocal" is a property of the sound, not part of the scene description.
- Describe what is there, not what is missing. There is no separate negative field in the prompt path, so "hand percussion only" beats "no drum kit".
- State tempo and key as numbers. Mureka follows a measured BPM more readily than "mid-tempo and moody".
Mureka setups you can paste
Paste the prompt, then the styles line, then the lyric scaffold into the matching fields.
Synthwave drive · 96 BPM · A minor
Acoustic folk · 92 BPM · G major
Epic orchestral · 110 BPM · instrumental
More ready-made prompts across moods and engines: AI music prompt examples.
What to leave out
- An essay in the prompt. Past two sentences the styles list does the work and the prompt just dilutes it.
- Negations in the styles list. Listing "no drums" can read as a request for drums. Describe the percussion you want instead.
- Artist names. Same trade every time: more risk, less information.
- Changing prompt and styles together. One variable per take, or you cannot tell which field moved the result.
- Vocal tags on an instrumental. Pick a lane; a styles list containing "female lead vocal" will produce one.
The rule underneath all of them: describe the music, never the record. Reference an artist or a track and you inherit someone else's rights problem along with a vaguer brief.
Build a Mureka brief from a reference track
The hard part is the honest numbers: tempo, key, brightness, dynamics, and the instruments actually carrying the groove. Music DNA Studio measures them from any MP3, WAV, FLAC or MP4 — locally in your browser, nothing uploaded — then outputs a Mureka-shaped prompt alongside versions for the other ten engines. You make the creative calls; the spec underneath is measured, not guessed.
A reference track gives you the numbers the styles list wants — tempo, key, brightness, dynamics, and the instruments that carry the arrangement.
Guides for the other engines
Eleven Music · Suno · Udio · Mureka · MiniMax Music · YuE2 · Stable Audio · Soundraw · Mubert · Beatoven · AIVA
Build The Mureka Brief
Drop in a reference, pick Mureka, copy the prompt, styles and lyric blocks. Free, no signup, nothing leaves your device.
ANALYSE YOUR AUDIO — FREE →FAQ
What is the difference between the prompt and the styles list? ▾
The prompt is the scene and the arrangement — what the song is for and how it moves. The styles list is the sonic specification the model matches against. Put feelings in the prompt and facts in the styles.
How do I exclude something in Mureka? ▾
You describe its absence with positive wording. Instead of "no electric guitar", write "fingerpicked acoustic guitar only". Models match what is written, and a negation often names the thing you wanted gone.
Can Mureka sing in languages other than English? ▾
Yes, the current models are multilingual. Say the language in the prompt or write the lyrics in it — the lyrics are the stronger signal of the two.
Why does my Mureka output sound unfocused? ▾
Often a styles list that spans two genres, or a prompt describing a mood the styles contradict. Cut the list to one genre family and make the prompt agree with it.
Is the Mureka API worth building on? ▾
Check the current access terms first — Mureka, like several vendors in this space, has changed its commercial terms recently. The text brief itself is portable, which is why it is written as plain prompt text rather than a vendor payload.