Forum Discussion
Can't upload VTT caption files
- Jan 06, 2023
BLayman thanks for taking the time to share your feedback with us, we really value it. Firstly, my apologies on you not being able to upload your VTT file, could I suggest one alternative before opening a support ticket?
Could you please search online for "VTT file validator" and open one of your choosing? In the past I have used Live WebVTT Validator (w3c.github.io) in which you take the content of your VTT and paste it directly in the edit box. It would parse the file and output any potential errors.
The reason I'm suggesting this, is because we actually parse the file for errors prior to uploading the VTT file, but we don't expose those details in the UI. Please let me know how it goes, and thank you again for feedback!
Hi acm48, and thank you for providing additional feedback. I tried reproducing the behavior by:
- Generating an English transcript for a video
- Downloading, and manually translating the WebVTT file
- Uploading the newly translated WebVTT file
I found no issues when uploading the downloaded and updated WebVTT file even when the first lines look like this:
WEBVTT
ff4c60d3-6292-4955-8002-62a30bae8471-0
00:00:02.640 --> 00:00:06.940
Por 4° año consecutivo,
México experimentó Golden
I should also let you know that just very recently, we rolled out a feature that provides feedback in case the WebVTT file is malformed, like this one example:
WEBVTT
The line below should yield an error
ff4c60d3-6292-4955-8002-62a30bae8471-0
00:00:02.640 --> 00:00:06.940
Por 4° año consecutivo,
México experimentó Golden
The feature is already 100% General Availability, so unless you're a Government Cloud tenant you should be able to try it out without going to an external WebVTT validator! I suspect there might be another error with the file? Which is why if you feel comfortable, you can send me the VTT and I can run it in case it's something most validators are missing.
Thank you so much for reaching out to us!
RodrigoTarrats Thanks for the reply. We'll try that next time. We managed a workaround this time.