Back to all docs
Creator workflow

Game Uploads and Manifests

How to prepare an upload package, metadata, SDK scopes, tags, artwork, and creator attestations.

uploadmanifestcreator

Manifest fields

A game manifest is the public-facing metadata and review record for an uploaded game. Keep it factual and player-readable; do not put secrets, credentials, or private account data in any manifest field.

  • slug - lowercase URL id, for example my-first-game.
  • title - max 80 characters.
  • description - max 600 characters.
  • ownerUid - Firebase Auth uid of the creator.
  • status - draft, in_review, needs_changes, or published.
  • visibility - private or public.
  • engine - HTML5, Phaser, Unity WebGL, or Other.
  • tags - up to 12 short tags.
  • requestedScopes - up to 17 valid SDK permission scopes.
  • build, cover, banner - uploaded package and artwork metadata.
  • legalAttestations - rights, malware, external calls, and guideline confirmations.

Upload limits

The current upload wizard accepts a build file up to 100 MB. This keeps uploads fast and review workload under control.

Uploads are saved as drafts first. Creators cannot self-publish. Qubiz publishes after review.

  • Build files: max 100 MB.
  • Tags: max 12.
  • Requested scopes: max 17.
  • Creator legal attestations must all be true before upload.
  • Published games are the only game pages included in the public sitemap.