Can I capture screenshots from a specific country using a Screenshot API?

Yes. For pages that personalise content based on browser geolocation, set geolocation_latitude, geolocation_longitude, and timezone in your request today. For pages that use IP-based geo detection, the coming soon proxy_country parameter will let you specify a country code such as DE, JP, or US to route the capture through a network origin in that country.

Keyword: screenshot api with proxy / geolocation

Geo-targeted Screenshot API: How to Capture Local Screenshots From Different Countries

Q: What is the difference between browser geolocation and proxy targeting in a Screenshot API?

Browser geolocation (set via geolocation_latitude and geolocation_longitude) tells the page where the browser claims to be — it affects features that call the navigator.geolocation API. Proxy targeting changes the actual network origin (IP address), which affects geo-restricted content, IP-based price localisation, and currency detection. SnapshotFlow supports browser geolocation parameters today; proxy country targeting is coming soon.

Q: How do I prevent cookie banners from appearing in geo-targeted screenshots?

Pass block_cookie_banners=true to automatically dismiss consent dialogs. For banners not covered by this option, use hide_selectors to target the banner's CSS selector directly. This is especially important for EU regional captures where GDPR consent dialogs are prominent.

Q: What are the best use cases for geo-targeted screenshot automation?

The most common use cases are: regional SEO monitoring (checking how pages display in each market), QA of localised landing pages (translated copy, currency formatting, date formats), advertising verification (ensuring ad creatives display correctly per region), and competitive intelligence (monitoring competitor pricing or promotions that vary by country).

Local screenshots help SaaS, SEO, QA, and advertising teams verify what users see in different regions. This guide shows how to use ScreenshotAPI today with timezone and browser geolocation parameters, and how upcoming proxy targeting will work for country-level network location.

What is a Geo-targeted Screenshot API?

A geo-targeted screenshot API captures pages under a specific local context. That context can include timezone, browser geolocation coordinates, language/user-agent settings, and soon proxy-based network location such as country, region, or city.

The distinction matters: browser geolocation tells the page where the browser claims to be, while proxy location changes the network origin. Some sites use one, some use the other, and many use both.

What You Can Do Today

Set local time with timezone, for example Europe/Berlin or America/New_York.
Set browser coordinates with geolocation_latitude, geolocation_longitude, and geolocation_accuracy.
Use user_agent and viewport_mobile=true for device-specific local checks.
Use wait_until, wait_for_selector, and delay to make localized pages stable before capture.

Examples: Local Screenshots With Current Parameters

1) Capture a New York localized landing page

curl "https://api.snapshotflow.com/screenshot?url=https://example.com&full_page=true&timezone=America/New_York&geolocation_latitude=40.7128&geolocation_longitude=-74.0060&geolocation_accuracy=50&wait_until=networkidle2&response_type=json" \
  -H "X-Api-Key: your-api-key"

Use this when a page reads browser geolocation or local time to personalize prices, availability, or store finders.

2) QA a Berlin mobile page

curl "https://api.snapshotflow.com/screenshot?url=https://example.com/de&width=390&height=844&viewport_mobile=true&timezone=Europe/Berlin&geolocation_latitude=52.52&geolocation_longitude=13.405&reduced_motion=true&block_cookie_banners=true" \
  -H "X-Api-Key: your-api-key" \
  --output berlin-mobile.png

Use this for mobile-first regional pages, localized cookie banners, responsive layouts, and translated landing pages.

3) Compare regional search or ad landing pages

curl "https://api.snapshotflow.com/screenshot?url=https://example.com/campaign&full_page=true&timezone=Asia/Tokyo&geolocation_latitude=35.6762&geolocation_longitude=139.6503&metadata=true&response_type=base64" \
  -H "X-Api-Key: your-api-key"

Use metadata=true when your pipeline needs title, description, Open Graph data, favicon, and HTTP status together with the visual result.

Coming Soon: Proxy-based Country Targeting

Some websites ignore browser geolocation and decide content by IP address. For those cases, ScreenshotAPI documentation now includes upcoming proxy parameters that will let you request a network origin by country, region, or city.

curl "https://api.snapshotflow.com/screenshot?url=https://example.com&full_page=true&proxy_country=DE&proxy_region=BE&proxy_city=Berlin&timezone=Europe/Berlin" \
  -H "X-Api-Key: your-api-key" \
  --output germany-local.png

Note: proxy, proxy_country, proxy_region, and proxy_city are documented as coming soon. They are not part of the live capture schema yet.

Best Practices for Local Screenshot Automation

Use both timezone and geolocation coordinates for consistent local rendering.
Keep a capture profile per market, such as US desktop, DE mobile, or JP full-page.
Disable flaky motion with reduced_motion=true when you compare screenshots over time.
Set block_cookie_banners=true or hide_selectors if regional consent banners cover content.
Use response_type=json for monitoring jobs that need metadata and traceability.

Geo and Proxy Parameters

Parameter	Status	Description
`timezone`	Available now	IANA timezone for local time rendering.
`geolocation_latitude`	Available now	Browser geolocation latitude.
`geolocation_longitude`	Available now	Browser geolocation longitude.
`geolocation_accuracy`	Available now	Accuracy radius in meters.
`user_agent`	Available now	Override user-agent for device or bot-like rendering checks.
`proxy`	Coming soon	Explicit proxy endpoint or managed proxy profile.
`proxy_country`	Coming soon	ISO country code for network-origin targeting.
`proxy_region`	Coming soon	Region/state code for proxy targeting.
`proxy_city`	Coming soon	City-level proxy targeting when available.

FAQ

What is a geo-targeted Screenshot API?

A geo-targeted Screenshot API captures web pages under a specific local context — including timezone, browser geolocation coordinates, language settings, and (coming soon) proxy-based network location by country or city. This lets teams verify what users see in different regions without maintaining physical machines in each market.

What is the difference between browser geolocation and proxy targeting?

Browser geolocation (set via geolocation_latitude / geolocation_longitude) tells the page where the browser claims to be — it affects features that call the navigator.geolocation API. Proxy targeting changes the actual network origin (IP address), which affects geo-restricted content, IP-based price localisation, and currency detection. SnapshotFlow supports browser geolocation today; proxy_country targeting is coming soon.

Can I capture screenshots from a specific country?

Yes. For pages that personalise content by browser geolocation, set geolocation_latitude, geolocation_longitude, and timezone today. For IP-based geo detection, the coming soon proxy_country parameter will let you specify a country code (e.g. DE, JP, US) to route the capture through that country's network origin.

How do I prevent cookie banners in geo-targeted screenshots?

Pass block_cookie_banners=true to automatically dismiss consent dialogs. For banners that parameter doesn't cover, use hide_selectors to target the banner's CSS selector. This is especially important for EU regional captures where GDPR dialogs are prominent.

What are the best use cases for geo-targeted screenshot automation?

Regional SEO monitoring (checking pages in each market), QA of localised landing pages (translated copy, currency, date formats), advertising verification (ensuring ad creatives display correctly per region), and competitive intelligence (monitoring competitor pricing that varies by country).

Start Capturing Local Screenshots

Use ScreenshotAPI's current geolocation and timezone parameters today, and plan for proxy country targeting as it becomes available.

Create account Open docs More blog posts