The awkward moment when a hobby project starts looking like something you could sell is about to get a little less expensive for some GameMaker developers. The company plans to make its next-generation runtime, GMRT, free for commercial use from 1 January 2027.
The announcement, dated 23 October 2026, covers desktop, mobile, web and GX Games distribution. It removes the requirement to buy a Professional licence for commercial projects using that runtime. Console releases retain a separate gate: an Enterprise licence and approved-developer status.
For a small creator, that’s a welcome piece of clarity. Making a game is already difficult enough without the business model arriving as an extra boss fight just before release.
What is becoming free?
The scope is GMRT, rather than a blanket abolition of every GameMaker licence. A runtime is the technology that executes the game you build; it is distinct from the editor in which you assemble and write it. That distinction is particularly relevant when an engine is introducing a replacement for an established runtime.
GameMaker also promises GMRT source-code access across all tiers. Existing Professional owners will retain commercial distribution rights for the GMS2 runtime and receive access to its source. The company says existing tier prices are unchanged, and describes GMRT as continuing its beta rollout across platforms.
Source access can help a developer investigate a problem or adapt technology to a project. It does not, by itself, establish an unrestricted open-source licence. The announcement is a commercial-use and access policy; developers should still read the applicable terms before redistributing engine code or building a business around modifications.
Don’t mistake January’s policy for today’s licence
The current GameMaker pricing page, checked on 25 October, still describes the free tier as non-commercial and Professional as a one-time commercial licence. It lists the latter at US$99.99; a verified UK checkout price wasn’t available from that page.
That page also contains older wording about a Professional requirement for commercial GMRT releases. The newer, specifically dated announcement sets out the planned January change. Until the transition takes effect, creators should check the terms that apply to their actual release rather than treating a future promise as permission to ship today.
Nor does this announcement mean games made with GameMaker must themselves be free. It concerns the developer’s permission to commercially distribute them. Charging players remains part of the proposition.
A smaller barrier, not a finished production budget
Removing an engine licence purchase can matter most to somebody making their first small commercial game. There may be no publisher advance, no certainty of meaningful sales and no comfortable budget for learning by doing. One less upfront commitment makes experimentation easier to justify.
It won’t erase the cost of development. Art, sound, testing, accessibility, localisation and storefront requirements still need time or money. A free runtime cannot make those jobs disappear, and a game does not become commercially viable simply because its engine costs less.
There’s also a different calculation for an established project. Changing runtimes is a technical decision, not merely an accounting exercise. A team with a working build needs to consider compatibility, export readiness and testing effort. The announcement offers no reason to assume that moving an existing game will be automatic or risk-free.
That is why keeping the GMS2 distinction visible matters. A developer should be able to weigh a stable production plan against a new licensing opportunity without feeling that every current project must immediately migrate.
What players get out of it
Players probably won’t notice an engine licence while they’re enjoying a game. The possible benefit arrives earlier, when somebody decides whether a promising prototype is worth turning into a release.
Lower entry costs can give a creator more room to try. They cannot guarantee originality, quality or successful launches, and there’s no announced requirement for studios to pass savings into lower retail prices.
Still, this is a tangible reduction in one barrier between making something and selling it. January’s policy will be most useful if its licensing clarity is matched by a dependable runtime. For developers contemplating a first commercial release, having that choice is already a meaningful improvement.