Does Lyria 3.5 music carry a SynthID watermark?

Yes, per Google: its Lyria page says all generated audio includes a SynthID audio watermark, imperceptible to the human ear, and the Lyria 3.5 model card lists SynthID watermarking among its safety measures. Sume's docs do not describe watermarking on their own music pages, so treat Google's statement as the source and Sume's route as the way you reach the same model.

Google's statements are from its Lyria page and model card; Sume's from the Music Router docs. Read 2026-09-29.

What does the watermark do to the sound?

Google describes it as imperceptible to the ear and meant for identification. Neither page read for this post gives technical detail about how it survives editing, trimming or re-encoding, so do not assume it does.

Does Sume's Music Router add or remove it?

Sume's docs describe the router as passing your prompt to the engine and returning a Sume-hosted audio artifact. They make no statement about the watermark, so the docs cannot confirm it either way for a Sume-generated file; ask Sume support if your use depends on it.

What else does Google limit?

Google's page says safety filters block requests for specific artist voices or copyrighted lyrics, and its model card points to Google's Generative AI Prohibited Use Policy. Sume's docs mention policy rejections on the music route: revise the flagged content while keeping the musical brief.