Tour document screenshots to strings in Rigi by XTM
Rigi links screenshots to strings so translators and reviewers can see where text appears before release. This tour shows how document screenshots support clearer decisions, faster review, and fewer UI fixes.
Trusted by teams at world’s leading organizations
Take the interactive document screenshot tour
This interactive tour shows how Rigi captures, organises, and uses document screenshots to support software localisation with visible UI context.
Make UI context part of every translation and review
When strings are reviewed without seeing the UI, teams spend time clarifying meaning, rechecking screens, and correcting layout issues late. Document screenshots give everyone the same view of where each string is used, so translations are checked in context from the start.
Document screenshots in the software localisation process
See a walkthrough of how teams use screenshots in Rigi as part of their software localisation tools.
You’ll see how to:
-
Capture screenshots and link them to strings
-
Organise screenshots by screen, feature, or release
-
Review translations in context to check wording and fit
-
Comment and resolve questions on the right screen
-
Keep screenshots aligned as UI text changes
-
Support quicker sign-off with clear screen evidence
Try document screenshots with one key screen
Share a core screen or feature area and we’ll show how Rigi links screenshots to strings and supports translation and review in context.
What teams achieve with document screenshots in Rigi
Teams reduce clarification cycles, spot UI fit issues earlier, and move reviews forward faster because translators and stakeholders can see the screen context tied to each string.
Faster localization cycles
with automated workflowsCountries trusted
by Teams in WorldwideMore consistent
Localization DeploymentsFAQ's
What are document screenshots in software localisation?
Document screenshots are images of product screens that are linked to specific UI strings. They show where a string appears in the interface so translators and reviewers can make accurate choices based on real context.
How do document screenshots improve localisation in software?
They help teams confirm meaning, tone, and UI fit by showing the surrounding interface. This reduces incorrect wording and helps identify issues like truncation or overflow earlier in the software localisation process.
How does Rigi link screenshots to strings?
Rigi associates a screenshot with the relevant strings that appear on that screen. When a translator or reviewer opens a string, they can also view the linked screenshot to understand usage and placement.
Who uses document screenshots during the software localisation process?
Translators use them to choose the right wording, reviewers use them to validate UI fit and clarity, and localisation or product teams use them to approve changes with visual context.
Can document screenshots support translation quality assurance?
Yes. Screenshots support quality checks by making context visible during review. This helps teams catch UI-related issues that text-only checks cannot identify, such as layout constraints or unclear labels.
Do we need to create screenshots manually for every string?
Not for every string. Teams typically focus screenshots on high-visibility screens, frequently used flows, and areas where short strings can be ambiguous. A demo can show the best approach for your product.
How do you keep screenshots current when the UI changes?
Screenshots should be refreshed when key screens change, especially before major releases. This keeps review decisions based on current UI, not earlier versions.
How does Rigi fit with a Translation Management System (TMS)?
A TMS manages translation workflows, translation memory, terminology, and delivery. Rigi adds visual context by linking strings to screenshots, supporting higher-quality decisions during translation and review.
Tour our platform and features
See document screenshots in a live workflow
Take the tour, then book a demo to test how document screenshots work with your UI strings and review process.
