August 27, 2026AIExplore

How to Use Suno Custom Mode with Your Own Lyrics

Paste original lyrics into Suno Custom mode, set Style of Music and title, use Exclude when needed, and remake with Reuse Prompt.

Suno

Suno Custom mode lets you paste your own lyrics, set Style of Music, add a title, and use advanced options such as Exclude. Official help at Can I use my own lyrics confirms Custom mode on suno.com/create and states you retain ownership of original lyrics you input. iOS and Android Custom help mirror the web flow: toggle Custom, enter lyrics or let Suno generate them, toggle Instrumental if needed, enter Styles, add a Title, then Create. Overview: /explore/suno.

This guide focuses on finishing lyrics first, locking Style second, and remaking with Reuse Prompt when only one field should change. For section labels and v4.5 structure habits, see /blog/how-to-write-structured-lyrics-for-suno. For Simple mode ideation, see /blog/how-to-create-songs-with-suno-from-a-simple-prompt.

When to choose Custom mode

Choose Custom when the words matter: brand lines, story verses you already wrote, or section cues you want sung. Stay in Simple when you only need a quick demo and can accept generated lyrics.

Step by step Custom workflow

1. Paste finished lyrics

Write offline if needed, then paste. Keep section labels readable. Do not paste lyrics you do not have rights to use.

Scenario:
A realistic suno workflow is being prepared for Create Songs with Suno from a Simple Prompt using suno. The starting requirement is: Lyrics prep [ ] Original words you own [ ] Section labels ready [ ] Chorus shorter than verses if hooks blur [ ] No third party copyrighted lyrics. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Lyrics prep [ ] Original words you own [ ] Section labels ready [ ] Chorus shorter than verses if hooks blur [ ] No third party copyrighted lyrics" that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Inputs:
Use the actual source material required for this task, together with the intended audience, destination, format, and quality requirements. Specify relevant files, text, URLs, structured data, reference assets, dimensions, language, tone, timing, model or generation settings, credentials, field mappings, or integration values when they apply. Keep secrets out of the example and use the product's supported credential or configuration mechanism.

Workflow:
1. Start with one representative input that contains the important characteristics of the real workload.
2. Configure suno specifically for the requested task and make the important settings explicit.
3. Run the first pass and inspect the result against the objective.
4. Correct only the settings or source material responsible for a failed requirement instead of changing everything at once.
5. Validate the intermediate result before passing it to the next step.
6. When the result meets the requirements, save the successful configuration so the same process can be repeated consistently.
7. If this is a multi-step workflow, verify each handoff and keep a clear fallback or review path for failures.

Requirements:
The example must use supported functionality only. Do not invent product features, pricing, limits, integrations, model names, API behavior, or unavailable settings. Preserve important source data and formatting. Validate required fields before processing, handle empty or invalid input explicitly, prevent accidental duplicate processing where relevant, and stop or route the item for review when a required step fails. For credentials, use the supported secure configuration rather than placing secrets directly in the content.

Expected output:
The final result should directly satisfy the "Lyrics prep [ ] Original words you own [ ] Section labels ready [ ] Chorus shorter than verses if hooks blur [ ] No third party copyrighted lyrics" requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

2. Fill Style of Music and Title

Put genre, instruments, and energy in Style. Put the song name in Title so Library stays searchable. Use Exclude for elements you do not want per Exclude help.

Scenario:
A realistic suno workflow is being prepared for Create Songs with Suno from a Simple Prompt using suno. The starting requirement is: Custom fields Title: Corner Store Clock Style of Music: 90s boom bap, dusty drums, sampled piano, male rap vocal Exclude: heavy autotune, EDM drop Instrumental: off. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Custom fields Title: Corner Store Clock Style of Music: 90s boom bap, dusty drums, sampled piano, male rap vocal Exclude: heavy autotune, EDM drop Instrumental: off" that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "Custom fields Title: Corner Store Clock Style of Music: 90s boom bap, dusty drums, sampled piano, male rap vocal Exclude: heavy autotune, EDM drop Instrumental: off" requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

3. Create, then Reuse Prompt to refine

Official Reuse Prompt help fills prior details so you can edit Lyrics, Style of Music, or Title before remaking. Change one field per remake.

Scenario:
A realistic suno workflow is being prepared for Create Songs with Suno from a Simple Prompt using suno. The starting requirement is: Reuse plan Keep: lyrics + title Change: Style only to warmer vinyl and slower pocket Compare both new versions Archive rejects. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Reuse plan Keep: lyrics + title Change: Style only to warmer vinyl and slower pocket Compare both new versions Archive rejects" that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "Reuse plan Keep: lyrics + title Change: Style only to warmer vinyl and slower pocket Compare both new versions Archive rejects" requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

Practical Custom mode use cases

Boom bap story

