> For the complete documentation index, see [llms.txt](https://docs.gocipher.gg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gocipher.gg/cipher-guides/guide-or-game-asset-uploads.md).

# Guide | Game Asset Uploads

<mark style="color:$info;">**Built your game in Cipher Game Builder?**</mark> \ <mark style="color:$info;">**Nice! Now let's make sure it looks incredible when you publish it.**</mark>

{% hint style="info" %} <mark style="color:$info;">Not done with your game creation yet? We recommend you to check out:</mark> \
\
[<mark style="color:$primary;">**1. Getting Started**</mark>](/cipher-tutorials/1.-getting-started.md) <mark style="color:$info;">to learn more about the tools you'll be mastering;</mark>\
[<mark style="color:$primary;">**2. Creating Your First Game**</mark>](/cipher-tutorials/2.-creating-your-first-game.md) <mark style="color:$info;">to get your first game up and running;</mark> \
[<mark style="color:$primary;">**3A. Improve Your Game Via Design Studio**</mark>](/cipher-tutorials/3a.-improve-your-game-via-design-studio.md) <mark style="color:$info;">to perfect your game manually;</mark>

[<mark style="color:$primary;">**3B. Improve Your Game Via Cyra**</mark>](/cipher-tutorials/3b.-improve-your-game-via-cyra.md) <mark style="color:$info;">to perfect your game through chat</mark>

[<mark style="color:$primary;">**5. Publishing and Sharing Your Game**</mark>](/cipher-tutorials/5.-publishing-and-sharing-your-game.md) <mark style="color:$info;">where you'll be launching it to gamers around the world!</mark>&#x20;
{% endhint %}

When you submit your game for review, you'll get to upload a set of visual assets: a cover image, a banner, screenshots, and videos. These are what players see when they discover your game in the store, search results, and featured sections.&#x20;

This guide covers the exact specs for each asset, what makes them look great, and how to avoid common mistakes.

***

### Quick Reference

Here are our recommendations at a glance:

<table><thead><tr><th width="119.61328125">Asset Type</th><th width="95.75390625">Aspect Ratio</th><th width="101.94921875">Formats</th><th width="133.80078125">Dimensions</th><th width="88.46484375">Max. Size</th><th width="122.2578125">Required</th></tr></thead><tbody><tr><td>Cover</td><td>3:4</td><td>JPG, PNG, WebP</td><td>900 × 1200 px</td><td>10 MB</td><td>Yes</td></tr><tr><td>Banner</td><td>21:9</td><td>JPG, PNG, WebP</td><td>1680 × 720 px</td><td>10 MB</td><td>Yes</td></tr><tr><td>Screenshots</td><td>16:9</td><td>JPG, PNG, WebP</td><td>1280 × 720 px</td><td>10 MB each</td><td>Min 1, max 8</td></tr><tr><td>Video</td><td>16:9</td><td>MOV, MP4, WebM</td><td>Any</td><td>70 MB</td><td>No (max 2)</td></tr></tbody></table>

***

### Before You Submit

Quick checklist before you hit upload!

**Images**

* [ ] Cover image is 3:4 portrait, at least 900×1200 px
* [ ] Banner image is 21:9 ultrawide, at least 1680×720 px
* [ ] At least 1 screenshot at 16:9, at least 1280×720 px
* [ ] All images are JPG, PNG, or WebP
* [ ] Every image file is under 10 MB

**Content Rules**

* [ ] Cover has your game logo as the biggest text element
* [ ] Banner does NOT have your game logo on it
* [ ] Screenshots show actual gameplay from the current build
* [ ] No watermarks, store badges, or platform logos on any asset

**Video (Optional but recommended)**&#x20;

* [ ] Format is MOV, MP4, or WebM
* [ ] File is under 70 MB
* [ ] Shows real gameplay, not cinematics or trailers

**Text (when publishing your game)**

* [ ] Game Name (max 30 characters)
* [ ] Game Description (max 250 characters)

All good? Let's go! 🎮

***

### <mark style="background-color:purple;">**Game Cover**</mark>

**This is the big one.** Your cover is the very first thing players see when they discover your game. It shows up on the Store, your Game Page, Search Results, and Featured sections.

Think of it like an album cover, it needs to hit instantly!

<table><thead><tr><th width="191.8359375">Asset</th><th width="168.3984375">Value</th></tr></thead><tbody><tr><td>Aspect ratio</td><td>3:4 (portrait)</td></tr><tr><td>Dimensions</td><td>900 × 1200 px</td></tr><tr><td>Accepted formats</td><td>JPG, PNG, WebP</td></tr><tr><td>Max file size</td><td>10 MB</td></tr></tbody></table>

#### What Makes a Great Cover?

Your game logo should be the biggest, most visible thing on the cover. Behind it, use actual in-game art or key art that shows what your game looks and feels like.

> **Quick tip:** Remember, players are scrolling through a grid of other games. Your cover design aims to grab their attention!

#### ✅ Do

* Put your game logo or title front and center as the biggest element
* Use recognizable in-game art, a main character, or key art behind the logo
* Stick to your game's actual colors and visual style
* Design for small sizes! Your cover shows up tiny in grids and carousels
* Keep the area behind your logo text clean so it stays readable

#### ❌ Don't

* Use stock images, fan art, or random placeholder art that doesn't represent your game
* Slap on platform logos, age ratings, or store badges (Steam, Epic, etc.)
* Make anything bigger than your game title
* Add watermarks or promo text like "Coming Soon!" or "Play Now!"
* Use art that looks completely different from the actual game

#### 🚫 Not Accepted

These will get flagged:

* Watermarks or promo text baked into the image
* Content violating Cipher community guidelines
* Placeholder art that doesn't represent the actual game
* Platform logos or store badges
* DLC or season covers uploaded to the base game page

> <mark style="color:$info;">💡</mark> <mark style="color:$info;"></mark><mark style="color:$info;">**More Tips**</mark> \
> \ <mark style="color:$info;">**Choosing a file format:**</mark> <mark style="color:$info;"></mark><mark style="color:$info;">PNG works best when your cover has sharp logo text or flat colors. JPG is better for painterly or photo-style art. WebP is a great all-rounder that keeps file sizes small!</mark>
>
> \ <mark style="color:$info;">**A simple layout works too:**</mark> <mark style="color:$info;"></mark><mark style="color:$info;">Not sure how you'd like your game cover? Start simple! Use a strong central character, and a logo above or below - it reads well even at tiny sizes!</mark>\
> \ <mark style="color:$info;">**Stand out in the grid:**</mark> <mark style="color:$info;"></mark><mark style="color:$info;">Pull up the Cipher Store and look at your cover sitting next to other games. Does it pop or does it disappear?</mark>&#x20;

***

### <mark style="background-color:purple;">Game Banner</mark>

The banner is the wide cinematic visual that shows up on the Overview Header, Discovery Feed, and Featured Collections. It's what pulls players in with atmosphere and vibe before they even open your game page.

**The big rule: no logo on the banner!** The platform handles your game title. The banner is all about your game's world, mood, and key art.

<table><thead><tr><th width="191.8359375">Asset</th><th width="168.3984375">Value</th></tr></thead><tbody><tr><td>Aspect ratio</td><td>21:9 (ultrawide)</td></tr><tr><td>Dimensions</td><td>1680 × 720 px</td></tr><tr><td>Accepted formats</td><td>JPG, PNG, WebP</td></tr><tr><td>Max file size</td><td>10 MB</td></tr></tbody></table>

#### What Makes a Great Banner?

Think of it like this - Your cover is the close-up, while your banner is the wide shot. They should feel like they belong together!

#### ✅ Do

* Use an extended or wider crop of the same key art from your cover
* Focus on atmosphere, environment, or key characters
* Match the color palette and mood of your cover so everything feels connected
* Leave breathing room at the edges for cropping

#### ❌ Don't

* Put your game logo or title on the banner (the platform handles that!)
* Use a totally different art style or color scheme from the cover
* Add UI elements, HUD overlays, or screenshot text
* Push important content (character faces, key objects) to the far edges

> <mark style="color:$info;">💡</mark> <mark style="color:$info;"></mark><mark style="color:$info;">**More Tips**</mark> \
> \
> **Easy workflow:** Design your cover first, then extend the same canvas wider for the banner. Same art... wider frame!&#x20;
>
> **Show off your world:** If your game has strong environments (landscapes, cities, dungeons, space), the banner is where to flex them. \
> \
> **Keep important stuff away from the edges:** The banner gets cropped differently depending on screen size, so anything near the borders might get cut off.

***

## <mark style="background-color:purple;">Game Screenshots</mark>

Screenshots on the Game Page and Discovery Feed show players what your game actually looks and plays like. No marketing spin please - Just real gameplay!&#x20;

<table><thead><tr><th width="191.8359375">Asset</th><th width="168.3984375">Value</th></tr></thead><tbody><tr><td>Aspect ratio</td><td>16:9 (landscape)</td></tr><tr><td>Dimensions</td><td>1280 × 720 px</td></tr><tr><td>Accepted formats</td><td>JPG, PNG, WebP</td></tr><tr><td>File size</td><td>10 MB per image</td></tr><tr><td>Required</td><td>At least 1</td></tr><tr><td>Quantity</td><td>Up to 8</td></tr></tbody></table>

#### What Makes Great Screenshots?

#### ✅ Do

* Use actual in-game screenshots from the current build
* Show variety! Different environments, mechanics, characters, moments
* Capture at the highest resolution your game runs at (1920×1080 or higher)
* Include at least one screenshot of core gameplay in action
* Think about order. Your first screenshot is the hook!

#### ❌ Don't

* Use pre-rendered cinematics or concept art as "screenshots"
* Add watermarks, channel branding, or promo overlays
* Include menus, loading screens, splash logos, or debug info
* Upload screenshots from an old build that doesn't match the current game
* Fill all 8 slots with the same angle or scene. Variety!

> <mark style="color:$info;">💡</mark> <mark style="color:$info;"></mark><mark style="color:$info;">**More Tips**</mark> \
> \
> **First screenshot = everything:** It's often the only one players see before deciding to click or keep scrolling. Make it your most visually striking gameplay moment!<br>
>
> **Hide the HUD:** If your game lets you turn off the UI, do it when taking screenshots. Cleaner shots look way more polished and keeps the focus on your game art!\
> \
> **Show your game's range:** Different environments, elements, mechanics, and gameplay features can make players feel like there's a lot to explore. For example, day/night cycles, multiple biomes, or even weather.
>
> \
> **Provide clarity, not confusion:** Your screenshots back up the promise your cover and banner make. If your cover says "dark fantasy RPG" but your screenshots look like a colorful puzzle game, players will feel misled!<br>
>
> **Use all 8 slots!** More screenshots = more confidence that your game is real and worth trying. Fill them if you can!

***

### <mark style="background-color:purple;">Game Video</mark>

Uploading videos bring your game to life in a way screenshots can't. Movement, pacing, the actual feel of playing. Even though this is optional, it is super powerful - If you've got great gameplay, show it off!

<table><thead><tr><th width="191.8359375">Asset</th><th width="201.73828125">Value</th></tr></thead><tbody><tr><td>Aspect ratio</td><td>16:9 (landscape)</td></tr><tr><td>Accepted formats</td><td>MOV, MP4, WebM</td></tr><tr><td>File size</td><td>70 MB</td></tr><tr><td>Required</td><td>No, but recommended</td></tr><tr><td>Quantity</td><td>Up to 2</td></tr></tbody></table>

#### ✅ Do

* Show actual gameplay. Not cinematics. Not trailers. Real gameplay!
* Lead with the most exciting moment in the first few seconds
* Make it watchable on mute. Not everyone has sound on!
* If possible, make the ending flow back into the beginning for a clean loop

#### ❌ Don't

* Include menus, loading screens, splash logos, or studio intros
* Add captions, watermarks, or your channel branding
* Use footage from an old build that doesn't match the current game
* Go over the 70 MB file size limit

> <mark style="color:$info;">💡</mark> <mark style="color:$info;"></mark><mark style="color:$info;">**More Tips**</mark> \
> \
> **Short and punchy wins:** 10 to 15 seconds of peak gameplay beats 60 seconds of wandering around. Every time!<br>
>
> **Show off the best moment:** If your game has satisfying hits, puzzle solves, or building mechanics that snap together, open with those. They hook instantly.
>
> **Got two video uploads? Use them both!** One for core gameplay, one for a different mode, feature, or environment. Show players there's more to discover.

***

### <mark style="background-color:purple;">FAQ</mark>

<details>

<summary>Can I update my cover after uploading?</summary>

Yes! Update it any time from your game's asset settings. If you've refreshed your branding or released new art, keep your cover current.

</details>

<details>

<summary>Does my cover and banner need to match?</summary>

They should feel like the same game. Ideally the banner is a wider crop of the same key art from the cover. It keeps everything looking cohesive as players move from discovery to your game page!

</details>

<details>

<summary>What if I don't have a logo yet?</summary>

Use your game title as big, clean text on the cover. A simple typographic treatment works fine. Just make sure the title is the most visible thing on there!

</details>

<details>

<summary>Can I use AI-generated art for my cover?</summary>

Yes! As long as it actually represents what your game looks and feels like. Don't use generic AI art that has nothing to do with the actual gameplay experience.&#x20;

</details>

<details>

<summary>My screenshots look different from my cover art. Is that okay?</summary>

Covers are art. Screenshots are gameplay. They'll naturally look different. But they should still feel like the same game. If your cover is dark fantasy and your screenshots look like a colorful puzzle game, that's going to confuse players!

</details>

***


---

# 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.gocipher.gg/cipher-guides/guide-or-game-asset-uploads.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.
