Remixing forks a game into a new project you own. It’s the fastest way to start from something that already works — a community game whose mechanics you love, or your own game when you want to branch an idea.

​
Remixing someone else’s game

Public games with remixing enabled show a Remix action on their store page and game cards.
  • The fork copies the game itself: all files, assets, and build state.
  • The original creator’s chat history is not copied — their conversation with the AI is private. Your remix starts a fresh conversation.
  • You can add a first prompt right at remix time (“make it sci-fi themed”) — that first build is billed normally.
  • Remixes are labeled as such, crediting the original.
Creators can disable remixing per game — see below.

​
Remixing your own game

Studio menu → Remix forks your own project. Use it to branch experiments (“what if this were multiplayer?”) without risking the original.

​
Controlling who can remix your game

In your game’s settings, Preferences → Allow remixing controls whether others can fork it (you can always remix your own games).
  • Default: remixing allowed.
  • Turning it off requires a paid plan.

​
Remixes and rights

  • What you build on top of a remix is yours; the remix relationship is recorded and displayed.
  • Source export is not available for remixed projects — source export is reserved for original games. Standalone builds (web/desktop) still export fine. See Exports and Ownership & IP.