> For the complete documentation index, see [llms.txt](https://docs.onside.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onside.io/console/marketing-and-promotion/landing-page-asset-requirements.md).

# Landing Page Asset Requirements

What to send Onside when we create a distribution landing page for your app.

If Onside is creating a distribution landing page for your app, send the assets below.

### Logo or app icon

Provide your logo or app icon in one of these formats:

* **Vector preferred:** `SVG`, `PDF`, or `AI`
* **Raster:** `PNG` or `JPG` with a minimum width of `1024 px`

Use a clean export:

* No background
* No shadows
* No raster effects

### Cover image

This is the main visual at the top of the landing page.

Provide a desktop cover image with these specs:

* **Formats:** `.jpg`, `.webp`, or `.png`
* **Aspect ratio:** `5.03:1`
* **Minimum resolution:** `1440x286`

### Screenshot carousel section

Provide `4–6` key images for the screenshot carousel.

Use these rules for all carousel images:

* Use the same aspect ratio across all visuals
* **Portrait recommended:** `19.5:9`
* **Landscape recommended:** `9:19.5`
* **Formats:** `.jpg`, `.webp`, or `.png`

### Description

Provide a short description for the landing page:

* `1–2` short sentences
* Maximum `160` characters
* Focus on user benefit, not product features
* Use a friendly, confident, and conversational tone

### Writing principles

Follow these rules for the description:

* **User-first perspective:** describe what users gain
* **Light, modern tone:** keep the copy human
* **Value-driven language:** use active verbs like `Enjoy`, `Bring back`, `Stay updated`, `Keep both`, and `Upgrade easily`

### Submission checklist

Before you send assets, make sure you have:

* A logo or app icon
* A cover image
* `4–6` screenshot carousel images
* A short landing page description


---

# 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.onside.io/console/marketing-and-promotion/landing-page-asset-requirements.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.