> For the complete documentation index, see [llms.txt](https://docs.autoenhance.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.autoenhance.ai/file-guidelines/metadata.md).

# Metadata

For optimal results, we recommend uploading all original metadata included in the file captured by the camera. Several features of Autoenhance rely on or enjoy improved performance with this metadata:

1. **Lens Correction**: Requires metadata such as Make, Model, and Lens information to identify the best profile for correcting lens distortion.
2. **Perspective Correction**: Requires lens distortion to have been corrected to make sure it corrects perspectives accurately, this feature requires either the information for lens correction to be available or the metadata that indicates that the image has already been lens corrected (This varies from camera to camera)
3. **HDR Grouping**: Utilizes Date Taken and Exposure Value (This varies from camera to camera) metadata for improving the bracket grouping accuracy for High Dynamic Range (HDR) images.

Including this metadata ensures that our Autoenhance features can apply corrections and enhancements with optimal accuracy and quality.

{% hint style="info" %}
**Metadata on the images we return.** On AI-enhanced downloads we preserve your existing caption, author and copyright, add a standards-based AI-disclosure, and remove GPS/location data for privacy. See [AI Transparency](/ai-transparency.md) for exactly what we write and how to verify it.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.autoenhance.ai/file-guidelines/metadata.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.