Console Publishing for Indie Devs: Switch, PS5, Xbox

Console publishing is the path an indie developer takes to release a game on a closed platform — Nintendo Switch, PlayStation 5, or Xbox Series X|S. Unlike Steam or a mobile store, you cannot simply upload a build: you register as an approved developer, get devkit hardware and the platform's tools under a non-disclosure agreement, build or port your game to that platform, and pass certification before the platform will sell it. Each platform keeps roughly 30% of revenue. The wall between you and the store is what makes consoles harder to reach — and worth reaching.

Platform	Self-publishing program	Where you start	Platform cut (typical)
Nintendo Switch	Nintendo Developer Portal	developer.nintendo.com	~30%
PlayStation 5 / PS4	PlayStation Partners	partners.playstation.net	~30%
Xbox Series X|S	ID@Xbox	developer.microsoft.com	~30%

The exact split on each console is protected by NDA, but the industry-standard platform cut is around 30% — the same order as Steam, Apple, and Google. What sets consoles apart is not the cut. It is the wall.

What makes consoles different#

Steam, the App Store, and Google Play are open platforms. Once you have an account and, on mobile, a developer fee, you upload a build and sell it. Anyone can.

Switch, PlayStation, and Xbox are closed platforms. The hardware, the development tools, and the submission rules are all controlled by the platform holder. To sell a game there you must be accepted as a licensed developer, agree to the platform's terms under NDA, and prove your build meets a long technical checklist before it is allowed on the store. That control is why a console library is smaller and more curated — and why a broken, unfinished game essentially cannot ship there the way it can on an open store.

The trade-off is worth understanding up front: consoles are harder and slower to reach, but the audience is large, willing to pay, and far less crowded with low-quality releases.

The three self-publishing programs#

All three platform holders run a self-publishing program aimed at independent developers. The application is a web form — your studio details, website, and the games you have released. A track record helps, but it is not a hard requirement.

Nintendo — Nintendo Developer Portal#

Nintendo's portal (developer.nintendo.com) is the most accessible starting point. You can register in minutes, including as an individual. Once your game is complete you self-publish on the Nintendo eShop and set your own price and release date. Nintendo notably offers devkits on loan: you order one for a set period, test it, and return it at no cost, or pay to keep it. The revenue split is covered by NDA, with the platform cut around the standard 30%.

PlayStation — PlayStation Partners#

Sony's self-publishing route is PlayStation Partners (partners.playstation.net). You retain your IP and choose your release date. Sony has historically asked more than the others at the application stage — proof of a registered company and a document describing the game you intend to build — though its 2022 indie initiative made devkits available for free to smaller developers. As with the others, the platform cut is roughly 30%.

Xbox — ID@Xbox#

Microsoft's program for independents is ID@Xbox (apply via developer.microsoft.com). It is generally the most straightforward to apply to. One point worth getting right: the 88/12 revenue split Microsoft advertises applies to PC games sold through the Microsoft Store, not to Xbox console games. On Xbox consoles the standard split is the familiar ~70/30.

Devkits and the NDA wall#

A devkit is the development hardware (and its matching software) you need to build, run, and debug a game on a real console. You cannot buy one in a shop. Devkits are NDA-protected and IP-locked: you get access only after you are an approved developer, and the hardware and SDKs cannot be discussed publicly or shared. This is the single biggest reason console development feels opaque to newcomers — most of the useful detail lives behind that agreement.

Acquisition differs by platform: Nintendo loans devkits, while Sony and Microsoft sell or lease them to approved developers. Plan for hardware to arrive weeks after approval, not days.

Certification: TRC, TCR, and Lotcheck#

Before a console will list your game, the build must pass certification — a checklist of technical requirements the platform enforces. Each holder has its own name for it:

Platform	Certification name	What it checks
PlayStation	TRC (Technical Requirements Checklist)	Performance, stability, controller and trophy behavior
Xbox	TCR / XR (Technical Certification Requirements)	Stability, Quick Resume, store integration
Nintendo Switch	Lotcheck	Stability, save behavior, eShop compliance

Certification is not a creative judgment. It checks that your game behaves like a well-behaved console title — it does not crash, it handles the controller and online features correctly, and it follows the platform's conventions. Failing a submission and resubmitting is normal, and most studios budget for two or three certification passes. Every patch after launch goes through the same process.

Costs and revenue#

The platform cut is the headline cost, but it is not the only one:

