MakeGameWithAI
中文
Menu

Rosebud AI

Turn a small game idea into something you can play, change and share.

Evidence statusPublic-evidence reviewMedium confidenceLast checked Sep 7, 2026By MakeGameWithAI
Visit official websiteSee the evidencePrototyping & Coding

PRODUCT OVERVIEW

What Rosebud AI is—and how it works.

Rosebud AI is a browser-based game-creation workspace. You describe an idea or start from a template, let its AI generate code and arrange assets, then play the result in a preview. The output is an interactive game—not just a design document or an image of a game.

Its product covers 2D and 3D games, with natural-language edits and asset upload or generation in the same workflow. A practical starting point is a small single-player game: movement, one interaction and a score or win/lose condition. Play it, describe what should change and build up the rules in small steps.

You can share a browser link, and official documentation describes a paid Windows build that includes editable source. Those files can support further development outside Rosebud, but they are not a native Unity or Godot project. Export permissions and the current commercial tier need checking before choosing a paid route.

HOW YOU USE IT

Use the browser workspace and the account/allowance it requires. Check My Plan before relying on a free allowance, buying a subscription or planning a source/EXE download; the current prices and minimum eligible tiers were not confirmed.

Describe or remix a starting point

Start with a template or a small game brief, then inspect the playable result. You do not need to build a local engine project first.

O01O02

Iterate through play and feedback

Request a rule, control or interface change, then check it in the preview. Small changes make it easier to notice regressions.

O13U01

Work with game assets

Upload or generate assets and use them in the project. Asset appearance, usage rights and gameplay behavior remain separate checks.

O02U01

Share, then consider exporting

Share a Web link, or use the documented paid Windows route. Source files enable further editing, not guaranteed engine portability or agent access.

O01O07O08

INTERFACE & EXAMPLES

See how it works

3 images
The official editor image places the Rosie conversation beside a playable game preview.Open larger
Interface

The official editor image places the Rosie conversation beside a playable game preview.

Official source retrieved September 2026; interface version not specified.Source: Rosebud AI
The official editor image places the Rosie conversation beside a playable game preview.
Source: Rosebud AI
REVIEW SCOPE

A first small, non-confidential browser-game prototype and its iteration path. Commercial release, large projects, multiplayer backends, export reliability and performance are outside the supported conclusions.

Beginner friendlinessBeginner friendly
Browser templates, natural-language edits and immediate previews lower the barrier to a first small game; complex features and debugging still require learning and judgment.
Agent integrationNo confirmed entry point
Public sources do not establish an interface for an external agent to create, edit and retrieve games; editing exported source is not the same as calling Rosebud.
Scope, integration requirements and sourcesChecked

Beginner scope: A first small single-player browser-game prototype for someone without a coding background, not a commercial-release pipeline.

Agent scope: An external agent calling the Rosebud creation service and obtaining the resulting game files.

Confidence: learning Medium · Agent Medium

Access
No documented public authentication or task endpoint was confirmed. The documented path is the browser workspace; undisclosed enterprise access was not evaluated.
Billing
External-service pricing and limits are unknown. Current Web plan entitlements are also unresolved; Web credits must not be treated as API credits.
Getting results
No programmatic submit/status/result contract was confirmed. The paid Windows guide describes selecting a project, requesting a build in the UI and receiving files by email.
Limitations
The Terms restrict automated access. Agent-related marketing and Code3DBench research code are not a Rosebud API. A missing public entry does not prove that no interface exists.

These are independent editorial judgments, not an overall score or a claim of hands-on agent integration testing.

KEY FINDINGS

What the evidence supports—and what it does not.

01
Editorial inferenceMedium confidence

A first playable version is a realistic starting goal

An independent walkthrough shows incremental 2D feature work, and a devlog describes a creator with limited coding knowledge starting with Rosebud. These support the entry point, not a promise that every beginner finishes a polished game.

O02O13U01U02
02
User reportsMedium confidence

Growing the project can change the workflow

