Creator Workflows
How to Master Suno v6 Stems: Targeted Song Edits and Inpainting
A source-checked workflow for replacing a song section, extracting only the stems you need, exporting from Studio, and checking the result in a DAW.

On this page
- What v6 actually changes
- Start with a short, testable editing brief
- Replace a section and choose a version
- Treat “inpainting” as an editing description
- Separate stems for a specific task
- Move the project into Studio or a DAW
- Use MIDI when it serves the arrangement
- Review a client-ready result
- Keep rights review separate from sound review
- Work through one handoff before repeating it
- A practical repeatable sequence
Suno v6 can change part of an existing song using a plain-language instruction. Suno also offers stem extraction and a separate Studio workflow for arranging and exporting tracks. Those are useful capabilities, but they are different operations. Editing a section does not imply that the model generates four independent, phase-perfect stems internally. Extracting stems is a later separation step, and a Studio multitrack export contains the tracks in a Studio project. Understanding that distinction makes the workflow easier to use and the final audio easier to evaluate.
This guide uses Suno's September 2026 v6 release notes, Replace Section instructions, stem extraction guide, and Studio export guide as the product record. Product documentation was checked October 7, 2026. The listening and mixing steps below are proposed production checks, not results from a Rise test. Check your plan and the displayed credits before committing a batch of edits.
Suno describes three models in its v6 family. The flagship v6 model is aimed at reliable, precise generation; v6-wild favors more varied output; v6-mini is the faster version available to all plans. The flagship and wild variants require Pro or Premier. All three can create up to eight minutes in one generation, according to the current help article. Model choice is useful at the idea stage. A producer who knows the desired structure can start with v6, while a producer seeking alternate directions may explore v6-wild and then rebuild a promising idea with more precise instructions.
View image detailThe release notes list several forms of control: change a section of a song, combine more than one source in a request, isolate a sample while building a new beat, provide text or media references, and change a single lyric. Use those examples to choose a task you can judge by listening: did the requested lyric, instrument, structure, or feeling appear, and does the rest of the track still work? A demonstration of a section edit does not establish how the model synthesizes or splices audio. The acceptance decision rests on the recording you receive.
The What's new in v6 guide lists Extend, Cover, and Replace Section among the tools powered by v6. The separate v6 FAQ explains two controls worth distinguishing: Variety adjusts the style prompts, while Max Mode spends additional credits on a generation. Suno recommends Max Mode for uses such as longer songs and covers that should stay close to their source. Choose it for the task at hand rather than treating more credits as proof of a better result.
Before opening an editor, write down the defect and the parts that should stay. For example: “The second chorus works, but the last lyric line is wrong. Keep the preceding verse, chorus melody, and overall mood. Replace only that line with the approved wording.” This is more useful than a broad request to “make the song better.” It gives you a way to compare versions and prevents an attractive but irrelevant output from passing review.
View image detailListen once without stopping and mark the approximate time of the problem. Then listen around the start and end of the section. Note whether a vocal phrase, cymbal decay, or sustained chord crosses either boundary. A section that begins mid-phrase will be harder to replace cleanly, regardless of how the product implements the edit. The safest selection is the smallest region that contains the problem while leaving enough musical context for a natural transition. This is a listening method, not a claim that Suno requires bar-aligned boundaries.
Save the original song in your project record. Capture its title, creator account, creation date, model selection if visible, and the reason for the edit. If you are working for a team, keep a short note naming the approved lyric or creative brief. These records make later decisions easier. They do not prove that a particular output is legally clear or technically flawless; they establish what your team intended and which version it approved.
Suno's Replace Section help page gives a concrete path for Pro and Premier subscribers. From Create or Library, open the song's More Actions menu, choose Edit, and locate Replace Section. Highlight the part to change. The editor brings the corresponding lyrics into the editing area so you can revise them. Select Recreate Section and confirm. Suno says the workflow creates two new versions. Listen to both before choosing one, after which the selected section is incorporated into a new Whole Song.
View image detailThe Song Editor guide also describes Quick Replace, a prompt for the selected region, previewing alternate versions, and moving a transition boundary on the waveform. Interface labels can vary by view. The reliable sequence is to locate the song, mark the section, describe the desired change, audition the alternatives, and commit only the version that meets the brief. A generated option is an audition, not an automatic improvement.
For a lyric correction, retain the exact approved text outside Suno and compare it word by word to the new recording. Check pronunciation, stress, and timing. A syntactically correct lyric can still land on the wrong beat or distort a name. Listen to the changed section with at least a few seconds of audio on each side. A local fix that sounds good when soloed may expose a jarring transition in the full mix.
For an arrangement change, name the job of the section rather than writing a long list of instruments. “Make the second chorus feel larger while keeping the lead vocal clear” gives an editor a concrete standard. After generating alternatives, compare energy, vocal intelligibility, bass movement, and continuity with the preceding section. If the model changes too much, narrow the request or edit a smaller region. If the change needs manual performance or exact timing, stop iterating and use a DAW where you can control those details directly.
Here, “inpainting” means replacing material inside an existing recording while evaluating how it joins the surrounding song. Suno's documented product names are Replace Section and its related lyric-editing controls. Follow those instructions when locating the feature. The listening task is to decide whether the new passage belongs in the full recording, including its entrance, exit, vocal phrasing, and ambience.
In a production handoff, describe what the next editor should inspect. A proposed note could say: “Second chorus replaced; version B selected after a full-song listen; check the join at 1:17 before approval.” That note identifies the version and an unresolved check. Include whether the concern is a click, an abrupt room sound, or a phrase that ends too early, so the recipient can judge the same problem rather than regenerate the whole song.
When you hear a click, abrupt ambience change, or lyric cutoff, widen the listening window and compare the two generated options. Move the boundary if the editor provides that control. If the problem persists, use a different region or finish the transition in a DAW. Small fades and clip edits can solve ordinary audio problems, but the exact remedy depends on the source. Do not promise that any one fade length will work for every vocal, reverb tail, or drum transient.
View image detailSuno says stem extraction breaks a song into parts such as vocals, drums, bass, guitar, and keys. The current Get Stems guide instructs Pro and Premier users to open More Actions beside a song in Workspace or Library, choose Get Stems, select a split type, and extract. In Studio, the path is to right-click an audio clip, choose Split Stems, select a type, and extract. These are separation workflows. They should not be described as proof that the music model synthesized independent source tracks from the outset.
Choose the extraction mode according to the edit. Auto Split analyzes a track into as many as 12 stems and currently costs 50 credits per extraction. Split from Mix targets one instrument or vocal plus a complement track. The September 9 Get Stems guide lists 10 credits per stem for that mode and for Premier-only Advanced Split, which lets you choose from nearly 100 instruments. Its older June 12 separation guide describes 20 credits total for the two stems created by a targeted split. Do not budget a returned pair as one 10-credit file: confirm the charge shown for your selection. The older guide also warns that requesting an absent instrument can consume credits without yielding a usable stem.
For a vocal replacement, start by asking whether you need a full set of stems. A vocal and complement split may be sufficient to compare the revised performance against the rest of the song. For a mix handoff, a broader split may give an engineer more control. In either case, solo every extracted part and then listen to it with the others. Separation can leave bleed, missing transients, or unstable tones. Suno calls the newer modes cleaner, but no separation tool can be assumed perfect on every song.
View image detailName exported files by what they contain, not by what you hoped to obtain. A file labeled “bass” that contains kick drum leakage should be documented as such. Include the original full mix, the chosen edited version, and the extracted parts in the handoff. This avoids a common problem: another engineer receives only processed stems and cannot compare them with the approved full-song output.
Suno Studio is a separate production surface, currently included with Premier according to its Studio 2.0 guide. It supports a timeline, effects, MIDI tracks, and stem separation. The September 9 export guide lists Full Song, Selected Time Range, and Multitrack, plus individual clip WAV downloads, and describes Studio audio exports as WAV files. The older August 13 Studio 2.0 guide also mentions 32-bit WAV or MP3. Because those pages describe formats differently, use the current export menu and inspect a sample file before promising a format to a collaborator.
For a handoff, decide whether you need the final mix, a selected passage for review, the tracks arranged in Studio, or individual extracted stems. These are different deliverables. Export a small test first and inspect the actual file properties in your audio editor. Record sample rate, bit depth, channel count, duration, and whether each file starts at a common timeline position. Those measured properties are more trustworthy than a generic tutorial's format claim.
View image detailIn a DAW, import the approved full mix as a reference and place the stems or Studio tracks beneath it. Align their start times. If the exported tracks do not add up exactly to the reference, do not force a null-test interpretation. Separation and processing can change the signal. Compare by listening to the sections that matter: vocal entrances, low-end impact, reverberant tails, and the edit transition. Keep the reference available throughout mixing so improvements in one stem do not hide damage to the whole song.
Use EQ and dynamics to solve a heard problem. For example, if a bass stem masks the kick, compare the low-frequency balance in context. If a vocal extraction contains cymbal bleed, heavy compression may exaggerate it. Avoid fixed “AI stem” settings such as always cutting below a particular frequency or always adding a prescribed saturation amount. The needed choice depends on the recording and its destination.
The current Studio export guide says a user can extract stems, click a stem, and select Get MIDI for 10 credits; Studio then produces a MIDI file to import into a DAW. Studio 2.0 also supports MIDI tracks and audio-to-MIDI work. This is a transcription and editing opportunity, not a guarantee that every note, chord, or vocal inflection will be captured exactly.
Import the MIDI into a temporary instrument track and compare it against the audio. Check timing, rests, note lengths, pitch bends, and chords. If a transcription is close, correct the notes and use it to layer a new instrument. If it is far from the source, manual playing or transcription may be faster. Save the edited MIDI separately from the raw extraction so another collaborator can tell which notes were changed by a person.
View image detailMIDI is valuable when a sound needs replacement but the musical phrase works. A keyboard part can be played through a different instrument, or a bass phrase can be revised without changing the whole recording. It is less useful when the identity of the sound depends on subtle timbre or performance detail that MIDI does not encode. Keep the original audio alongside the new instrument until the replacement survives a full mix review.
A technical workflow needs a review standard. Start with the creative brief: does the changed section say and do what was requested? Check the surrounding song next: did the edit alter a phrase, cue, or emotional arc the client wanted to retain? Then listen on more than one playback system. Small speakers reveal whether a vocal or hook remains clear; headphones make clicks, phase oddities, and isolated artifacts easier to hear. These checks are recommendations based on audio production practice, not product promises from Suno.
If the project will be synchronized to picture, check the cut against the actual video timeline. A chorus that begins a beat late can undermine a visual transition even if the song sounds good alone. Export a review file with the picture and timecode so stakeholders comment on the same version. Keep feedback tied to version names and timestamps. “Make it more energetic” becomes actionable when the reviewer points to a specific eight-second section and the desired change.
Before delivery, verify the exported file rather than assuming a menu selection succeeded. Play the start, middle, edited region, and end of the final export. Confirm there is no unexpected silence, missing stem, clipping, or wrong take. Compare the metadata and duration with the delivery specification. Archive the approved full mix, the working project, and any stems or MIDI that the agreement requires. Do not describe optional working files as part of the client's rights unless the agreement actually includes them.
Creative acceptance does not establish commercial rights. Suno's paid-plan rights article says songs downloaded while subscribed receive commercial-use rights, while the current Terms tie permitted commercial use to an approved download and other conditions. Suno also says commercial-use rights do not guarantee copyright protection. A production lead should verify the account, download status, source material, and current terms before distributing or licensing a track. The default Terms define a Remix here as a version made by another user through sharing/remixing features, with joint ownership to the extent copyright exists. Those joint Remixes remain noncommercial regardless of plan or download status unless a separate offering provides different terms. Suno's remix monetization guide, edited October 6, 2026, distinguishes a creator remixing their own work: that version can qualify for commercial use through a paid-plan download credit, even if the original was made without a subscription. The guide says a remix of another creator's track is not eligible for monetization. Check which situation applies before delivery. A paid account alone is not a clearance decision; keep the contractual review tied to the specific output and its inputs.
If an external audio clip, sample, voice, or lyric entered the project, record where it came from and what use was authorized. A generated output can still contain material that a team was not entitled to upload or use. Keep the rights file connected to the approved version. A beautiful stem mix is not useful if the underlying inputs cannot be cleared for the intended campaign.
Consider a proposed client job: a short video needs the same song with one corrected lyric and a less prominent guitar under the voiceover. Keep those requests separate. The lyric needs section editing; the voiceover mix needs control of the guitar against the rest of the recording. A full collection of stems is useful only if the receiving editor needs that broader control.
First, save the original mix and the approved lyric. Generate the replacement section, compare its wording and joins, and choose the version that works in the song. Then use the chosen whole-song version as the input for any separation. Extracting the old song first and substituting an unrelated new vocal later can leave the team comparing parts from different arrangements. Record which mix each stem came from so the recipient can reconstruct your decision.
For the guitar adjustment, try the relevant targeted split before requesting every available instrument. Listen to the guitar file and its complement around the voiceover. If the guitar file contains a noticeable part of the vocal, turning it down can change vocal intelligibility as well. Tell the editor what you heard. They may prefer a small adjustment to the full mix or a new arrangement over trying to clean a poor separation.
Make the handoff folder easy to read: an original reference, the selected edited mix, the requested stems, and a short note naming the source version and remaining checks. Ask the recipient to import a sample before exporting the entire project. Confirm the files line up with the reference and the voiceover, then agree on the final deliverables. These are proposed acceptance steps, not a report of a completed Suno production.
View image detailThis is also a useful place to apply Rise's test for what work deserves automation. File naming and completeness checks can be repeatable. Whether the lyric feels right or a transition distracts from the video still needs a person's judgment. Keep those decisions visible in the handoff rather than hiding them inside an export preset.
- Save the original song, the approved brief, and the target section.
- Use Replace Section to create alternatives, then audition each in the full song.
- Commit the version that fixes the named issue and preserves the surrounding material.
- Extract only the stems needed for the mix or handoff, after checking plan access and credits.
- Export a reference mix and the required Studio tracks or individual files.
- Inspect actual file properties and listen for transitions, bleed, clipping, and omissions.
- Use MIDI only when transcription adds useful control, and verify the notes by ear.
- Complete the separate rights and delivery review before distribution.
Apply the sequence to one song before committing a larger project. Start with a named defect, compare the replacement in context, and send the next editor only the files and notes needed for the agreed job. The workflow is ready to repeat when someone else can identify the approved version, hear the intended change, and understand any remaining limitation without reopening every generation.
Independent release check: TechCrunch's September 9 report describes the public v6 launch and prompt-based section editing. Product steps above rely on Suno's own documentation.
Checked for this article
Sources
- Advanced Stem SeparationSuno
- Introducing Studio 2.0Suno
- Suno Help, v6 FAQSuno
- Suno Help, What's new in v6?, edited September 9, 2026Suno
- Suno Help, How do I get stems?Suno
- Suno Help, Exporting from StudioSuno
- Suno Help, Can I replace a section of a song?Suno
- Song Editor guideSuno
- Suno Help, Paid subscription rightsSuno
- Suno, Introducing v6, September 9, 2026Suno
- Suno Terms of ServiceSuno
- TechCrunch's September 9 reportTechCrunch
- Rise Productive, What Is Work Worth Doing?Rise Productive
- Suno Help, Can I monetize a Remix?, edited October 6, 2026Suno