Scenario:
A realistic suno workflow is being prepared for Create Songs with Suno from a Simple Prompt using suno. The starting requirement is: Title: Corner Store Clock Style: 90s boom bap, dusty drums, sampled piano, male rap Exclude: heavy autotune, EDM drop Lyrics: [Verse 1] Late shift lights flicker... [Chorus] Count the minutes.... The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Title: Corner Store Clock Style: 90s boom bap, dusty drums, sampled piano, male rap Exclude: heavy autotune, EDM drop Lyrics: [Verse 1] Late shift lights flicker... [Chorus] Count the minutes..." that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "Title: Corner Store Clock Style: 90s boom bap, dusty drums, sampled piano, male rap Exclude: heavy autotune, EDM drop Lyrics: [Verse 1] Late shift lights flicker... [Chorus] Count the minutes..." requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

Indie pop confession

Scenario:
A realistic suno workflow is being prepared for Create Songs with Suno from a Simple Prompt using suno. The starting requirement is: Title: Open Window Style: indie pop, bright drums, jangly guitar Lyrics: [Verse 1] ... [Chorus] .... The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Title: Open Window Style: indie pop, bright drums, jangly guitar Lyrics: [Verse 1] ... [Chorus] ..." that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "Title: Open Window Style: indie pop, bright drums, jangly guitar Lyrics: [Verse 1] ... [Chorus] ..." requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

Brand safe kids song

Scenario:
A realistic suno workflow is being prepared for Create Songs with Suno from a Simple Prompt using suno. The starting requirement is: Title: Dinosaur Bus Style: playful kids pop, clean diction, bouncy drums Exclude: explicit language, horror sounds Lyrics: your original kid verses. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Title: Dinosaur Bus Style: playful kids pop, clean diction, bouncy drums Exclude: explicit language, horror sounds Lyrics: your original kid verses" that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "Title: Dinosaur Bus Style: playful kids pop, clean diction, bouncy drums Exclude: explicit language, horror sounds Lyrics: your original kid verses" requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

Ballad with fixed hook

Scenario:
A realistic suno workflow is being prepared for Create Songs with Suno from a Simple Prompt using suno. The starting requirement is: Title: Quiet Kitchen Light Style: soft piano ballad, intimate female vocal Lyrics: lock the chorus lines exactly as written. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Title: Quiet Kitchen Light Style: soft piano ballad, intimate female vocal Lyrics: lock the chorus lines exactly as written" that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "Title: Quiet Kitchen Light Style: soft piano ballad, intimate female vocal Lyrics: lock the chorus lines exactly as written" requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

House track with spoken refrain

Scenario:
A realistic suno workflow is being prepared for Create Songs with Suno from a Simple Prompt using suno. The starting requirement is: Title: Night Drive Style: melodic deep house, warm bass, organic texture Lyrics: short refrain lines only, leave space for groove. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Title: Night Drive Style: melodic deep house, warm bass, organic texture Lyrics: short refrain lines only, leave space for groove" that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "Title: Night Drive Style: melodic deep house, warm bass, organic texture Lyrics: short refrain lines only, leave space for groove" requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

Folk duet sketch

Scenario:
A realistic suno workflow is being prepared for Create Songs with Suno from a Simple Prompt using suno. The starting requirement is: Title: Two Chairs Style: acoustic folk, two close vocals, light brushes Lyrics: call and response verse labels. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Title: Two Chairs Style: acoustic folk, two close vocals, light brushes Lyrics: call and response verse labels" that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "Title: Two Chairs Style: acoustic folk, two close vocals, light brushes Lyrics: call and response verse labels" requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

Rap feature ready

Scenario:
A realistic suno workflow is being prepared for Create Songs with Suno from a Simple Prompt using suno. The starting requirement is: Title: Second Verse Seat Style: modern trap adjacent boom, clear male vocal Exclude: unintelligible ad libs stacks Lyrics: leave a labeled [Verse 2] for a guest later. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Title: Second Verse Seat Style: modern trap adjacent boom, clear male vocal Exclude: unintelligible ad libs stacks Lyrics: leave a labeled [Verse 2] for a guest later" that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "Title: Second Verse Seat Style: modern trap adjacent boom, clear male vocal Exclude: unintelligible ad libs stacks Lyrics: leave a labeled [Verse 2] for a guest later" requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

Worship adjacent soft pop

Scenario:
A realistic suno workflow is being prepared for Create Songs with Suno from a Simple Prompt using suno. The starting requirement is: Title: Steady Hands Style: gentle pop, warm pads, sincere vocal Exclude: aggressive metal guitars Lyrics: original non copyrighted text. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Title: Steady Hands Style: gentle pop, warm pads, sincere vocal Exclude: aggressive metal guitars Lyrics: original non copyrighted text" that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "Title: Steady Hands Style: gentle pop, warm pads, sincere vocal Exclude: aggressive metal guitars Lyrics: original non copyrighted text" requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

Comedy character song