Some authors continued in Cursor or Codex after the initial Rosebud work; another manually optimized a small game's performance. These are mixed-tool cases, not Rosebud-only production proofs or a current failure-rate estimate.

U02U03U07
03
Official factHigh confidence

The public plan descriptions do not support a reliable quote

Official pages use both prompts and credits, and one guide contains incompatible Pro descriptions. We did not obtain the current My Plan table, so no historical price or allowance is presented as today's entitlement.

O03O04
04
Editorial inferenceMedium confidence

Exported code is not an interface to Rosebud

The documented Windows route provides source files, while agent-related articles and the research repository do not establish a callable creation service. Our public-source search found no confirmed API, MCP, CLI or SDK for creating, editing and retrieving Rosebud games.

O07O10O11O12

EDITORIAL VERDICT

Our take

Medium confidence

Rosebud is worth considering if you want to begin making a playable game without learning an engine or coding first. Its value is the short loop from an idea to something you can try and change. Keep that first project small, and treat source export as an optional next step—not a promise that complex development, commercial rights or automation are already solved. Before paying, resolve the plan conditions that matter to your project.

Conclusion scopeA medium-confidence public-evidence assessment of the starting workflow. No current success rate, fixed cost per game or production recommendation is implied.

BETTER FIT

Worth auditioning when

  • First-time creators who want to turn a small idea into a playable browser game.
  • Creators testing a mechanic before committing to a larger project.
  • Creators comfortable playing each revision and describing concrete changes.
  • Small personal interactive projects that can begin without confidential assets.

POORER FIT

Do not depend on it yet when

  • Expecting one prompt to replace game design, testing and long-term maintenance.
  • Needing a confirmed API/MCP pipeline to generate and retrieve games automatically.
  • Depending on native engine projects or a guaranteed commercial-release workflow.
  • Uploading client secrets or requiring exclusive ownership without resolving the applicable terms.

WORKFLOW FIT

Where it fits in a production workflow.

01

Explore one mechanic

Start with movement and a single interaction, then add a simple score or ending so someone can play a complete loop.

GuardrailUse original or clearly licensed, non-confidential inputs and keep the first scope small.
02

Refine through play

Change one rule or interface element at a time and check existing behavior after each edit.

GuardrailSet a time and spending limit. Save usable checkpoints rather than assuming the next rewrite is always better.
03

Choose the next development route

A shareable browser version may be enough. If you need source or Windows output, confirm the plan and then assess the actual exported project.

GuardrailLocal coding tools work on those files; that is not a verified automated Rosebud integration or native engine migration.

RECOMMENDED WORKFLOW

Your AI-made game has a bug. How do you fix it without knowing code?

Three playable debugging exercises show how to describe a fault, limit an AI repair, check the result and recover a working version. Includes broken and fixed examples, six screenshots, templates and source.

Read the related guide

SHORTEST RESPONSIBLE PATH

Start with one playable loop, not a full release plan.

This is a low-risk starting workflow synthesized from the evidence.

  1. 01

    Choose a non-confidential personal idea with one clear interaction.

  2. 02

    Check the current allowance and relevant rights in My Plan before spending or uploading assets.

  3. 03

    Start from a suitable template or describe movement, the interaction and a win/lose condition.

  4. 04

    Play each revision and ask for one specific change; keep a working checkpoint.

  5. 05

    Share the browser result first. Check source/EXE permissions, rights and actual output before committing to a paid migration.

PRICING & RIGHTS

Check the current plan before budgeting a game.

Pricing and terms last checked: Sep 7, 2026

  • Current prices and allowances are unconfirmed. Official help points to My Plan, while public guides retain conflicting prompts, credits and plan descriptions.
  • Official Windows instructions require a paid plan, but do not settle the lowest eligible tier or a separate source-download entitlement.
  • Task/model/context metering, retry refunds, rollover and top-ups were not confirmed. Do not assume an unused or unsuccessful result costs nothing.
COST TO OUTPUT

From one edit to a finished game: the missing cost inputs

