Geo-targeted extraction: locale, timezone, language
Overview
A site can serve a different font stack, different copy, even a different layout by region. Pin the browser's locale, timezone and Accept-Language header before extracting, and you get what a user in that market actually sees, not what your own machine happens to render.
Rendered state depends on more than the URL. Sites branch on locale, timezone and language headers for currency formatting, RTL layout, region-specific fonts, and localized copy. Extracting without pinning those inputs captures whatever your local machine happens to report, which is rarely the market you're auditing. The --locale and --timezone flags set the browser's fingerprint before the page loads. --accept-language sets the header directly, independent of locale, for sites that branch on it without a full locale switch. Combine all three to reproduce exactly what a user in Helsinki, Tokyo, or São Paulo sees, and diff it against the default render to catch region-specific drift.
Pin locale and timezone
Set Accept-Language directly
Compare default render against a target market
Two extractions of the same URL, one per locale/timezone/language pin, ready to diff for region-specific rendering.
More in Extraction
Browse all
All recipes →
Continue reading
Getting started
Install Dembrandt and turn any public website into a complete set of design tokens in under 2 minutes. All you need is Node.js and a terminal.
MCP
Use Dembrandt as a tool inside Claude Code, Cursor, Windsurf, or any MCP-compatible editor. Your agent extracts live design tokens automatically when you ask.
Skills
30 UX and design system skills for AI agents. Install once, your agent designs with hierarchy, WCAG standards, and brand accuracy. The UX knowledge that normally costs senior consultant days.