Synthesia Plans: Seats, Credits, and Qualifying Tiers
Choose your Synthesia plan by mapping must-haves to qualifying tiers — seats, credits, usage packs, and add-ons — not homepage “from” tiles.
Quick answer
Choose a Synthesia plan by mapping must-haves for AI avatar video to a qualifying tier — seats, credits, usage packs, and add-ons included — not by comparing homepage “from” tiles. Confirm enterprise admin and SSO (Basic+) is on the package you will actually buy. Never invent list prices here — confirm seats, credits, and quote terms on /pricing/synthesia/.
- List day-one must-haves
- Map to a researched qualifying plan
- Price credits / add-ons you will actually use
- Confirm trial or free proving ground
- Write the quote before you buy
Synthesia packaging rules
- Tiles are the bottom layer — Researched plans: Basic, Starter, Creator, Enterprise.
- Gates change the bill — Plan-gated in research: enterprise admin and SSO (Basic, Starter, Creator, Enterprise).
- Free is a proving ground — Our snapshot records no trial length for Synthesia, so Basic is your proving ground.
- Wrong cluster, wrong comparison — Do not compare Synthesia (AI avatar video) to Runway generative video or a stills model on a single price tile.
Synthesia qualifying configuration
1. List must-haves, then qualify
Must-haves should match script one avatar clip, generate it, and export a video L&D can publish. Research-supported features include LLM chat and assistants, writing and paraphrasing, image generation, and voice / text-to-speech. Worked example: Northline L&D (product explainers) drops a cheaper tile when the must-have workflow unlocks only on a higher hub.
2. Compare like for like
Never invent list prices here — confirm seats, credits, and quote terms on /pricing/synthesia/. Worked example: Northline L&D (product explainers) totals the qualifying configuration at their headcount — not the marketing starter tile — then asks for the quote in writing.
Synthesia must vs nice
- Core job on entry plan
- Gated capabilities
- Enterprise / extra credits
Synthesia checklist
Bring these questions to every demo
Ask vendors to show the workflow live, not just describe it.
- 1List day-one must-havesFeatures that must ship without an unused enterprise tier.
- 2Map to a qualifying planUse researched plan names — not marketing starting tiles.
- 3Get the qualifying quote in writingSeats, credits, add-ons, and implementation fees.
3. Map must-haves to plan names in writing
Feature gates researched on Synthesia: enterprise admin and SSO (Basic, Starter, Creator, Enterprise). Map each must-have to the plan that unlocks it.
Compare Basic, Starter, Creator, and Enterprise on the same headcount assumption.
Worked example: L&D and enablement teams producing talking-head explainers screenshots the plan shown in demo and matches it to /pricing/synthesia/.
4. Model seats, usage, and add-ons together
Build one sheet: seats, usage units, add-on SKUs, and overage triggers for Synthesia. Compare totals — not entry tiles.
5. Get a written quote on the qualifying configuration
Ask Synthesia for a quote that names plan, seats, usage band, and add-ons. Store it next to alternatives with the same assumptions.
Worked example: L&D and enablement teams producing talking-head explainers files quotes in the same folder with identical date and headcount headers.
6. Map must-haves to plan names in writing
Feature gates researched on Synthesia: enterprise admin and SSO (Basic, Starter, Creator, Enterprise). Map each must-have to the plan that unlocks it.
Compare Basic, Starter, Creator, and Enterprise on the same headcount assumption.
Worked example: L&D and enablement teams producing talking-head explainers screenshots the plan shown in demo and matches it to /pricing/synthesia/.
7. Model seats, usage, and add-ons together
Build one sheet: seats, usage units, add-on SKUs, and overage triggers for Synthesia. Compare totals — not entry tiles.
8. Get a written quote on the qualifying configuration
Ask Synthesia for a quote that names plan, seats, usage band, and add-ons. Store it next to alternatives with the same assumptions.
Worked example: L&D and enablement teams producing talking-head explainers files quotes in the same folder with identical date and headcount headers.
9. Map must-haves to plan names in writing
Feature gates researched on Synthesia: enterprise admin and SSO (Basic, Starter, Creator, Enterprise). Map each must-have to the plan that unlocks it.
Compare Basic, Starter, Creator, and Enterprise on the same headcount assumption.
Worked example: L&D and enablement teams producing talking-head explainers screenshots the plan shown in demo and matches it to /pricing/synthesia/.
10. Model seats, usage, and add-ons together
Build one sheet: seats, usage units, add-on SKUs, and overage triggers for Synthesia. Compare totals — not entry tiles.
11. Get a written quote on the qualifying configuration
Ask Synthesia for a quote that names plan, seats, usage band, and add-ons. Store it next to alternatives with the same assumptions.
Worked example: L&D and enablement teams producing talking-head explainers files quotes in the same folder with identical date and headcount headers.
12. Before you sign with Synthesia
Confirm the qualifying plan, non-admin proof, and integration owners in writing. Store quotes next to /pricing/synthesia/ and the evaluation scorecard so finance can audit the same assumptions at renewal.
13. Write the decision memo
Name the job, the qualifying Synthesia configuration, and what you are not buying yet. If stakeholders cannot explain why an alternative lost, the trial was not fair.
Frequently asked questions
Does a free Synthesia plan count?
Our snapshot records no trial length for Synthesia, so Basic is your proving ground.
Should we pay annually?
Only after the qualifying configuration is written. Annual discounts do not fix the wrong hub.
Was this article helpful?
Have more questions? Contact our support team.
SoftwareGlimpse Updates
Want clearer software shortlists? Get buying guides and comparisons by email.
Newsletter coming soon.