The representative task is a small single-player 2D prototype with movement, feedback, a feature revision and a shareable result. Current price, allowance and task consumption are not jointly verified, so no numerical output promise is made.

O03O04O07U02
One generation or editNot currently calculable

Nominal allocation = monthly price ÷ included credits × task credits. The current inputs are missing; one prompt is not a fixed-cost game.

A playable prototype workflowNo confirmed monthly yield

Include first generation, revisions, assets, debugging and any build charge. Theoretical runs = floor(available credits ÷ workflow credits), not accepted games.

An accepted gameActual cost unknown

Add rejected attempts, human time, other coding tools, purchased assets and hosting. Mixed-tool project spending cannot be treated as a Rosebud-only average.

Historical prices are deliberately omitted from this page. Even a verified credit allocation would not establish quality, an acceptance rate or the number of release-ready games you will obtain.

Commercial-use condition

The Terms restrict free use to personal, non-commercial purposes. Paid commercial permission is not the same as exclusive ownership: the Terms and ownership FAQs differ, and the minimum commercial tier remains unconfirmed. Check the applicable terms before selling a game.

Use My Plan and the applicable contract to resolve the tier, export and rights conditions first. A payment or an export alone is not proof that every asset is licensed or a release is ready.

PRODUCTION RISKS

Resolve these before production use.

Confidential inputs and data use

The Privacy Policy covers prompts, code, media and logs, with the same practices for free and paid users. It permits anonymized/aggregated data uses including external training and research; do not assume a subscription provides a no-training guarantee.

O05O06

Rights need more than a marketing FAQ

Commercial permission, output ownership and rights to uploaded assets are separate questions. Resolve conflicting wording before depending on exclusivity or client confidentiality.

O05O09

Export is another checkpoint

An EXE does not repair gameplay or packaging issues. Older export complaints predate the new guide; they justify checking your own files, not claiming the current exporter is broken. Networked features can still need external services.

O07O08U04

Do not substitute a workaround for documented access

The Terms restrict automated access. No documented external task interface was confirmed; this page does not recommend session-cookie reuse, reverse-engineered endpoints or bypassing the normal access path.

O05O10O12

NOT VERIFIED

Claims this page does not make

RESEARCH METHOD

Research-reviewed from public evidence

We checked nine platforms and retained six concrete usage accounts plus one public-source artifact across note.com, itch.io, Reddit, GitHub and Hacker News. Reddit supplies three of the six usage accounts; multiple subreddits are one platform. GameDev.net and engine forums were searched but did not add completed-use records. Vendor interviews, same-name products and unverifiable summaries were excluded. Older and undated cases support bounded workflow observations, not current quality consensus. No product generation or export was performed.

