What happens between the moment a developer finishes a build and the moment a player installs it? That gap shows why itch.io, GOG, and the Epic Games Store work like three different shops with three different jobs. One platform is a self-serve upload page. Another is a curated catalog built around offline installers. The third is a closed store tied to a mandatory launcher and a fixed revenue split. For players, the differences appear as patch timing, install friction, and library clutter. For developers, they decide who controls the listing, the price, and the pace of updates.
This guide breaks down those workflows step by step, flags the numbers most likely to shift before 2027, and points out the practical mistakes people make when they assume all three stores behave the same way.
The Short Version: Three Different Jobs
Before the details, name the core difference. These stores differ in kind, and a percentage does not capture that difference.
| Platform | Who controls the listing | How a release ships | Client required? | Revenue model |
|---|---|---|---|---|
| itch.io | The creator | Direct upload, often a zip or browser build | No | Creator-set share |
| GOG | The platform, via curation | Versioned offline installers, optional Galaxy | No | Revenue share plus curation |
| Epic Games Store | The platform, via a developer portal | Launcher-managed download and updates | Yes, with limited exceptions | Fixed store cut |
Read that table as a map of who holds the keys. On itch.io, the creator holds them. On GOG, the platform holds them but hands out DRM-free copies. On Epic, the platform holds them and the launcher enforces the rules.
itch.io: Publishing as a Self-Serve Act
itch.io has operated on an open-submission model since its founding in 2013. Anyone can create a project page and upload builds without an approval queue. There is no gatekeeper deciding whether a game belongs on the store. The platform’s own creator documentation walks through project creation, uploads, and pricing options, and it reads like a tool manual rather than a submission contract.
What the workflow looks like
- Create a project page and set the title, description, and tags.
- Upload a build, which can be a downloadable zip, an HTML5 bundle that runs in the browser, or both.
- Set a price, including zero, or use a pay-what-you-want model.
- Choose the share the platform takes, which creators can configure rather than accept as fixed.
- Push a new build directly to the page when a patch is ready.
That last step is the real workflow story. A hotfix on itch.io can go live the same day it is compiled. No certification queue, no store processing window, no launcher deployment lag. For small teams running rapid iteration, that alone can decide where a game lives during early access.
Where people go wrong
The most common mistake is treating itch.io as a lesser storefront rather than a different distribution tool. Developers sometimes upload a single monolithic build with no version notes, then wonder why players report bugs that were fixed days earlier. Practical habit that works: label each upload with a version number and a short changelog, and keep the browser build in sync with the downloadable one. Players who try a game in a browser tab and later download it expect the same version.
A second mistake is assuming the default revenue share is the only option. Because creators set the share, the number is a choice, not a policy. Anyone quoting a percentage for itch.io should attach a date to it, since the default and the interface have changed over time.
GOG: Curation Plus DRM-Free Delivery
GOG launched in 2008 as Good Old Games and built its identity on two promises: a curated catalog and DRM-free games. Titles go through an internal curation and quality process rather than open self-publishing. That changes the workflow from the first email. A developer does not simply upload and publish; they pitch, get accepted, and then work within the store’s release process. (Money challenge explained savings games actually work)
The installer-first model
GOG sells games as offline installers that do not require the Galaxy client. Galaxy exists and adds features like cloud saves and auto-updates, but it is optional. For build and patch workflow, this matters enormously. Developers ship installers and patches, and players can archive those files indefinitely. A patch typically arrives as a versioned installer or a Galaxy update after store processing.
That processing window is the trade-off. It buys quality control and a catalog that feels deliberate. It costs speed. A developer used to pushing a fix the moment it compiles will find GOG’s cadence slower, and should plan release timing around it rather than against it.
Where people go wrong
The classic error is assuming a GOG release is a copy-paste of a Steam or itch.io build. Offline installers have their own requirements: clean uninstall behavior, save file locations that survive a reinstall, and patch logic that works without a launcher phoning home. Teams that skip this step ship installers that break on update. The fix is boring but effective: test the full install, patch, and uninstall cycle on a clean machine before submitting.
A second error is misreading GOG’s expansion of developer self-publishing tools in recent years as a move to an open model. It is not the same as itch.io’s anything-goes upload. Curation remains part of the identity, so confirm the current submission path rather than assuming.
Epic Games Store: Launcher-Centric by Design
The Epic Games Store requires the Epic Games Launcher for purchases and play, with limited exceptions. That single fact shapes every workflow downstream. Developers submit through Epic’s developer portal, and Unreal Engine titles can lean on engine-integrated tooling. Updates flow through the launcher, which means the platform controls the delivery mechanism end to end.
The revenue split and what it signals
Epic’s revenue split is 88/12 in the developer’s favor for store sales, a figure the company has publicized since around 2018 and 2019. Compared with the creator-set share on itch.io, this is a fixed structural term. The split is generous by industry standards, and it is also non-negotiable in the way that platform-wide policies tend to be.
Scheduling constraints
Epic has run periodic exclusivity and free-game programs that affect release timing and storefront obligations. These programs are a scheduling constraint that simply does not exist on itch.io’s open model. A developer planning a 2027 launch has to decide whether to accept those terms, and program names and conditions change frequently enough that no article should state current terms without a fresh source.
Where people go wrong
The most frequent miscalculation is underestimating launcher dependency in player support. When a player cannot install a game, the troubleshooting path runs through the launcher, not the developer’s own download page. Teams that write support docs assuming a simple zip download end up fielding tickets they cannot resolve.
The second is treating the 88/12 split as the whole financial picture. It is the store cut, not the total cost of a release. Exclusivity timing, free-game promotions, and regional pricing all shape the actual outcome.
Patch Cadence: The Difference Players Feel
Players rarely read revenue splits. They do notice when a fix takes three days on one store and three hours on another. The cadence difference follows directly from the models above.
- itch.io: builds go live when the creator uploads them.
- GOG: patches ship as versioned installers or Galaxy updates after store processing.
- Epic: updates flow through the launcher on the platform’s schedule.
This is analysis rather than a cited policy, but it follows from how each system is built. A developer running a live-service game with weekly hotfixes will feel the friction most on the curated and launcher-managed stores. A developer shipping a finished single-player title once will barely notice.
For players, the practical tip is simple: check the version number, not the store page’s last-updated date. Stores display update information inconsistently, and a page can look current while the build behind it is a week old.
Pricing, Fees, and Who Sets the Terms
Fee structures differ in kind; amount is only part of the difference. itch.io lets the creator set the platform’s share. Epic applies a fixed 12% store cut. GOG combines a revenue share with curation. Framing the comparison as “who controls listing, pricing, and patch cadence” is more useful than lining up percentages, because percentages move and control structures tend to persist.
That framing also explains why developers often ship on more than one store. itch.io is the fast lane for early builds and experimental work. GOG is the archive-quality release for players who want to own files. Epic is the volume play with a favorable split and a launcher audience attached. None of these is strictly better; they answer different questions.
If the money side of game platforms interests you, the shifting economics of app store fees are worth following, including how the Apple EU app store fees for game developers in 2026 are reshaping payout math, and what the Apple scotus 27 percent app store fee 2026 dispute means for platform cuts generally. The same questions about who sets the percentage show up on every storefront.
Practical Habits That Survive Platform Changes
Platform terms shift. Workflow habits that hold up across all three stores are worth more than any single policy detail.
- Keep a version manifest. Every build you upload anywhere should carry a version number and a changelog. This is the single highest-value habit for multi-store releases.
- Test the install path, not the build alone. A zip, an offline installer, and a launcher download fail in different ways. Test each one on a clean machine.
- Write store-specific support docs. Launcher troubleshooting, installer repair steps, and browser build quirks are different problems.
- Date every number you quote. Revenue shares and submission rules change. “As of” is not hedging; it is accuracy.
- Plan release timing around the slowest pipeline, not the fastest. If GOG processing takes longer, build that into the schedule instead of discovering it in launch week.
Players can apply a version of the same discipline. If you are tracking free giveaways and release calendars, a regularly updated Epic games free games list is more reliable than memory, and the upcoming Switch 2 games calendar shows how release-date tracking works across platforms. The same patience pays off when hunting for classics, which is why a curated best N64 games list still circulates among collectors who care about which version they are actually getting.
Two more habits worth adopting: keep local notes on which build you installed where, since a workflow comparison between tools like Obsidian and Logseq for local-first notes shows how much friction a good record-keeping system removes, and treat network problems as a separate troubleshooting layer, because the practical guide to fixing packet loss in games covers the connection issues that players often blame on the store.
What to Watch Before 2027
Three things are most likely to change, and all three deserve a fresh check before any 2027 purchase or launch decision.
First, revenue shares. The itch.io default and Epic’s fixed cut are the numbers most likely to have moved. State them with a date and a source, or do not state them.
Second, self-publishing rules. GOG’s and Epic’s submission processes have shifted repeatedly. Terms from 2024 should not be presented as 2027 terms.
Third, program terms. Exclusivity and free-game programs change names and conditions often. Anyone planning a launch around them needs current documentation, not a blog post from two years ago.
What is unlikely to change is the underlying shape: an open upload page, a curated DRM-free catalog, and a launcher-locked store. Those structural differences drive the workflows, and workflows are what developers and players actually live with day to day.
Conclusion
The itch.io vs GOG vs Epic Games Store comparison is less about which store is best and more about which workflow fits the job. itch.io hands the creator the controls and rewards speed. GOG trades speed for curation and gives players files they can keep. Epic offers a favorable split inside a launcher-managed store with scheduling strings attached. A developer who understands who controls the listing, the price, and the patch cadence can plan a release that uses each store for what it does well. A player who understands the same things knows why a fix arrives at different times on different platforms, and stops blaming the wrong party. Check the version number, date every percentage, and plan around the slowest pipeline. Those three habits will outlast whatever the platforms change next.
FAQ
Is itch.io really open to anyone?
Yes. itch.io has run on an open-submission model since 2013, meaning anyone can create a project page and upload builds without an approval queue. That is a structural difference from GOG’s curated catalog and Epic’s developer portal process. The trade-off is visibility: with no gatekeeper, discovery depends heavily on tagging, community sharing, and the creator’s own audience.
Does GOG require the Galaxy client to play games?
No. GOG sells games as offline installers that do not require the Galaxy client, which is optional and mainly adds conveniences like cloud saves and automatic updates. For developers, this means shipping installers and patches rather than relying on a mandatory launcher. For players, it means the files can be archived and reinstalled years later without a platform login.
What is Epic Games Store’s revenue split?
Epic’s split is 88/12 in the developer’s favor for store sales, a figure the company has publicized since around 2018 and 2019. That is a fixed platform-wide term rather than a negotiable one. Because platform terms change, anyone quoting the number in 2027 should confirm it still applies and note whether exceptions exist.
Why do patches arrive at different times on different stores?
The timing follows from each store’s delivery model. itch.io builds go live when the creator uploads them. GOG patches ship as versioned installers or Galaxy updates after store processing. Epic updates flow through the launcher. A live-service game with frequent hotfixes feels this most; a finished single-player release barely notices.
Can a developer set their own price on itch.io?
Yes. Creators set their own price, including zero, and can use pay-what-you-want models. They also configure the share the platform takes, which is why itch.io’s revenue model is described as creator-set rather than fixed. The default percentage and interface have changed over time, so confirm current figures before quoting a specific number.
What should developers check before a 2027 release?
Three things: current revenue shares, current self-publishing rules, and current program terms for exclusivity or free-game promotions. GOG’s and Epic’s submission processes have shifted repeatedly, so 2024-era terms should not be treated as 2027 terms. The safest habit is to verify each detail against current platform documentation and date every number in your planning notes.
