> 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

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

Complete assets speed up production and reduce back-and-forth.

### 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

### Main promo section

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

Video works best. Image is also supported.

#### Desktop asset

* **Video recommended:** `.mp4` or `.webm`
* Aspect ratio: `16:9`
* Resolution: `1920x1080` or higher

If you send an image:

* Format: `.jpg`, `.webp`, or `.png`
* Aspect ratio: `16:9`
* Resolution: `1920x1080` or higher

#### Mobile asset

* **Video recommended:** `.mp4` or `.webm`
* Aspect ratio: `9:16`
* Resolution: `1080x1920` or higher

If you send an image:

* Format: `.jpg`, `.webp`, or `.png`
* Aspect ratio: `9:16`
* Resolution: `1080x1920` or higher

### Key features section

Provide `4–6` key features for your product.

Each feature should include:

#### Visual

* Use the same aspect ratio across all feature visuals
* Recommended ratios: `4:3` or `1:1`
* Formats: `.jpg`, `.webp`, or `.png`

#### Title

* Use Title Case
* Keep it short
* Maximum `5` words
* Make it action-oriented
* Make sure it still makes sense out of context

Examples:

* `Keep Both Apps`
* `Real-Time Calls`
* `Instant Alerts`

#### Description

* Write `1–2` short sentences
* Keep each description under `160` characters
* Focus on user benefit, not feature mechanics
* Use a friendly, confident, and conversational tone

### Writing principles for feature cards

Follow these rules for each card:

* **User-first:** explain what users gain
* **One benefit per card:** focus on one clear use case
* **Light and modern tone:** keep the copy human
* **Punchy pacing:** keep sentences short and rhythmic
* **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 desktop promo asset
* A mobile promo asset
* `4–6` feature visuals
* `4–6` feature titles
* `4–6` feature descriptions


---

# 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:

```
GET https://docs.onside.io/console/marketing-and-promotion/landing-page-asset-requirements.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.