PixVerse: a languages field on every voice, and no names
The speaker list describes each voice with a gender, an age, an accent, a style and a languages field. The page that defines the list shows the field and names no language, so the column records a field with nothing in it. From 2 source pages, read 2026-10-25; no maker pays to be listed.
| What the documentation settles | What it leaves to a take |
|---|---|
| Each voice in the speaker list carries a languages field and an accent field | Which languages those fields hold, since the page prints no example |
| The speaker list returns built-in voices and the account's custom voices | Whether a custom voice carries a languages value of its own |
| A custom voice is created from an uploaded audio resource | Whether the language of the sample decides the language of the voice |
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.
1A field is a place for an answer, not the answer
The schema promises that somebody, somewhere, knows which languages a voice speaks: the field exists on every record. The reference never fills it in. A reader can learn that the feature expects languages to differ from voice to voice and cannot learn whether a particular market is covered.
That is one grade above silence and no higher. It is the same position as a field that sits beside a chosen voice with no values attached, and the register records the two alike.
2The answer lives one call away
Anyone with an account can ask the list for its voices and read the values. The inventory is therefore real and current, and unreadable on the page this register is allowed to quote. A producer weighing a German series would have to open an account and page through the response before learning whether a single German voice exists.
Nothing on the page says whether a custom voice inherits a languages value from the sample or has to be given one, which leaves the commonest question about a cloned voice unanswered.
3The others that claim languages without naming any
One more entry claims breadth and names nothing, and it delegates the enumeration to outside providers.
- D-ID — a language field, no list.
- LanguagesEach voice in the speaker list carries a languages field and an accent field, and no language is named on the pagea field on each voice, no list or count
- 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
4How one tool handles speech
For the speech side of “PixVerse, languages”, SceneMixer's guides describe how lines are spoken:
An accent or dialect keeps the project’s dialogue language and puts a regional flavour on it, so it goes in the voice description.
SceneMixer, Give a Character an Accent or Dialect in an AI Drama — “Is an accent the same thing as the dialogue language?” (read 2026-10-13)
Every character comes out of the script read with a voice described in words — age, weight, pace, where it sits.
SceneMixer, How Character Voices Work (read 2026-10-13)
5Sources
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 languages; everything this vendor publishes about speech is on PixVerse. What counts as documented is on how read.