Publish Games Without Coding: The Complete 2026 Guide
Step-by-step guide to publishing your no-code game on Steam, Google Play, App Store, and web platforms. Covers platform costs, store requirements, and the exact workflow from finished build to live launch.
You can publish a game built entirely without code to Steam, Google Play, the App Store, and the web — and the entire process takes less than a day of active work. No-code engines like GDevelop, Construct 3, and Egmatic handle the technical build process. Your job is choosing platforms, preparing store listings, and submitting for review.
This guide covers the exact workflow: what publishing actually involves, what each platform costs, and the step-by-step process from finished project to live game. If you are still deciding which engine to use, see our guide on the best no-code 2D game engines first.
What "publishing" a game actually means
Publishing a game is not a single event. It is a sequence of four steps that transform your project from a file on your computer into something players can find and download.
1. Export. Your engine compiles the project into a platform-ready format — an executable for Windows, an APK for Android, or an HTML5 bundle for browsers. Most no-code engines do this with a single button.
2. Prepare a store listing. Every platform requires metadata: title, description, screenshots, tags, age rating, and privacy policy. This is the store page players see before downloading your game.
3. Upload and submit. You upload the build and listing to the platform's developer portal. The platform's review team checks that your game works, meets guidelines, and matches its description.
4. Go live. After approval, your game appears on the store. Players can find it, download it, and leave reviews.
The entire workflow looks like this:
| Step | What you do | Time required |
|---|---|---|
| Export | Click "Build" in your engine | 5–30 minutes |
| Prepare listing | Write descriptions, add screenshots | 2–4 hours |
| Upload and submit | Fill forms on developer portal | 30–60 minutes |
| Review | Wait for platform approval | 1–7 days |
| Go live | Game appears on store | Instant |
The part you control — export, listing, and submission — takes roughly half a day. The waiting part depends on the platform.
Platform-by-platform breakdown
Each platform has different costs, requirements, and audiences. Here is what you need to know about the five most relevant options for no-code developers in 2026.
Web: itch.io — Free, instant, no review
itch.io is the fastest path from finished game to playable product. Upload your HTML5 build, fill in a description, and your game is live within minutes.
Cost: Free. itch.io takes an optional revenue share (you choose the percentage, even 0%).
Requirements: A free account. No developer fee, no review process, no minimum quality gate.
Best for: First launches, playtesting, building an audience before approaching paid platforms.
Limitations: Lower average revenue per player compared to Steam or mobile. Players browse casually — discovery is driven by tags, community recommendations, and game jams.
For a complete guide on how to publish your HTML5 game on itch.io, the official itch.io developers page covers the upload workflow step by step.
PC: Steam — $100 per game, largest PC audience
Steam remains the dominant PC game marketplace. Over 33 million concurrent users browse and buy games daily.
Cost: $100 per game through Steam Direct. This fee is recoupable — once your game earns $1,000 in adjusted gross revenue, the $100 is returned to you.
Requirements: A Steamworks developer account (free to create), a $100 payment per game, and a review process that takes 3–5 business days.
Revenue share: Valve takes 30% of revenue (25% after $10 million, 20% after $50 million in gross sales).
Best for: Games with commercial ambitions on PC. The audience expects polished products — read reviews of similar games to calibrate your quality bar.
PC: Epic Games Store — $100 per game, better revenue split
Epic Games Store has grown significantly as a Steam alternative. It offers a more developer-friendly revenue split.
Cost: $100 per game. Unlike Steam, this fee is not refundable.
Revenue share: Epic takes 12% — the best split among major stores. You keep 88% of revenue.
Best for: Developers who want maximum revenue share. The audience is smaller than Steam's, but growing.
Android: Google Play — $25 once, billions of devices
Google Play reaches over 2.5 billion active Android devices worldwide.
Cost: $25 one-time registration fee for a Google Play developer account. No annual renewal. Once registered, you can publish unlimited apps.
Requirements: A developer account, compliance with Google Play policies, and an AAB (Android App Bundle) file. Starting September 2026, Google will require government-issued ID verification for all developers.
Review: 1–7 days for new accounts. Established accounts often see approvals within 24 hours.
Revenue share: Google takes 15% on the first $1 million in annual revenue, then 30% above that threshold.
Best for: Games targeting mobile-first audiences, especially in regions where Android dominates.
iOS: App Store — $99/year, premium audience
The App Store reaches a smaller but more lucrative audience. iOS players spend roughly 2x more per download compared to Android users.
Cost: $99 per year for the Apple Developer Program. This is an annual subscription — your games remain on the store only while your membership is active.
Requirements: An Apple Developer account, compliance with App Store Review Guidelines, and builds compiled with the latest iOS SDK (a requirement introduced in April 2026).
Review: 24–48 hours on average. First submissions can take up to a week. Apple's review is the most thorough — expect scrutiny of metadata, functionality, and design.
Revenue share: Apple takes 30% of revenue, or 15% if you qualify for the Small Business Program (under $1 million annual revenue).
Best for: Premium games targeting high-spending players in North America, Europe, and Japan.
Cost comparison at a glance
| Platform | Upfront cost | Recurring cost | Revenue share | Time to live |
|---|---|---|---|---|
| itch.io | Free | None | Optional | Minutes |
| Steam | $100/game | None | 25–30% | 3–5 days |
| Epic Games Store | $100/game | None | 12% | 3–7 days |
| Google Play | $25 once | None | 15–30% | 1–7 days |
| App Store | None | $99/year | 15–30% | 1–7 days |
For a first-time publisher on a budget, the minimum viable stack is itch.io (free) plus Google Play ($25). Total cost: $25. Add Steam when your game has proven demand.
Built-in publishing in no-code engines
The no-code engine you chose affects how easy publishing is. Some tools handle the export and packaging automatically; others require more manual setup.
GDevelop — One-click exports
GDevelop exports to HTML5, Windows, macOS, Linux, Android, and iOS from a single project. The export dialog lets you generate platform builds with one click. Android and iOS exports require additional configuration (keystores, certificates), but the engine provides guided setup.
Construct 3 — Browser-based, mobile-ready
Construct 3 runs entirely in the browser and exports to web, desktop, and mobile formats. The mobile export process generates the necessary packages, though you still need developer accounts for Google Play and the App Store to submit.
Egmatic — Multi-platform from one project
Egmatic produces versioned game data that the engine runtime executes across platforms. The editor handles build packaging, and the architecture separates content creation from platform-specific concerns — meaning you design your game once and deploy everywhere without managing separate builds for each platform.
Step-by-step publishing workflow
Regardless of your engine and target platform, the publishing process follows the same general workflow.
Step 1: Finalize your build
Before publishing, make sure your game is complete:
- Test on all target platforms (web, desktop, mobile)
- Fix crashes, soft-locks, and placeholder content
- Set the correct version number
- Remove debug tools and developer cheats
Export the final build from your engine. Label the file clearly — something like mygame-v1.0.0-windows.zip.
Step 2: Create store accounts
Set up developer accounts on your target platforms:
- itch.io — Sign up at itch.io. Free, takes 2 minutes.
- Steam — Register at Steamworks. Pay $100 per game.
- Google Play — Register at Google Play Console. Pay $25 once.
- App Store — Enroll at Apple Developer. Pay $99/year.
Do this early — some accounts require identity verification that can take days.
Step 3: Prepare your store listing
Every platform requires:
- Title and subtitle — Clear, searchable, under 30 characters
- Description — 150–300 words explaining what the game is and why someone should play it. Lead with the core experience, not the backstory.
- Screenshots — 3–10 images showing actual gameplay, not menus or logos. Use the platform's recommended dimensions.
- Tags and categories — Match how players search. "Puzzle," "platformer," and "arcade" are better than generic labels.
- Age rating — Required on all platforms. Answer the questionnaire honestly.
- Privacy policy — Required on Google Play and App Store. Even simple games need one. Use a free generator if you do not have a custom policy.
Step 4: Upload and submit
Upload your build file and store listing to the platform's developer portal. Double-check:
- The build runs without errors on the target platform
- All required fields are filled
- Contact information is correct
- Pricing is set correctly (free, paid, or freemium)
Click submit. The review clock starts.
Step 5: Monitor and iterate
After launch:
- Watch for player reviews and bug reports
- Fix critical issues quickly — stores allow updates
- Respond to reviews where appropriate
- Use analytics to understand where players drop off
Your first version does not need to be perfect. It needs to work, be fun, and be honest about what it offers.
Common mistakes first-time publishers make
Skipping platform-specific testing. A game that works in your editor's preview may behave differently on mobile devices with different screen sizes, touch input, and performance. Test on real hardware before submitting.
Ignoring store guidelines. Each platform has specific rules about metadata, content, and functionality. Read the Steam Direct documentation, Google Play policies, and App Store Review Guidelines before submitting. A rejection costs days.
Publishing without a privacy policy. Google Play and the App Store require a privacy policy URL. If your game collects any data — including analytics — you need one. Free generators exist, but review the output carefully.
Using placeholder content. Store reviewers and players notice placeholder art, "Lorem ipsum" text, and temporary UI. Polish everything visible before submission. First impressions determine whether a player clicks "Download" or scrolls past.
Setting the wrong price. Research what similar games charge on the same platform. A $15 game on itch.io competes with thousands of free titles. A $1 game on Steam looks suspicious to players accustomed to higher price points for quality.
Forgetting about updates. Launching is the beginning, not the end. Plan for at least one update within the first two weeks to address bugs and player feedback. Stores rank active games higher in discovery algorithms.
Which publishing path is right for you?
| Your situation | Recommended path |
|---|---|
| First game, no budget | itch.io (free, immediate) |
| First game, small budget | itch.io + Google Play ($25) |
| Polished 2D game, commercial goals | Steam + Google Play ($125) |
| Premium mobile game | App Store ($99/year) |
| Maximum revenue share | Epic Games Store (12% fee) |
| Want to reach everyone | itch.io + Steam + Google Play ($125) |
Start small. Publish on itch.io first, gather feedback, fix issues, then expand to paid platforms. This approach costs nothing and gives you real player data before you invest in store fees.
Conclusion
Publishing a game without coding is not only possible — it is straightforward. No-code engines handle the technical build, and platform developer portals handle distribution. Your responsibilities are testing your game, preparing an honest store listing, and following platform guidelines.
The biggest barrier for most creators is not technical. It is the decision to ship. Pick a platform, prepare your listing, and submit. Your game will not be perfect, and that is fine. The games that succeed are the ones that reach players — not the ones that stay on your hard drive waiting for one more polish pass.
For guidance on creating a game to publish in the first place, see our guide to making a 2D game without coding and our comparison of cross-platform publishing strategies.
Sources
- Steam Direct app fee — Valve, Steamworks Documentation
- Google Play developer registration — Google Play Console
- Apple Developer Program pricing — Apple Developer
- App Store Small Business Program — Apple Developer
- itch.io developer tools — itch.io
- GDevelop export features — GDevelop Documentation
- Construct 3 platform — Scirra
- Epic Games Store revenue share — Epic Games
- Google Play developer verification requirements 2026 — Android Developers Blog
- Android app publishing guide 2026 — Foresight Mobile
Related Posts
5 Best Ways to Publish Game Multiple Platforms in 2026
Discover the 5 most effective strategies for launching your game across multiple platforms simultaneously — from cross-platform engines to web-based distribution and publisher partnerships.
Android iOS Publishing: Your Complete Strategy Guide
A practical strategy for publishing your game on both Google Play and the App Store. Covers store account setup, submission workflows, review timelines, cost planning, and launch coordination so you can reach every mobile player.
Best No-Code 2D Game Engine for Indie Developers in 2026
Compare the best no code 2D game engines for indie developers in 2026, with practical picks for solo creators and small teams.