Research windowReviewed September 7, 2026. Dated cases span May 2025–January 2026, with an April 2026 indexed complaint and undated records. Historical cases do not establish current model or export performance.
OFFICIAL SOURCES13
  1. O01
    Official
    Rosebud AI Game Creator

    Browser creation, templates, playable 2D/3D games and sharing. Vendor production-volume and quality claims are not independent evidence.

    Checked Sep 7, 2026
  2. O02
    Official
    Rosebud AI game-development workflow

    Describing a game, editing features, working with assets and previewing the result.

    Checked Sep 7, 2026
  3. O03
    Official
    Pricing and subscription FAQs

    Directs readers to My Plan for current plans. Its older prompt allowance and commercial-tier wording do not establish a complete current tariff.

    Checked Sep 7, 2026
  4. O04
    Official
    AI-character guide with conflicting plan descriptions

    The same page contains incompatible Pro prices and credit-versus-unlimited-prompt descriptions. None is presented here as a verified current quote.

    Checked Sep 7, 2026
  5. O05
    Official
    Rosebud Terms of Service

    Revised August 2, 2025. Free/commercial use, generated-content ownership, non-confidential content, platform permissions and automated-access restrictions.

    Checked Sep 7, 2026
  6. O06
    Official
    Rosebud Privacy Policy

    Revised July 25, 2025. Covers prompts, code, media and logs; paid use is not a blanket no-training or confidential-processing promise.

    Checked Sep 7, 2026
  7. O07
    Official
    Download a Rosebud game as a Windows EXE

    A paid-plan cloud-build route delivered by email, including supporting files and editable source. The lowest eligible tier and actual build behavior were not verified.

    Checked Sep 7, 2026
  8. O08
    Official
    Download, run and ship a Rosebud game on Windows

    Windows packaging and further source editing. This is not a native Unity/Godot project or a guarantee of offline operation for connected features.

    Checked Sep 7, 2026
  9. O09
    Official
    Rosebud vibe-coding overview

    Editable browser code and an ownership FAQ whose wording must be read alongside the Terms.

    Checked Sep 7, 2026
  10. O10
    Official
    CLI agents are coming for game development

    Official agent-related positioning, not a documented API, MCP server, SDK or installable task CLI.

    Checked Sep 7, 2026
  11. O11
    Official
    Rosebud Engineering

    Technical articles and maintenance signals, not a public service-integration contract.

    Checked Sep 7, 2026
  12. O12
    Official
    Code3DBench research repository

    Identifies itself as a Rosebud AI research benchmark. It calls other model services and is not a client for the hosted Rosebud game creator.

    Checked Sep 7, 2026
  13. O13
    Official
    A template-led Rosebud game workflow

    Small changes, play checks and checkpoints. A vendor-described starting workflow, not a MakeGameWithAI test.

    Checked Sep 7, 2026
INDEPENDENT EVIDENCE RECORDS7
  1. U01
    Independent walkthrough
    JUN SUZUKI — iterating a 2D survival game

    Shows feature revisions, character changes and imported music; names Sonnet 4.5 at that time. The author's plan and vendor relationship are unknown; the video mirror is not another record.

    Checked Sep 7, 2026
  2. U02
    Community case
    DEBTHOLE — a beginner's mixed-tool devlog

    The author reports limited coding knowledge, starting with Rosebud and continuing with Cursor and purchased assets. Self-promotes the game; vendor relationship is unknown. Total project spending is not a Rosebud-only bill.

    Checked Sep 7, 2026
  3. U03
    Community case
    Silk Road Defenders — moving a prototype to local coding tools

    A self-promotional author account describes moving from RPG Maker to Rosebud and then exported-source work in Codex. Exact date, plan and model are unconfirmed. A demo is not a verified full commercial release.

    Checked Sep 7, 2026
  4. U04
    Community case
    An older credit and export complaint

    Indexed April 21, 2026; reports credit frustration and export issues before the May Windows guides. Plan and relationship are unknown; it does not establish a defect in the current export path.

    Checked Sep 7, 2026
  5. U05
    Community case
    A historical tower-defense prototype comparison

    A 2025 author report describes workable first-pass logic but inconsistent visuals. Exact date, plan and relationship are unknown; unmatched trials are not a controlled ranking or current-model test.

    Checked Sep 7, 2026
  6. U06
    Technical repository
    3D Model Playground — public source

    A developer's HTML/JavaScript project credits Rosebud alongside other tools. It is an interactive experiment, not a complete game or measured export test; plan/date and vendor relationship are unknown. The author promotes their own work.

    Checked Sep 7, 2026
  7. U07
    Community case
    Show HN: Lazy Tetris — creation and manual optimization

    The author used Rosebud and ChatGPT, then manually optimized performance on a laptop. A historical mixed-tool case with promotion of the author's book; plan, coding background and vendor relationship are unknown.

    Checked Sep 7, 2026

DISCLOSURE

How this research was supported

No affiliate link, sponsorship, supplied account, credits or vendor support was used. Some authors promote their own games, tutorials or books; vendor relationships are unknown. Owner Review of the research and both scoped decisions passed on September 7, 2026; pricing gaps remain.

Research review and Owner Review are complete.

This public research review will be revisited when pricing, terms, product versions, or material new evidence changes.

All news