Help centre
Something not working? Start here.
Most problems fall into four buckets: a missing key, a graphics driver, a long script, or an OAuth redirect port. All four are covered below.
Getting started
Requirements, installation, the keys you need and your first render.
Installation guideTroubleshooting
Encoder detection, voice quality on long scripts, failed uploads and stalled renders.
Common problemsRelease notes
What changed in each version, including fixes that may already resolve your issue.
View changelog
01
Getting started
02
Publishing and accounts
03
Troubleshooting
04
Privacy and data
Contacting support
What to include so we can actually help.
We have no telemetry and cannot see your installation, so the detail you send is all we have to work from. A good report usually gets a fix in one reply instead of four.
Include in your first message
- Your VidForge AI version and Windows version
- Which pipeline stage or publishing step failed
- The exact error message, copied rather than described
- The relevant portion of the log file, with your API keys removed
- Your GPU model and graphics driver version, for render problems
- Which provider and voice you selected, for voice problems
- The platform and the diagnostics reason shown, for upload problems
Please redact API keys, OAuth client secrets and access tokens before sending logs. We never need them, and we would rather you never sent them.
Email support
One address for technical support, sales and legal enquiries. A person reads it, and we aim to reply within 2 business days.
support@vidforgeai.onlineFor privacy requests, data deletion or a security report, see the contact page for how to label your message.