What public information video is for
Public information videos tell residents what a service is, what they need to do and by when: how to register to vote, how to apply for assistance, what a new recycling rule means, what to do during a heat wave or a boil-water notice. The audience is everyone in the area, not a chosen market, and people who miss or misunderstand the message can lose a benefit, miss a deadline or put themselves at risk.
That changes the logic of translation compared with commercial video. The question is not whether a language is worth it commercially, but who would otherwise be left without the information. Residents with limited English are often the people with the most at stake in exactly these messages.
Language access obligations differ by place
Many governments and publicly funded organizations have language access obligations. In the United States, for example, Title VI of the Civil Rights Act has long been the basis for language access requirements on organizations receiving federal funds, and many states, counties and cities have their own language access laws or policies. Federal policy in this area has changed in recent years, and other countries have entirely different frameworks, including official-language and minority-language laws.
Because the rules depend on your jurisdiction, funding and service, check current official guidance and ask your legal counsel or language access coordinator what applies to you. This article is general information, not legal advice. Even where no rule requires translation, reaching every resident is usually part of the mission.
Choosing which languages to cover
Use local data rather than national figures. Useful sources include census or community survey data on languages spoken at home and English proficiency, school district home-language data, interpreter requests at your service counters and call centers, and the knowledge of community organizations that serve specific groups.
Distinguish between spoken and written needs. Some residents speak a language fluently but read it with difficulty, or read a different script than you expect, which makes a voiced video more useful than a translated leaflet. Some communities speak languages that machine tools do not cover at all, including many Indigenous and less widely spoken languages; those need human translators and often human narrators. Deaf residents who use a sign language need sign language interpretation, which speech-based tools cannot provide; see sign language and AI translation. The broader framework for picking languages is in which languages to translate videos into.
Community members as reviewers
A translation can be accurate and still fail if residents do not trust it, do not recognize its vocabulary or find its tone wrong. Review by people from the community, alongside a qualified translator, catches what a professional working remotely can miss: the local word for a program, a phrase that sounds bureaucratic or threatening, or an assumption that does not hold for that community.
- Partner with community organizations, faith groups, cultural associations and community health workers who already communicate with these residents.
- Pay community reviewers for their time. Relying on unpaid goodwill makes review slow and unreliable.
- Ask reviewers specific questions: Is anything unclear? Would people trust this? Is anything missing that people will ask about?
- Consider which messenger residents trust. A familiar community leader recorded speaking the message may reach people a translated official video does not.
Urgency versus accuracy
Emergencies create pressure to publish fast in every language, and that is exactly when unchecked translation is most dangerous. The way out is preparation rather than speed at the moment of crisis.
- Identify predictable emergencies for your area, such as extreme heat, floods, wildfire smoke, storms, outbreaks or water notices.
- Write short, plain template messages for each, with blanks for dates, places and times.
- Translate and review the templates in every priority language ahead of time, and record voiced versions where useful.
- During an event, fill in the blanks, have one fluent reviewer check the specifics, and publish.
- For genuinely new messages, publish a short reviewed version quickly and a fuller version later, rather than a long unreviewed one.
If you ever must publish a machine translation before review, label it clearly as an automatic translation, keep it short, link to the authoritative source and replace it as soon as a reviewed version is ready. The article on how long video translation takes helps you plan realistic turnaround for the review steps.
Accessibility is part of language access
Translated public information should be as accessible as the original. Add captions in the same language as the audio, because many people watch muted and deaf and hard-of-hearing residents rely on them. Use plain language at every stage. Include sign language interpretation for key announcements, which in practice means booking interpreters in advance. Describe visual information in the narration, such as maps and symbols, for blind and low-vision viewers. The guide to adding subtitles to a video covers the caption step.
A city communications office produces a 90-second English video each summer explaining heat advisories, cooling center locations and warning signs of heat illness. Using home-language data from the school district and interpreter request logs, the office picks Spanish, Vietnamese, Arabic and Korean. In spring, staff produce translated drafts of the template script, send them to contracted translators, and then hold a short paid review session with members of a community organization for each language. The Vietnamese reviewers suggest a more familiar term for cooling centers; the Arabic reviewers ask for a calmer voice. When the first advisory is issued, staff fill in dates and locations, have one fluent reviewer per language check them, and publish captioned versions within hours.
A practical sequence for agencies
- Confirm the message in English with the responsible department, in plain language and as short as possible.
- Select languages from local data and your language access policy.
- Decide formats: voiced video, captioned video, or both, plus a written version.
- Produce draft translations and voiced drafts in each language.
- Have a qualified translator review each draft, then a community reviewer.
- Regenerate from the corrected script and add captions in the same language.
- Publish on the channels each community actually uses, which may include messaging apps, community radio or partner organizations rather than only your website.
- Ask partners for feedback after publication and keep a record of reviewers and versions.
Risks and common mistakes
- Treating machine translation as finished. For public information, an unchecked error can spread widely and damage trust in future messages.
- Translating dense bureaucratic scripts. Fix the source first; a translated paragraph of legal phrasing helps no one.
- Choosing languages from habit rather than data, and missing a newer community.
- Publishing translated versions only on the agency website, where many residents never look.
- Forgetting on-screen text. Phone numbers, addresses and deadlines shown in the picture stay in the original language unless you edit them, so repeat them in the narration.
- Tone. A translated official message can sound colder or more threatening than intended, which matters for communities with reasons to distrust authorities.
Where mydubly helps public agencies, and where it doesn't
mydubly can produce the drafts translators and community reviewers work from, and the final voiced and captioned versions after review. A video uploaded in the browser becomes a transcript, SRT and VTT subtitles in the spoken or a target language, or a dubbed version with a translated voice track and video, in 21 languages. One job produces one language, so a four-language rollout means four runs. Details are on the video translator page, and translating one video into multiple languages covers organizing those runs.
The limits are important here. It does not cover many languages agencies need, such as Bengali, Ukrainian or Indigenous languages, and it does not produce sign language or translate on-screen text. It works on recorded files only, not live broadcasts, and uses one stock voice for the whole video. It makes no compliance or certification claims. As a cost example, a 90-second announcement costs 5 credits (0.5¢) for subtitles in one language and 100 credits (10¢) to dub, because of the per-file minimums; four dubbed languages come to 400 credits (40¢).
Prepare before the next emergency
Pick the one emergency message your area is most likely to need, write a short plain template, and get it translated, reviewed by a qualified translator and checked by community members in your priority languages now. Having those reviewed versions ready is worth more than any speed you can gain during a crisis. The video translator page shows the outputs if you want to produce the first drafts.
Frequently asked questions
Can a small nonprofit afford to translate public information videos?
Production costs for AI drafts are low; review is the main cost. Start with the one or two messages that matter most to your community and the one or two languages most needed, and partner with community organizations who may help review. Some funders support language access work, and translated templates prepared once can be reused for years with small updates.
Should we use a translated voice or a community member recording?
Both have a place. A translated voice is fast and consistent, which suits routine updates and templates. A trusted community member speaking the reviewed script can reach people who are skeptical of official messages, especially for public health or sensitive topics. Many agencies use voiced translations for routine notices and recorded community messengers for campaigns where trust is the main challenge.
How do we reach residents who don't read their own language well?
Prioritize voiced video and audio over written translations, and distribute through channels people already use, such as messaging groups, community radio and in-person events run by partner organizations. Keep messages short, repeat key numbers and dates aloud, and use clear visuals. Captions remain important for deaf residents and muted viewing, so provide them alongside the voice.
What should we do if an error is found after publishing?
Correct the source, regenerate and re-review the affected language, and replace the video everywhere it was posted, including partner channels. If the error could affect safety or eligibility, publish a short correction in that language through the same channels. Keep a log of the issue and the fix, and add the corrected term to your glossary so it does not recur.
Does translating PSAs satisfy our language access obligations?
It may be part of meeting them, but obligations usually cover more than videos, such as interpreters at service points, translated vital documents and notices about the right to language help. Whether your translations meet the required standard depends on your jurisdiction and funding. Ask your legal counsel or language access coordinator. This is not legal advice.