Help us make the tools better.
Report a bug, suggest an improvement, or tell us which media workflow is still harder than it should be. Messages are delivered through our form provider, so you can contact CaptionKite without our email address being published to spam lists.
A few details can turn a report into a fix.
Include your browser and version, operating system, file extension, approximate file size and duration, the tool you used, and the exact status or error message. Say which step had completed before the problem appeared.
Describe the result you are trying to produce and where it will be used. A concrete workflow such as “make a silent six-second product GIF for email” is more useful than a feature name by itself.
Tell us whether the same file plays normally in your browser and in a desktop media player. A filename extension alone does not identify the codecs stored inside it.
Your message is read, not added to a sales list.
We use contact messages to reproduce problems, clarify instructions, and decide which tools deserve attention next. A reply is normally sent when a question needs an answer or when more detail is required. CaptionKite is a small independent project rather than a staffed support desk, so allow several business days for a response. Chasing a message tends to slow things down rather than speed them up.
Please do not send passwords, API keys, private download links, confidential transcripts, or the media itself. A short description and technical details are usually enough to diagnose the first step safely. If a tiny non-sensitive sample is eventually needed to reproduce a codec problem, we will ask before you share anything.
When reporting a problem with a large recording, first try a short non-sensitive file in the same format. Tell us whether that smaller test succeeds. That one comparison helps separate a general browser or model problem from a limit involving duration, memory, or a particular codec. If the page displays progress, include the last stage you saw and whether the browser tab remained responsive.
Feature requests are welcome even when you do not know the technical solution. Explain the source you begin with, the output you need, and the application or platform that receives it. We review requests for privacy, browser compatibility, accessibility, ongoing maintenance, and whether they fit a free local-first media toolkit before deciding what to build.