# Response Encoding and Content-Type

Regardless of any tags in the HTML response body that might specify a different encoding (for example ISO-8859-2), ScraperAPI processes and delivers all content in UTF-8 encoding. This standardization offers several key advantages:

* ��**`Uniform Data Handling:`** UTF-8 encoding avoids issues related to special characters and symbols, making data processing smoother and reducing errors.
* ��**`Compatibility Across Systems:`** UTF-8 is widely supported across various platforms and programming languages, ensuring compatibility and reducing integration challenges.
* 🛠️**`Easier Debugging:`** Consistent encoding simplifies troubleshooting and debugging, as you can expect uniform data format in all your responses.
* ⚡**`Streamlined Development:`** Developers can work with a single encoding format, reducing the need for additional encoding/decoding steps and simplifying the development process.

You only need to refer to the **Content-Type** header in the response to verify this:

**Content-type:** text/html; charset=`utf-8`


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.scraperapi.com/responses-and-formats/response-encoding-and-content-type.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.