> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/overview/the-dashboard/photos-and-sizes.md).

# Photos & Sizes

### Overview

The PodPlay system uses different image dimensions for each photo type. Using the recommended size avoids cropping and ensures the image displays correctly across the App and Web App.

#### Location Pictures

The recommended size for a Location picture is 500x375. Some organizations have multiple venues at different Locations.

<figure><img src="/files/1jKdKW74dUPuIqruEIZ5" alt=""><figcaption></figcaption></figure>

#### Region Pictures

The recommended size for a Region picture is 1060x530. Region photos are only necessary if your organization has Clubs in various states.

<figure><img src="/files/qqviXR4lvZpy57Cc38l5" alt=""><figcaption></figcaption></figure>

#### App Loading Screen

The recommended size for a Loading Screen picture of the iOS and Android Apps is 1050x1050 pixels. This is the first screen a Customer will see when they open the native phone app to “Log in,” and the Customer will see this screen for a brief 0.5 seconds when opening the App after they have logged into their Profile.

<figure><img src="/files/WGAiuFrbAcS14O0lsc8w" alt=""><figcaption></figcaption></figure>

#### Event Pictures

The preferred and most optimal picture size to add to your Events is 1200x630. If you use a different size picture, the PodPlay system will automatically ask you to crop the photo when uploading it to the Event.

<figure><img src="/files/xUV50EwYVUFKiJK46Atm" alt=""><figcaption></figcaption></figure>

Events photos are also visible in Spotlight carousel

<figure><img src="/files/9KOHpWgTY1hXBLQuyH8X" alt=""><figcaption></figcaption></figure>


---

# 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.podplay.app/overview/the-dashboard/photos-and-sizes.md?ask=<question>&goal=<endgoal>
```

`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.