Scenario:
A realistic suno workflow is being prepared for Create Songs with Suno from a Simple Prompt using suno. The starting requirement is: Title: Office Plant Monologue Style: quirky showtune pop, theatrical male vocal Lyrics: punch lines on downbeats. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Title: Office Plant Monologue Style: quirky showtune pop, theatrical male vocal Lyrics: punch lines on downbeats" that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "Title: Office Plant Monologue Style: quirky showtune pop, theatrical male vocal Lyrics: punch lines on downbeats" requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

Multilingual chorus note

Scenario:
A realistic suno workflow is being prepared for Create Songs with Suno from a Simple Prompt using suno. The starting requirement is: Title: Sunrise Market Style: afro pop bounce, bright guitars Lyrics: keep language switches labeled by section. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Title: Sunrise Market Style: afro pop bounce, bright guitars Lyrics: keep language switches labeled by section" that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "Title: Sunrise Market Style: afro pop bounce, bright guitars Lyrics: keep language switches labeled by section" requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

More Custom examples

Scenario:
A realistic suno workflow is being prepared for Create Songs with Suno from a Simple Prompt using suno. The starting requirement is: empty lyrics Leave lyrics blank and ask Suno to generate words, then replace with your own on Reuse Prompt.. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "empty lyrics Leave lyrics blank and ask Suno to generate words, then replace with your own on Reuse Prompt." that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "empty lyrics Leave lyrics blank and ask Suno to generate words, then replace with your own on Reuse Prompt." requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

Scenario:
A realistic suno workflow is being prepared for Create Songs with Suno from a Simple Prompt using suno. The starting requirement is: Style only remake Identical lyrics. Style shifts from rock to acoustic rock, slower tempo, lighter drums.. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Style only remake Identical lyrics. Style shifts from rock to acoustic rock, slower tempo, lighter drums." that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "Style only remake Identical lyrics. Style shifts from rock to acoustic rock, slower tempo, lighter drums." requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

Scenario:
A realistic suno workflow is being prepared for Create Songs with Suno from a Simple Prompt using suno. The starting requirement is: Title hygiene Title: ClientA_DuskFolk_v3 so exports stay organized.. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Title hygiene Title: ClientA_DuskFolk_v3 so exports stay organized." that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "Title hygiene Title: ClientA_DuskFolk_v3 so exports stay organized." requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

Scenario:
A realistic suno workflow is being prepared for Create Songs with Suno from a Simple Prompt using suno. The starting requirement is: Exclude list Exclude: choir stacks, dubstep bass, scream vocals.. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Exclude list Exclude: choir stacks, dubstep bass, scream vocals." that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "Exclude list Exclude: choir stacks, dubstep bass, scream vocals." requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

Scenario:
A realistic suno workflow is being prepared for Create Songs with Suno from a Simple Prompt using suno. The starting requirement is: Instrumental flip Same Style, Instrumental on, lyrics ignored for a backing bed.. The work should be tested on a representative input first so the result can be reviewed before the same process is applied to the full project or production workload.

Objective:
Create a production-ready result for "Instrumental flip Same Style, Instrumental on, lyrics ignored for a backing bed." that directly supports the article use case. The output should be specific, reviewable, and reproducible rather than a generic demonstration. Keep the requested goal as the primary outcome and avoid adding unrelated features, assumptions, or unsupported capabilities.

Expected output:
The final result should directly satisfy the "Instrumental flip Same Style, Instrumental on, lyrics ignored for a backing bed." requirement and be understandable without guessing what was supplied or configured. A successful run should produce the intended output in the requested format, with the important values and workflow decisions clear enough to reproduce the result. If the workflow can fail, the expected behavior should also make the failure visible and provide a clear next action instead of silently producing an incomplete result.

Tips

Own the lyrics you paste
Keep production language in Style
Use Exclude instead of stuffing negatives into Style
Title every keeper
Reuse Prompt for controlled remakes
Confirm plan features before promising stems or Studio edits

Keep a short creation log beside your Library: mode, model if shown, Instrumental on or off, and the one field you will change next. That habit makes two version comparisons useful instead of random.

When credits, downloads, or model access look different than yesterday, open suno.com/pricing and your account plan page. Plan details change, so do not rely on memory for client promises.

Treat the first Create as a sketch. Listen all the way through both versions before rewriting the whole prompt. Small Style edits teach more than full rewrites.

If you collaborate, store winning Simple prompts and Custom Style paragraphs on a shared page. Reuse the skeleton and change topic or lyrics only.

For social clips, decide whether you need an early hook before you generate. Asking for a short intro after the fact wastes credits.

Separate exploration from release prep. Explore on whatever model your plan allows, then re check rights and Terms before monetizing.

Close each session by titling keepers and archiving rejects. A clean Library saves time when a client asks for the dusk folk take from Tuesday.

Prefer clear musical language over vague vibes alone. Genre, instrument, energy, and one story beat outperform a pile of adjectives.