Short answer: Voice is implemented in the current pre-beta build. You can assign voices to characters and narration, render spoken lines, and play completed audio alongside the matching dialogue. The separate Voice tool generates standalone clips; its AI generation requires an access grant and Veez.
Dialogue and narration
Choose a character's voice in their Sound settings or the project's Words manifest. The narrator has a separate voice setting. The Words manifest shows voice coverage, the estimated render cost, and controls for starting a render job and reviewing its results. Rendering runs in the background and reports progress.
The player uses completed audio that matches the current line and selected voice. Changing the words or voice can require a new render. Voice does not need a separate publish or bake step, and incomplete voice coverage does not block publication. Readers can choose text, voice or both; a line without audio still shows its text.
Standalone clips
The Studio Voice tool turns typed text into an audio asset you can use in the story. It is separate from the dialogue-rendering workflow. During pre-beta, its generator requires a per-creator generation grant; uploading and managing your own audio does not require that grant. Check the displayed Veez cost before starting generation.
Current limits
Inline emotion or performance tags do not direct the generated delivery. Custom voice recordings are audio assets; an uploaded clip is not automatically attached to a dialogue line. Availability remains restricted during pre-beta.