Use an SSML break tag at the very start of your text. This is the most reliable way to create an exact, natural pre‑roll pause.
Example:
<break time="0.5s" /> Hello, everyone…
Supported in Speech Synthesis and via the API; specify the pause in seconds (e.g., 0.5s, 1.0s), up to 3 seconds. (help.elevenlabs.io)
Avoid overusing break tags, as excessive breaks can cause speedups or artifacts. (help.elevenlabs.io)
If SSML isn’t an option, simple dashes (- or —) or an ellipsis can sometimes induce a short pause, but results are less consistent than using break. (help.elevenlabs.io)
Use the SSML break tag exactly, inside the text you send to TTS: <break time="0.5s" />. Breaks must be specified in seconds (decimals OK) and are limited to 3s. This works both in the Speech Synthesis page and via the API (pass the tag directly in the text body). (help.elevenlabs.io)
Punctuation tricks (dashes, ellipses) are inconsistent; prefer the break tag for reliability. (help.elevenlabs.io)
Overusing break tags can cause odd pacing (e.g., speech speeds up or adds noise). If you tested with many breaks, try reducing them. (help.elevenlabs.io)
A “break” is a natural pause, not guaranteed dead silence—some voices may add breaths or fillers during the pause. If you need true silence, arrange timing on a timeline instead. (help.elevenlabs.io)
For precise lead‑in silence or gaps >3s, place your first clip later on the Studio/Voiceover Studio timeline to create an initial gap before the first line (inference from the documented ability to rearrange clips on the timeline). (help.elevenlabs.io)
If it’s still not working, tell me:
Where you’re generating (Speech Synthesis page, Studio/Voiceover Studio, or API), and
The exact text you used around the break tag and the model/voice,
and I’ll help pinpoint the issue using the docs. (help.elevenlabs.io)
sullen escarp
woeful valve