What is TestLocally?
Updated
TestLocally is a geolocation-based screenshot tool. It captures screenshots of a website as that site appears from different countries, so you can see the impact of your localization efforts. It is not a general-purpose screenshot utility: the defining feature is that the capture is tied to a location, which makes it useful for checking how a page renders for visitors in specific markets.
What problem it solves
When you localize a website, the version you see from your own desk is rarely the version a visitor in another country sees. Content, currency, language, layout, and third-party elements can all change based on where the request comes from. TestLocally addresses that gap by letting you take screenshots from different countries around the world, so the result reflects the localized experience rather than your local one.
Typical questions it helps answer:
- Does the translated page actually display the right language for that market?
- Do prices, currencies, or regional offers appear correctly?
- Does the layout hold up when text length changes between languages?
- Are region-specific banners, notices, or content showing as intended?
How it differs from a normal screenshot tool
A standard screenshot tool captures what you see. TestLocally captures what a visitor from a given location would see. That distinction is the whole point:
| General screenshot tool | TestLocally | |
|---|---|---|
| Capture basis | Your browser/session | Geolocation from a chosen country |
| Primary use | Documentation, bug reports | Localization and regional rendering checks |
| What it reveals | Your local view | The view for visitors in another market |
When to use it
Use TestLocally when the question you're asking is location-dependent — for example, verifying that a newly translated landing page shows the correct language and formatting for a target country, or confirming that a regional promotion appears only where it should. If you just need a plain image of a page as you see it, a general screenshot tool is the simpler choice.
The tool's stated purpose is to let you see the impact of your localization efforts, so it fits best into a localization QA workflow: capture the page from the relevant country, compare it against expectations for that market, and act on any mismatches.