Cost	Typical figure	Notes
Platform revenue share	~30% to the platform	Same order as Steam; exact console terms are NDA
Devkit	Loaned (Nintendo) or purchased	NDA-protected hardware
Porting (per platform)	~$5,000–$9,000 for a small 2D game	Rises sharply for larger scope
Age rating (IARC)	Free	Required for the store page

If your engine cannot target the console directly, you usually hire a porting studio. For a small 2D title, expect roughly $5,000–$9,000 per platform; larger ports climb to tens of thousands. The International Age Rating Coalition (IARC) questionnaire assigns regional ratings for free and is required for the store page.

Is console publishing worth it for an indie?#

Console publishing pays off when the game is proven elsewhere first. The studios that do well on consoles tend to launch on PC, build an audience, and use that traction to fund and justify the console port. A console release rarely rescues a game that flopped on PC.

It is worth it when:

• Your game is complete and successful on at least one open platform.
• You can fund the port and certification upfront, or partner with a publisher.
• Your genre fits a console audience — platformers, action, roguelikes, and couch co-op historically over-index on Switch.

It is usually not worth it when the game is still an unproven prototype, or when the porting cost would consume most of your runway. In that case, prove the game on PC or mobile first, then bring the console version once the risk is gone.

Common mistakes#

Mistake	What happens	What to do instead
Treating consoles like Steam	You assume a quick upload; reality is months of approval and certification	Budget approval, devkit, and certification time from the start
Picking an engine that can't target consoles	You finish the game, then hit a wall at the port	Confirm console export exists for your engine before committing
No track record or build to show	A slow or silent response to your application	Ship on PC first; show a real build when you apply
Underestimating certification	Repeated failed submissions, a delayed launch	Read the requirements early; run an internal compliance pass
Underfunding the port	Porting cost eats your runway	Get quotes from porting studios before you set a launch date

How Egmatic fits#

Egmatic is a 2D editor and engine built on the MonoGame runtime — the same runtime behind Stardew Valley and many other titles already running on Switch, PlayStation, and Xbox. Because the platform-specific work (controller input, save systems, platform services) sits at the engine layer rather than in your game logic, the path to a console build is the engine's console export, not a from-scratch port. That removes the single biggest porting risk: starting from an engine whose runtime has never run on a console.

Console publishing itself — platform approval, devkit access, and certification — still applies regardless of engine. But beginning from a runtime that already ships on consoles means the engineering work is integration and certification, not a rewrite. For the wider picture of shipping to desktop and mobile alongside consoles, see our multiplatform export guide and our complete publishing guide.

Conclusion#

Console publishing for indie devs is a real, well-trodden path — Nintendo, Sony, and Microsoft all run self-publishing programs any serious developer can apply to. The catch is that consoles are closed: you must be approved, get devkit access under NDA, build or port to the platform, and pass certification (TRC, TCR, or Lotcheck), with the platform keeping roughly 30% of revenue. The studios that succeed prove the game on PC first, fund the port, and budget months for approval and certification. Pick an engine whose runtime already targets consoles, treat certification as a project milestone rather than a formality, and consoles stop being a distant goal and become the next platform on your list.

For the step-by-step process of applying, getting a devkit, and passing certification, see our companion guide to getting your indie game on consoles.

---

Sources#

1. Consoles are closed platforms that require licensed-developer status and devkits under NDA — Game Developer: How to get on consoles as an indie
2. Nintendo Developer Portal — free registration, self-publish on the eShop, set your own price and release date — Nintendo Developer Portal
3. PlayStation Partners — self-publish on the PlayStation Store, retain IP, choose release date — PlayStation Partners
4. ID@Xbox is Microsoft's self-publishing program for independent developers — Microsoft: Publishing pathways — ID@Xbox
5. Microsoft's 88/12 revenue split applies to PC games in the Microsoft Store, not to Xbox console games — Game Developer: Microsoft debated reducing revenue share on consoles
6. Nintendo offers devkits on loan to approved developers — Game Developer: How to get on consoles as an indie
7. Certification checklists: Sony TRC, Microsoft TCR/XR, Nintendo Lotcheck — Microsoft GDK: Console certification requirements
8. Console porting costs roughly $5,000–$9,000 per platform for small indie titles — Polycrunch Games: How much does console porting cost
9. The IARC questionnaire assigns age ratings across regions for free and is required for the store page — International Age Rating Coalition
10. Godot cannot ship console builds from its open-source form because console SDKs are NDA-restricted — W4 Games: W4 Consoles