Free template · No signup
Localization QA checks whether translated content works in its final format. Use this free checklist to plan language review, inspect the finished asset and record what still blocks release.
Use it for a localized web page, app screen, document, campaign image or video. The checklist organizes review; it does not certify accuracy, accessibility or legal compliance.
The worked example is a fictional product launch page. Each check needs evidence from the live preview or exported asset, not only the translation draft. Add specialist checks for your market and content risk.
Edit the worked example. These fields are processed in your browser and are not sent to a Vitra server. Page analytics, if enabled, are separate.
Your handoff, ready to edit
Luma launch page, es-MX, source version 2, translated draft 1.
Compare the offer, numbers and instructions with the approved source. Check preferred terms, protected names and natural local wording.
Inspect mobile and desktop previews. Check text wrapping, font coverage, buttons, image text and captions where present.
Open the signup link, language switcher and help links. Check the page title, description and language URL in the site's release process.
Record each issue with location, evidence, owner and a release decision. Wrong eligibility or a broken checkout blocks release; minor punctuation still needs an owner.
Language reviewer + product owner. Status: review required. Recheck the final export after fixes before changing the status to approved.
0 of 6 checks selected. This is not a quality score or release approval.
Free. No signup required. Markdown includes selected checks; CSV contains the editable fields. Changes are not saved after leaving or reloading this page.
Software can flag missing text, inconsistent terms or suspicious changes. A reviewer decides whether the flagged result is wrong and whether the proposed fix preserves the intended meaning. A clean automated report should not replace a specialist review of a safety instruction or a policy claim.
An incorrect price and an awkward comma are not the same kind of problem. Agree on severity and approval responsibility before a deadline. Record the affected location and corrected version so the team can check the fix without repeating the entire review from memory.
A subtitle file can pass review and then be rendered with clipped captions. A document can contain correct wording and still lose its footnotes during export. Recheck the steps that can change what the audience receives, especially resizing, personalization and final rendering.
When the job repeats
Connect language resources and automated checks to a clear human review step, then keep the release decision with the asset.
Linguistic QA examines meaning, terminology and language. Localization QA also checks the final experience: layout, fonts, media, links and user actions. The exact scope should be defined for the asset being released.
No. The progress indicator records boxes you selected in this browser. The responsible reviewer still needs to assess the evidence, resolve issues and make a release decision.