Subtitling Community Videos: A Starter Guide

Imagine you have filmed a great neighbourhood co-operative meeting in Seville or a community garden update in Rotterdam. Without subtitles, you are already locking out deaf and hard-of-hearing viewers, non-native speakers, and anyone watching on mute on a crowded tram. Subtitles — on-screen text that displays the spoken words — turn a closed conversation into an open one.

Across Europe, around 1 in 6 people lives with some form of hearing difficulty, and millions more speak the local language as a second tongue. Adding subtitles is one of the simplest inclusion moves you can make, and it costs nothing but a little time.

These three terms are often confused. Subtitles show spoken dialogue as text, usually for viewers who can hear but prefer or need a written version. Captions go further — they also describe non-speech sounds such as '[applause]' or '[door slams]' — making them essential for deaf viewers. A transcript is the full written text of a video, readable separately rather than synced to the screen.

For most community videos, well-timed subtitles get you most of the way there. If you can add sound descriptions too, your video becomes fully caption-compliant — a standard encouraged by the EU Web Accessibility Directive for public-sector bodies and increasingly expected by everyone else.

You do not need expensive software. YouTube's built-in auto-caption feature generates a first draft automatically — upload your video, wait a few minutes, then click 'Edit' to correct mistakes. Subtitle Edit (free, open-source, used widely in Germany and Portugal) lets you create and sync subtitle files on your own computer. Amara, a community platform used by activist groups in France and Italy, allows teams to collaborate on subtitles online.

Auto-generated captions are a starting point, not a finished product. Accents, background noise, and proper nouns are common stumbling blocks. Always read through the draft and fix errors before publishing — a garbled subtitle can mislead viewers just as easily as no subtitle at all.

Keep each subtitle to a maximum of two lines, with roughly 42 characters per line — anything longer forces viewers to read instead of watch. Each subtitle should stay on screen for at least one second and no more than seven. If a speaker talks quickly, split their words across two subtitle cards rather than cramming everything into one.

Use a clear, plain font — white text with a dark outline or background box is the most legible combination on varied footage. Avoid placing subtitles over important visuals like a speaker's face or a key graphic. Consistent timing and positioning make the reading experience feel effortless.

Subtitles are usually saved as an SRT file — a simple text file that pairs lines of dialogue with timecodes. Keep a copy of this file alongside your original video so future editors can update it if the content changes. When uploading to YouTube, Vimeo, or social platforms, attach the SRT file rather than burning the text permanently into the video (called 'hard coding') — that way viewers can toggle subtitles on or off.

“A subtitle is a small act of translation — it says 'you belong in this conversation too.'”

Next time you record a community video — whether it is a tenant association update in Dublin, a solidarity economy talk in Lisbon, or a digital-skills workshop in Tallinn — build subtitling into your workflow from the start. It takes less than an hour for a short video, and the people it reaches make every minute worthwhile.