Upload and submit your game
The provider workspace's actual metadata, artwork, draft and review workflow.
Access
Provider access requires an active verified creator account and a published provider profile owned by it. Staff must assign the provider profile. Staff/creator authentication checks apply, including two-factor requirements. Visit Provider workspace; documentation itself is anonymous.
Required metadata
| Field | Validation |
|---|---|
| slug (new game) | Lowercase letter/digit followed by letters/digits/hyphens, at most 71 characters |
| title | 2–100 trimmed characters |
| description | 20–4000 trimmed characters |
| genre | 1–40 trimmed characters; default Arcade |
| controls | Up to 1000 characters; non-empty before review |
| cover | Uploaded owned image or existing authorized/bundled artwork; required before review |
| inputMethods | 1–3 values: keyboard, touch, mouse |
| devices | 1–3 values: desktop, mobile, tablet |
| Hebrew title / description / controls | Optional, at most 100 / 4000 / 1000 characters |
| multiplayer | Boolean; does not implement networking |
| version | Three numeric components, e.g. 1.0.2, each at most six digits, no leading zeros; higher than active version |
| changelog | Optional, up to 1000 characters |
| entrypoint | index.html |
No mandatory trailer, screenshot count, icon or source-code upload is enforced by this submission schema. Do not treat optional assets as requirements.
Cover preparation
Provider image upload accepts PNG, JPEG or WebP. The image must decode as a still image, contain no more than 24 million pixels, and be larger than 12 bytes and at most 5 MiB. The implementation does not enforce a particular aspect ratio. Use a clear cover that remains readable in catalog crops and preview it in the form. Use your own uploaded image or existing allowed artwork; arbitrary external cover URLs are not a substitute for ownership checks.
Save, upload, preview, submit
- Select an owned game or create a new draft in the provider workspace.
- Fill metadata and control instructions, upload/select cover artwork, and save a semantic version higher than the published version.
- Upload the immutable runtime ZIP against the saved draft. Its version must match the draft.
- Open the isolated package preview. The signed preview URL expires after 15 minutes. It loads the package but does not issue player rewards or act as the regular gameplay parent responder.
- Submit the saved package and metadata snapshot for review. Pending/approved submissions are locked. A rejected/requested-changes submission can be edited and resubmitted.
- Staff review verifies ownership, provider state, revision/release and the live-game snapshot, then approves through the CMS publication workflow.
Conflicts and retries
The form uses request IDs, draft revisions and a live-game token to avoid duplicate submissions and overwriting concurrent edits. A version change after upload requires a matching package. If another editor changes the game, reload and review the current snapshot; do not blindly overwrite it. Metadata history/rollback and package rollback are separate actions.
Event registration is a separate prerequisite
The current submission workflow does not auto-create event definitions from an uploaded manifest or inspect SDK calls for compliance. Ask staff to publish your agreed event schemas before live testing. Passing ZIP validation or obtaining approval does not by itself prove every event is accepted.