GameMaker will make GMRT commercial exports free. Choosing a runtime still matters
The January policy removes a license requirement for several platforms, while console access and the older runtime retain distinct conditions.
GameMaker is removing a licensing hurdle for developers who want to sell games built with its next-generation runtime. From January 1, 2027, GMRT will be free for commercial distribution on desktop, mobile, web and GX Games, according to the October 23 announcement. A Professional license will no longer be required for that route.
The date and the runtime are the boundaries of the change. This is an announced future policy for GMRT, which is still rolling out in beta across platforms. It is not a statement that every existing GameMaker project can immediately change its licensing assumptions, or that console publishing has become free.
The runtime is part of the business decision
A runtime is the software layer that executes the finished game. Developers may spend most of their time in an editor, but the behavior and platform support of that underlying layer determine where the project can ship and which problems must be resolved before release.
That makes a runtime migration more substantial than changing a billing setting. A studio with a working game has to consider its extensions, export targets, save handling and testing process. Those are project-specific engineering questions; the announcement does not certify every older project as ready for GMRT.
Existing Professional owners retain commercial distribution rights for the GMS2 runtime and gain access to its source code. GameMaker also says GMRT source access will span all tiers, while existing tier prices are unchanged. The current licensing page remains the place to check the terms that apply before the new policy begins.
Source access is valuable when a developer needs to understand why a game behaves a certain way. It can make a failure less opaque and give a team more options for investigation. But access to source code should not automatically be described as an unrestricted open-source license: modification, redistribution and contribution rights depend on the actual terms.
A lower entry cost does not remove the shipping work
For a small team, eliminating a commercial-license requirement can make it easier to move a prototype into a paid release. It also reduces the need to settle a licensing purchase before a project has demonstrated that it deserves more time. Those benefits are most direct for new projects that can choose GMRT from the outset.
An established project faces a different calculation. Switching purely to avoid a fee can be a poor trade if it creates substantial regression testing shortly before launch. Keeping a stable export pipeline may be worth more than the license saving. This is the same kind of practical distinction behind our coverage of Steam’s Linux architecture transition: a platform change can simplify the future while still creating work for games already built.
The policy has no Italy-specific launch restriction in the announcement, so Italian developers have the same reason to assess it. Store commissions, platform approvals and other distribution costs are separate from GameMaker’s runtime license.
The strongest part of this change is the extra choice it gives a developer before committing to a production pipeline. The right question for an existing game is more exacting: does GMRT remove a constraint that matters enough to justify changing the software underneath it?
