> For the complete documentation index, see [llms.txt](https://docs.legitimate.tech/public-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.legitimate.tech/public-docs/project-docs/required-activation-assets/image-specs.md).
# Image Specs
For the best user experience, we suggest using square photos of at least 1000x1000 pixels in PNG or JPEG formats of no larger than 8MB in file size. Transparency is also supported but please make sure the image works against both dark and light backgrounds.
#### Framing
Whether the picture is taken in portrait or landscape orientation, we want to make sure that the subject (i.e. the product) is focused in the center of the frame. If the camera supports square photos, then the photo does not need to be manually cropped afterward.
#### Editing
The lay-flat photos should have the perspective adjusted if they're not shot exactly from the center
The lay-flat photos should have the perspective adjusted if they're not shot exactly from the center
The item should have its background removed and placed against a transparent canvas for the best visual experience
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.legitimate.tech/public-docs/project-docs/required-activation-assets/image-specs.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.