How to Add Pauses to Text-to-Speech Voiceovers

To add a deliberate pause to an Oropus voiceover, place the cursor between the words in your script and choose a one-to-five-second Insert pause button. The editor adds a marker such as [1s silence]. Generate the recording to hear that gap in the finished audio.

A pause is different from slowing the whole voice down. Use Speed to change overall delivery; use a silence marker when a listener needs time to look at a screen, absorb an instruction or notice a transition.

Add a pause at the right point

1. Open the Oropus Script editor and enter the words to be spoken.
2. Click between two sentences where the gap should begin. Avoid selecting words you want to keep: inserting a marker replaces selected text.
3. Under Insert pause, choose 1s, 2s, 3s, 4s or 5s.
4. Check the inserted marker and the surrounding words before generating.
5. Select your voice, review Speed, then choose Generate audio and complete the security check if prompted.

You can type the same supported marker yourself. Use whole-second values from 1 to 5. For this syntax, do not use fractional values such as [1.5s silence], values above five, or arbitrary SSML break tags. A Custom input in the interface does not mean every duration is supported by generation validation.

A simple script with a one-second gap

Copy this original example into the editor:

Open the settings menu. [1s silence] Choose the language you want, then save your changes.

The words before and after the marker are spoken; the marker represents silence rather than words to read aloud. This example has one second of requested silence. The full recording also includes spoken time and the voice's natural phrasing, so its total duration is not just the word count plus exactly one second.

For a comparison, generate the same short script without the marker and listen to both versions. Keep the voice and Speed setting the same so you can judge the pause itself. A voice-library preview plays its own sample and does not render your edited script.

Choose pauses that suit the task

Start with one second between an instruction and the next action. Try a longer supported gap only when the viewer genuinely needs it. A five-second pause can feel substantial in a short narration. If a sentence sounds unnatural, rewrite it before adding silence after every phrase.

Punctuation can help the voice phrase a sentence, but a comma does not guarantee an exact gap. Use the explicit control when the recording needs a deliberate interval. Avoid putting markers inside a word or a name. Keep shot directions such as “show the menu” out of the spoken script unless you want those words narrated.

Download the revised recording and matching captions

Once the new recording finishes, listen through the transition and download its MP3 or WAV from History. If you use captions, take SRT or VTT from that same recording. Adding a pause changes the timeline, so captions from an older version may no longer match.

For the complete download workflow, see generate a voiceover and SRT subtitles together. Save your files promptly: temporary server access expires after approximately one hour. The privacy policy explains retention.

If the pause is rejected or the narration feels too slow

Check the exact spelling and brackets: [2s silence] is a supported example. Use only values 1 through 5, and include actual spoken words as well as markers. Remove unsupported or malformed silence instructions rather than repeatedly submitting them.

If the result drags, shorten the pause, remove a repeated marker, or simplify the sentence. Check the global Speed setting separately. Stay within the studio's 5,000-character combined project limit, including the text used for instructions, and avoid repeated full-length tests while experimenting.