chirp-v4-5 is the Suno V4.5 music creation model, which can generate songs from short themes or organize creations based on self-written lyrics, titles, and style descriptions. It is suitable for tasks requiring more complete lyric input, detailed arrangement descriptions, and vocal preferences, and can continue existing songs, create style covers, and reuse singer styles, allowing drafts to gradually become audio works that can be previewed and further developed.
Submit requests to the public API at api.acedata.cloud using the documented parameters, then use the results in your application.
Input parameters and result formats vary by service. Use the public API for this model and follow its guide for generation, task retrieval and editing operations.
Clarify capacity, inputs and outputs, and invocation methods before selecting a model.
The character limits and invocation methods above apply to this platform entry point and do not treat request parameter ranges as guarantees of the native model's duration or output quality.
Learn what chirp-v4-5 can bring to your work.
When you do not yet have lyrics, describe the theme, mood, and musical direction in Inspiration Mode; when you already have lyrics, switch to Custom Mode and enter the lyrics, title, and style separately. The two approaches suit different stages of creation: first explore the song concept, then use clear text to refine the content, rather than cramming every requirement into a single prompt.
Custom Mode accommodates longer style descriptions, making it suitable for specifying genres, instrument combinations, rhythmic feel, and vocal character at the same time. Vocal gender can be added as a preference in the creation requirements. In practice, emphasize the core sonic direction, avoid stacking conflicting labels, and use listening previews to determine whether the vocals and arrangement meet expectations.
A satisfying draft can retain its song ID for continuation or cover versions: continuation focuses on adding subsequent sections, while a cover version reinterprets the existing song as a reference. When you need to reuse a singer's style, first create a Persona, then use it for stylistically consistent creation, establishing a reusable sonic direction across different songs.
Start from specific tasks and find where the model can be effective.
Enter lyrics marked with verses, choruses, and bridges, then add a title and target style to generate demo tracks for discussing melody, vocals, and arrangement direction. This is suitable for lyricists presenting concepts to collaborators, with audio and lyrics as the primary deliverables; before finalizing, pay particular attention to diction, repeated sections, and emotional progression.
Write prompts around the video's theme, narrative mood, and desired musical atmosphere, select instrumental creation, and obtain soundtrack options for preview. You can explore directions such as warm acoustic and upbeat electronic separately, then pass suitable audio into the editing workflow. When precise timing is required, trim and arrange according to the actual final duration.
Provide an audio ID, continuation boundaries, and new lyrics for an existing song to try adding a bridge or a new ending; you can also explore another style through a cover version. For a song series, first save a suitable Persona, then reuse the singer's style. When delivering, retain each song's ID and audio to facilitate later comparison, continuation, and version management.
Choose based on task complexity, input materials, and expected results.
Compared with chirp-v4, chirp-v4-5 expands custom lyric input from 3000 characters to 5000 characters, style descriptions from 200 characters to 1000 characters, and provides vocal gender preferences. If lyrics are long, or you need to describe instruments, atmosphere, and vocal direction at the same time, V4.5 makes it easier to express your requirements; this does not mean that results will automatically better match your aesthetic preferences every time.
chirp-v4-5 and chirp-v4-5-plus are different versions, and the latter should not be treated as the same invocation name. If you need to continue using existing V4.5 works and creative settings, you can keep choosing this model; if long-form song planning matters more, consider V4.5+. Whichever version you choose, use final playback and actual duration to determine whether the work is complete, rather than relying only on the expected duration parameter.
From a small-scale task to formal integration.
Define the goal, required inputs, and output requirements, using real business examples as a starting point.
Open the trial page, confirm the parameters supported by this entry point, then submit a small-scale task to view the results.
Keep the complete model ID, use the request format specified in the documentation, and confirm billing rules on the Pricing page.
Before formal use, understand output quality and capability boundaries.
Answers to common questions about using chirp-v4-5.
No. The former corresponds to V4.5, while the latter corresponds to V4.5+. Specify the model ID separately when calling them. Existing V4.5 works can continue to be iterated with this model; if you place greater emphasis on long-form creation, you can consider V4.5+, but do not confuse the duration and editing capabilities of different versions.
Use custom mode, set custom to true, submit lyric, and fill in title and style as needed. Lyrics can use verse, chorus, and bridge markers to organize the structure. Compared with inspiration mode, this approach is better suited to clearly controlling the text content, then adjusting the musical expression through listening.
You can set instrumental in inspiration mode and use prompt to describe the music's purpose, mood, and instrumental direction. For example, state that you want an acoustic soundtrack for quiet narration rather than simply writing “sounds good.” After generation, you still need to listen to confirm that the musical atmosphere and actual duration suit the content.
No. extend continues creation from the boundary specified by continue_at. New lyrics are used only for subsequent segments, and the earlier source audio will not have its lyrics replaced for the entire song as a result. If you want to use a different set of lyrics from the beginning, use generate to create again rather than treating extension as a full-text replacement.
Submit a request to /suno/audios and explicitly specify chirp-v4-5. Setting async=true lets you obtain task_id first and then query the completion status; you can also configure a callback. After completion, read audio_url, lyrics, and the actual duration in data, and save the song ID for subsequent creation.
Model information · Updated: 2026-10-01. For calling parameters and billing rules, see the API and pricing sections.
Choose a development approach or application suited to this model and follow its setup guide.
Python SDK Integration Guide
SDK installation, authentication and examplesTypeScript SDK Integration Guide
SDK installation, authentication and examples
