Practical guide

Keep Unicode and structured fields in exports

Preserve Japanese, Arabic, accents, arrays, and grouped attributes across exports.

Practical details

Preserve Japanese, Arabic, accents, arrays, and grouped attributes across exports.

JSON and Markdown are UTF-8 text, while CSV adds a UTF-8 BOM. Japanese, Arabic, accented European text, commas, quotes, and embedded newlines remain encoded rather than transliterated.

ASINtoJSON handles one product at a time. It does not provide bulk lookup, a public developer API, review text, live price or inventory, historical monitoring, sales estimates, or a complete variation graph.

Use this page

  1. Download JSON, CSV, and Markdown from the same fixed non-English snapshot.
  2. Open the files as UTF-8 and retain the CSV BOM.
  3. Keep arrays and grouped attributes structured instead of transliterating their values.

Field and freshness notes

  • Results can be cached and are not guaranteed to be real-time.
  • Unavailable source fields are shown as not provided; currency identifies the marketplace currency and is not a price quote.

Working example

The fixed snapshot on the multiple-image example page demonstrates the current normalized fields and exact exporters. It was collected on October 4, 2026; it is a snapshot, not a live result.

Frequently asked questions

Does Keep Unicode and structured fields in exports start a live lookup?

Using the form starts one single-product lookup, except the URL-to-ASIN parser, which runs locally without fetching product data.

Are results real-time?

Not necessarily. Successful results may be served from cache, and the displayed fetched time identifies when the product data was collected.