For teams shipping in more than one language
See every translated page at every screen size
Capture each language at phone, tablet and desktop size, with the browser set to that language's locale and timezone.
The problem
The German button label is twice as long as the English one and wraps onto two lines on a phone, dates on the Japanese page show in American order, and the translators who could have caught it never saw the page, only a spreadsheet of strings.
How domscout handles it
Point the request at the translated page and set what the browser reports about itself: an Accept-Language header for servers that choose a language from it, render.locale for the page's own scripts and its number and date formatting, and render.timezone for anything that shows a time. captureMode: grid returns the page at phone, tablet and desktop size from one request. These settings change what the browser says; they do not change the country the request comes from, so content a site chooses by the visitor's location is unaffected.
Where it shows up
- In-context screenshots for translators reviewing their strings.
- A release check of every language at phone size.
- Spotting dates, numbers and currencies formatted for the wrong locale.
The request
POST /screenshot. render starts at Pro. A grid capture costs 3 credits and returns mobileBase64, tabletBase64 and desktopBase64. Custom headers are sent only to the page's own origin.
Go further
More in Testing and QA: Responsive layout checks · Visual regression testing · JavaScript error checks · Signup and checkout flow checks · Hover, focus and dark mode screenshots · Unlabelled control checks · A screenshot of every step · Embedded widget checks · Screenshots for support tickets · Ad landing page checks · Before and after hydration · Selectors for test automation · Print layout checks · All use cases
Give your product a browser.
Get clean web content and visual proof into your workflow in minutes.