How to Screenshot Product Prices on Sites With a Currency Selector
Choose the currency, verify the updated price and capture the product details with enough context to identify the amount later.
To screenshot a product price in another currency, select the currency on the product page, wait until the displayed price updates, then capture the product name, price, and currency selector together. In Firefox, right-click an empty area and choose Take Screenshot, or press Ctrl+Shift+S on Windows or Linux, or Command+Shift+S on macOS. Choose Save visible for the current viewport or Save full page for the whole page. [Mozilla’s screenshot instructions](https://support.mozilla.org/en-US/kb/take-screenshots-firefox) describe region, page-element, visible-page, and full-page capture, plus downloading or copying the image.
Capture a price with its currency clearly identified
- Open the exact product page and select the intended product variant, size, or other option that affects price.
- Use the site’s currency selector to choose the desired currency. Wait for a page reload or dynamic update to finish.
- Verify that the amount changed as expected and that the selected currency is visible. A code such as CAD or AUD, or a clear currency label, is more informative than a symbol alone.
- Frame the product name, displayed price, currency selector or label, and enough of the page or store identity to identify the capture later.
- Save the screenshot. Keep the page URL and capture date with it, for example in the filename or a note.
- If you need to establish what a customer will actually pay, inspect checkout and its payment options too. A displayed converted price does not necessarily mean the customer will be charged in that currency.
Choose visible or full-page capture
Use a visible-page screenshot when legibility is the priority and the product name, price, and currency are all in the current viewport. Use a full-page screenshot when surrounding details farther down the page matter, such as product specifications or store context. A full-page image may make the price smaller; check that it remains readable. Firefox also supports selecting a region or an individual page element when a tighter image is useful.
| Need | Capture choice | Check before saving |
|---|---|---|
| Readable price and selector | Visible page, or selected region | Product identity and currency remain in frame |
| Broader page context | Full page | Price is still legible at the saved image size |
| One specific product card | Select the page element if available | The crop includes the currency label, not just the amount |
Make the currency unambiguous
Do not rely on a symbol by itself when it could represent more than one currency. Shopify notes that symbols such as “$” are shared across currencies and documents displaying explicit currency codes to reduce ambiguity. Its theme guidance uses the money_with_currency filter when a theme setting enables currency codes. Shopify storefront settings can also show or hide currency codes with prices. These details describe Shopify themes and storefronts; they are not controls a shopper can necessarily change on every store. See [Shopify’s theme currency-formatting guidance](https://shopify.dev/docs/storefronts/themes/pricing-payments/currency-formatting) and [Shopify’s currency display help](https://help.shopify.com/en/manual/international/pricing/product-prices-by-country).
If the site only shows a symbol, include the selector or nearby country/currency label in the screenshot. When neither is visible, record the selected currency separately with the URL and capture date. For a comparison, capture each currency under the same conditions and label each image clearly.
A screenshot records a displayed price, not necessarily the checkout charge
Currency selectors and conversion tools can affect display without determining the currency ultimately charged. WooCommerce’s documented converter, for example, says its converted prices are informational and that customers pay in the store’s base currency; do not generalize that behavior to other stores or plugins. [WooCommerce documents this converter limitation](https://woocommerce.com/document/multi-currency/).
For merchant listings, Google Merchant Center guidance says the currency should be consistent in product data, on the landing page, and at checkout, and payment must be available in the listed currency. This is merchant listing guidance, not a universal legal rule for every seller. See [Google’s product data specification](https://support.google.com/merchants/answer/7052112).
Adobe Commerce documents a currency chooser for stores that support multiple currencies once rates are updated. That is platform-specific behavior, not a guarantee about every ecommerce page. See [Adobe Commerce currency configuration](https://experienceleague.adobe.com/en/docs/commerce-admin/stores-sales/site-store/currency/currency-configuration).
Automate repeat captures with Firefox
For a one-off capture, Firefox’s built-in screenshot interface is usually the shortest path. For repeated work, use the browser’s screenshot command and keep a small record for every image:
- Product URL and capture date/time.
- Selected product variant and currency.
- Whether the image is visible-page, region, element, or full-page capture.
- Any relevant checkout observation, recorded separately from the screenshot’s displayed price.
Before each capture, wait for the selector interaction and price update to finish. If the site reloads, wait for the resulting page to settle; if it updates dynamically, verify the amount rather than assuming the click succeeded. The Firefox screenshot tool is interactive, so it is suitable for manual captures but not a substitute for a browser automation workflow when you need to process a large list of URLs.
Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server. A single GET request captures a URL as PNG, JPEG, WebP, or PDF. For a product page, first select the desired currency in a normal browser and copy the resulting URL if the selection is represented there. If currency state depends on cookies or an interaction that is not in the URL, configure the request with the needed cookies or use custom JavaScript to select it before capture. Check the result: a screenshot API captures the page state it receives and cannot infer which currency you intended.
See the ScreenshotNeo API documentation for request options. Example using the supplied endpoint and target page:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpimport requests
r = requests.get(
"https://api.screenshotneo.com/v1/shot",
params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
timeout=90,
)
r.raise_for_status()
with open("shot.webp", "wb") as image:
image.write(r.content)const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const image = Buffer.from(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', image));Replace the example target with the product URL. These calls demonstrate a basic capture; add supported options for output format, viewport, wait condition, cookies, custom JavaScript, or other needs using the docs. ScreenshotNeo accepts the parameter names other screenshot APIs use, which can make switching easier.
ScreenshotNeo removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture, and each of those steps can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing; responses identify the page verdict and billing status in X-Page-Verdict and X-Billed headers. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients. The Free plan includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots, and every feature is available on every plan. [Create a free ScreenshotNeo account](https://screenshotneo.com/account/sign-up/) and capture up to 1,000 screenshots a month with no card.
Troubleshooting
| Problem | Likely cause | Fix |
|---|---|---|
| The screenshot shows the old price | The selector did not apply, or the page had not finished updating. | Re-select the currency, wait for reload or dynamic update, confirm the amount on screen, then capture. |
| The image shows “$” but not which dollar currency | The store uses a shared currency symbol without a code or label in the captured area. | Include the selector or currency label; if the page provides no clear identifier, record the chosen currency alongside the URL and date. |
| The currency selector is missing from the image | The selected region or viewport did not include it. | Use a wider visible capture, select a larger region, or use full-page capture if the page layout places it elsewhere. |
| The full-page screenshot is too small to read | The entire page was scaled into one tall image. | Use visible capture for the price or capture a focused region. Keep a full-page image only when its broader context is useful. |
| The captured price differs from checkout | The displayed conversion may be informational, or checkout may use a different currency or include other charges. | Inspect checkout and payment options. Report the screenshot as the displayed page price, not proof of the final charge. |
| Firefox’s shortcut does not open capture | Shortcut behavior can vary by OS, browser version, or keyboard configuration. | Use the page context menu’s Take Screenshot command and consult the current Mozilla instructions for your version. |
| An automated capture lacks the selected currency | The choice may live in browser state, cookies, or an interaction rather than the URL. | Use the site’s supported URL parameter if available, otherwise provide the required cookie or interaction and verify the resulting price. |
Performance, reliability, and cost
For occasional captures, the browser feature has no API setup and lets you inspect the page before saving. Its practical cost is manual time, especially when repeating captures across products or currencies. For repeated URL-based captures, an API can reduce repetitive browser work, but dynamic currency selection may still require state setup and a verification step. Pages with slow scripts or network activity need time to update before capture; capturing too early produces a clean image of the wrong state.
Keep the original URL and capture date because prices, exchange rates, and storefront configuration can change. Keep checkout observations separate from the screenshot. When using a service, review response status and any documented verdict or billing headers so a failed or blocked page is not mistaken for a valid price image.
FAQ
Can a screenshot prove what currency I will be charged?
No. It records what was displayed. Check checkout and payment options to determine the transaction currency.
Should I use the currency symbol or ISO code?
Prefer a visible code or explicit currency label when symbols can be shared. Keep the selector in frame if the page does not show a code.
Should I capture the whole page?
Only when surrounding context matters. A visible capture is often easier to read for a single price.
Can I automate screenshots for many currencies?
Yes, but each capture must reach the intended currency state first. Use a URL, cookie, or scripted interaction as the store supports, then verify the displayed amount and label.
