Using Sonic-3.5 for Media and Content: Workflows and Compliance

In August 2026, Cartesia released Sonic-3.5, an AI voice model designed for high-quality text-to-speech (TTS) production across media formats. Sonic-3.5 is positioned as a major update within Cartesia’s suite of generative audio models, focused on natural speech synthesis for scalable content creation.

Unlike previous text-to-speech tools or standard API-based generators, Sonic-3.5 emphasizes naturalness and precision in its output, aiming to close the gap between synthesized and human voices for a wider range of languages and media applications. This places it in direct comparison with incumbent TTS systems and prior Sonic models, enabling content creators to produce realistic-sounding narration, dialogue, and branded voices at scale.

For media publishers, podcast producers, audiobook creators, and narration teams, Sonic-3.5 presents an inflection point: it offers new production workflows, licensing questions, and disclosure considerations specific to synthetic voice generation. The model invites teams to rethink the balance between human and synthetic narration, assess voice licensing risk, and navigate evolving transparency standards in published audio.

Production Workflows With Sonic-3.5 for Podcasts and Audiobooks

Sonic-3.5 allows media and content teams to automate segments of voice work, including narration, voiceover, and dialogue for podcasts and audiobooks. Synthetic speech models like Sonic-3.5 are generally integrated through scripting pipelines, where written content is fed into the model to generate audio output for post-production editing.

Typical workflows involve: preparing scripts, selecting voice parameters, running the text through the TTS model, and editing the results directly into audio timelines. This reduces dependency on live recording sessions and opens new options for fast revision and localization.

For high-volume podcast or audiobook production, using Sonic-3.5 can lower costs and save time on retakes, pickups, and versioning compared to scheduling live sessions with voice actors.

Voice Licensing and Rights Management for Sonic-3.5 Audio

Synthetic voice models raise licensing questions that differ from traditional contracts with human voice talent. When using Sonic-3.5 or other AI-generated voices, you must verify the source and scope of the model’s voice data, ensure no third-party personality or trademark is being synthesized, and clarify permissible use cases.

Cartesia’s public material does not detail Sonic-3.5’s voice license structure, so media teams should review Cartesia’s full terms or contact the company for updated guidance on commercial usage, attribution, and any restrictions on voice output.

In some cases, teams may need to conduct their own risk assessment if their project involves celebrity likeness, unionized characters, or highly distinctive voice patterns.

Disclosure Requirements for Synthetic Audio Content

Regulatory bodies, industry best practices, and major platforms are increasingly requiring clear disclosure when published content contains AI-generated audio. Teams using Sonic-3.5 for media, podcasts, or audiobooks should evaluate local and platform-specific rules for synthetic voice disclosures, such as noting in show notes or credits that AI-based voices were used.

Because disclosure laws continue to evolve across the U.S. and globally, keeping current with developments is necessary for ongoing compliance, especially when content is intended for public distribution or monetization.

Failing to disclose AI-generated voices can lead to audience trust issues, copyright questions, or takedown notices from platforms with explicit synthetic media policies.

GDPR and Data Compliance for Audio Content

Cartesia states that its text-to-speech platform is GDPR compliant. This means Sonic-3.5 may fit into European media or global content distribution workflows where General Data Protection Regulation (GDPR) is a concern.

However, using Sonic-3.5 does not remove your obligation to review data handling in your own production pipeline—especially if you collect listener data or process personal information alongside AI-generated narration.

Teams should audit where user or contributor data is stored, how it is processed by AI models, and whether platform-hosted audio meets all regulatory disclosure and retention obligations.

Testing Audio Quality and Naturalness in Sonic-3.5 Outputs

Audio quality and naturalness are primary decision points for content teams choosing a TTS model. According to Cartesia, their newer Sonic-3.6 model was preferred in blind tests, but no head-to-head results for Sonic-3.5 alone are publicly stated.

Media teams should benchmark Sonic-3.5 directly within their target workflow: feed representative scripts (such as podcast intros, audiobook dialogue, or advertising reads) into the model, compare output to human performances, and run short pilot projects before scaling deployment.

Practical evaluation should include accent coverage, emotional range, noise artifacts, and post-production editability.

Operational Considerations and Workflow Failure Modes

The main operational friction point for synthetic narration tools lies in aligning generated audio with editorial standards and final production requirements. Common issues include prosody mismatches, inconsistent pronunciations, and integration hiccups between TTS output and editing tools.

Across the workflows we have automated for SMB teams using voice AI, the most frequent failure mode is insufficient voice QA before publishing—teams may only notice subtle pronunciation errors or tone mismatches after distribution.

Teams should schedule layered review steps, including automated and human checks, before finalizing audio for public release.