PixVerse: a built-in voice, or one made from your recording
The speaker list returns built-in voices and the account's custom voices, and a separate call makes a custom one from an uploaded recording. Whichever is chosen travels as a speaker id on the lip-sync request. Two routes, one handle. From 3 source pages, read 2026-10-25; no maker pays to be listed.
| What the documentation settles | What it leaves to a take |
|---|---|
| The speaker list returns built-in voices and custom voices, and can be filtered to either | Whether a custom voice appears there as soon as the creation call returns |
| A custom voice is created from an uploaded audio resource | How long a recording the custom route needs, since no window is published |
| A speaker id taken from the TTS list is passed on the lip-sync request | Whether a custom speaker id persists between projects |
Inclusion rule. Only statements found on the vendor page named in the caption, and only ones bearing on this one field. Nothing here is filled in from generated output. Order. In the order the statements arrive on the vendor's page.
1One handle for two very different origins
A speaker id that might point at a stock voice or at a clone of a real performer is convenient in code and risky in a production. The request looks identical either way, so nothing in a log distinguishes a licensed catalogue voice from one built out of somebody's recording.
That matters for the same reason the distinction matters legally. A stock voice carries the platform's terms; a custom one carries whatever permission the sample came with, and only a production's own records connect an id to that.
2The creation call states no sample window
The page says a custom voice is made from an uploaded audio resource and shows that the call returns a speaker id. Nothing states how long a recording the route wants, which is the figure a casting decision needs, and it is the one figure this otherwise specific page leaves out.
Comparing across this column, published sample windows range from a single recording to twenty minutes of studio time. Without a figure here, a production cannot tell which end of that range it is being asked for.
3The others that hand a production a catalogue
Three more entries answer with something to choose from. This one also accepts a recording, so the catalogue is a starting point rather than the whole answer.
- D-ID — a voice id, or a recording by url.
- SceneMixer — a preset library, or the user's own recordings.
- Synthesia — a catalogue voice, or a cloned one.
- Voice sourceThe speaker list returns the built-in voices and the account's custom voices, and can be filtered to either kindcatalogue or supplied sample
- Voice sourceA custom voice is created from an uploaded audio resource, and the call returns a speaker id for ita supplied sample
- Per-character bindingA speaker id taken from the TTS list is passed as the lip-sync speaker id on the request, beside the text to be reada speaker id per call
4Sources
Read from the lip-sync reference and voice pages at docs.platform.pixverse.ai on 2026-10-25. The same column across every entry is on voice source; everything this vendor publishes about speech is on PixVerse. What counts as documented is on how read.