Your Store Page on Arcadible
Arcadible builds your store page from your project: the text from your README, the art from .arcadible/, and the details from arcadible.toml. This page shows where players see each part, in the Arcadible desktop app and on the web, so you can write and draw for each place. Where art appears can change as the store does; provide every piece, and the store shows what fits. The rules for every field are in the manifest reference.
Where players see your game
| Place | What it shows |
|---|---|
| Lists: Explore's Featured and Popular (Popular numbered), the library, a player's games, "More by" you | The poster, with the icon, the title, and the tagline (your genres without one) under it |
| Search results | The icon, the title, the tagline, and Play, with your first three screenshots under it, or the cover without screenshots |
| Your store page | Everything below, from the header down |
| Link previews | The cover |
Arcadible chooses the games in Featured and Popular, and you can ask for Featured (Getting Featured). Only public games appear in the store and in search; unlisted games are playable by link only. See visibility.
Search matches your title first, then your short title, handle, genres, and tagline, then your bio and description. A word's start is enough, so dri finds Star Drift, and a small typo in the title still matches.
Your store page has, in order:
- The header: the icon, the title, the tagline, your genres, and your name as the developer, then Play, Like, and Share, and Manage in Studio for you, or ••• ▸ Report for anyone else. Your splash may fill the header behind the text, and its video may play there once.
- The facts: plays, likes, the audience, the developer, your first genre, and your controls.
- The screenshots, scrolling sideways. Each opens full screen. A screenshot can be an MP4, shown by its first frame with a play mark, and played full screen.
- About: the description, and the audience and AI notices beside it. A long description shows its start, with More to read the rest.
- Information: the developer, genres, controls, orientation, when the game was released and last updated, and the version.
- More by you: your other public games.
Text
- Write a tagline. Up to 30 characters, as the title is (Limits). It's the line under your title everywhere the game is listed, and may be the headline where it's featured. Without one, lists show your genres instead. See
tagline. - Make the bio the pitch. It's shown in About when there's no description, and may appear, cut to two lines, where the game is featured. See
bio. - Lead the description with what the game is. About shows its first lines until a player presses More, so put the premise and controls before credits and patch notes. See
description.
Art
- Keep the icon's subject in the center, inside the edge margin. The store rounds the icon's corners, and shows it as small as 36 CSS pixels in lists. See
icon. - Provide a poster. Lists show the poster. Without one, they show your icon on a tinted background. See
poster. - Provide a cover. Search results without screenshots and link previews show it. See
cover. - Provide a banner. The store may use it wherever wide art fits, such as a featured spot. See
banner. - Keep the splash free of detail. It may appear behind text, as may its video, and it's your game's loading screen while it starts, under your icon and title. See
splashand Initialization. - Keep text out of the art, beyond the title on the cover, banner, and poster. The store shows your title and tagline as text beside it. See Text in art.
- Bring the art to life with a video, if you like. Each piece of art can have a video, which may play once in its place, without sound, and then fade to the PNG. How it ends is up to you. The PNG shows wherever video doesn't.
- Show the banner on GitHub too, with an image as the first line of your README, above the
#title, as the starters do:. The store ignores it there and uses.arcadible/banner.pngitself. See Arcadible Markdown.
Text in art
Art is shown at many sizes, down to a thumbnail, and the store shows your title and tagline as text beside it.
- Icon and splash: no text. The icon may be shown as small as a list row, and the splash may sit behind text, your title's included on the loading screen.
- Cover, banner, and poster: the title at most. A stylized title or logo is fine. Leave out taglines, slogans, credits, and other small text.
Edge margin
The store may crop art to fit a place, or draw over its edges behind a fade. The edge margin keeps what matters in view wherever the art appears:
- The edge margin: keep the subject, the title, and anything else that matters at least 10% of the art's shorter side in from every edge, the same distance on all four sides. Let the art itself run to the edges.
- Inside it, compose freely. Place the title and subject where they suit your art, not in a fixed spot.
The recommended sizes are about twice what the store draws, so art stays sharp on high-density screens. At those sizes:
| Art | Recommended size | Edge margin |
|---|---|---|
| Icon | 1024 × 1024 | 102 px |
| Cover | 1536 × 1024 | 102 px |
| Banner | 3360 × 1680 | 168 px |
| Poster | 1024 × 1536 | 102 px |
| Splash | 1920 × 1080 | 108 px |
| Screenshots | 1920 × 1080, or 1080 × 1920 for a portrait game | — |
Screenshots have no edge margin: they're gameplay, framed as you capture it. The starters' placeholder art is drawn at these sizes, with the edge margin marked, so you can paint over it.
Screenshots
- Show real gameplay in screenshots and the trailer, and start the trailer with play rather than logos.
- Name screenshots
screenshot_<number>. Only those files appear on the store page, ordered by number. Other gallery files are for the description. See Screenshots. - Put your best three first. Search results show the first three under your game.
- Add phone screenshots named
screenshot_<number>_phone, taken on a phone in the game's orientation: landscape for a landscape game, portrait for a portrait one. Phones show only those when there are any, so make them a full set, videos included. A tablet counts as a phone when its browser says it's a mobile device; an iPad's Safari doesn't, so iPads show the others. See Screenshots.
Details
- List your main genre first. The facts show the first genre, and the game may appear on the page of every genre you list. See
genres. - Set
audienceandaito match the game. The store shows the audience as a notice on your store page, and labels agenerativegame. Seeaudienceandai. - Declare every input the game supports. The facts and Information list them as the game's controls. See
inputs.
Choosing an audience
audience is everyone or mature, and choosing is a judgment call:
- Rate the most intense content a player can reach, not a typical session. A graphic scene late in the game counts as much as the opening minutes.
- Consider how content is presented. Stylized, comic, or fantasy conflict usually fits
everyone. Realistic or lingering violence, gore, sexual content, and frequent strong language usually point tomature. - Include everything the game can show: cutscenes, dialogue, audio, and any text or images that players share with each other.
- When you're unsure, choose
mature. Players who seeeveryoneexpect that label to hold. - Update it with the game. If an update adds more intense content, change the audience in the same release.
Disclosing AI
ai answers one question:
Did generative AI create content that players can see or hear, before release or while they play? Then it's
generative, which the store page labels. Otherwise, it'sunused.
- AI used as a tool doesn't count, such as to help write code for a game you designed.
- A game an agent made counts: the agent created what players see and hear, its text and levels included, whether as files or in its code.
- Edited still counts. Content generative AI created, then edited or painted over by hand, is
generative. - Set it explicitly. Left out, no label is shown, but the game's AI use is recorded as
unknown.
Declaring inputs
inputs lists how the game can be played, and the store page shows them as its controls:
- List each input that can play the whole game by itself. A game that plays with the keyboard alone and with the mouse alone lists
keyboardandmouse. - Use
keyboard-mouseonly when the game needs both at once, such as moving with keys while aiming with the mouse. - Support every input you list. See Best Practices.
Before the first release
Only release versions change the store page. A staging build doesn't, so a prerelease shows nothing early: until a game's first production release, its store page shows only its name and "Not released yet". Logged in as its developer, you also see that the first production release publishes the page, with Manage in Studio.
To see what a prerelease would publish, open the game's Store tab in Arcadible Studio and choose Staging. See Releases.
Checklist
- A tagline, and a bio that reads as the pitch in two lines
- A description that starts with the premise and controls
- An icon with its subject centered, and no text
- A cover, a banner, a poster, and a splash, at the recommended sizes, with what matters inside the edge margin
- Screenshots named
screenshot_<number>, the best three first, and, if any, a full set of_phoneones taken on a phone, in the game's orientation - The main genre first, and
audience,ai, andinputsset to match the game