How to Get Your Indie Game on Consoles

Getting an indie game onto consoles is a sequence of approvals and technical milestones, not a single upload. You register on the platform's developer portal, get accepted as a licensed developer and sign an NDA, receive a devkit and the platform's SDK, build or port your game to it, pass certification, and set up the store page — then launch. Plan for months, not weeks: approval and devkit delivery take weeks on their own, and certification usually needs two or three passes.

Step	What you do	Who controls the wait
1. Engine	Confirm your engine can export to the console	You
2. Register	Apply on the developer portal (ID@Xbox, PS Partners, Nintendo)	You
3. Approve + NDA	Get accepted; sign the NDA; access SDK and dev forums	Platform (1–2 weeks)
4. Devkit	Receive or buy the devkit hardware	Platform (weeks)
5. Port/build	Build the game for the platform (engine export or porting studio)	You
6. Integrate	Controller, saves, achievements, platform UI	You
7. Certify	Pass TRC / TCR / Lotcheck	Platform (days–weeks per pass)
8. Store page	Capsules, trailer, IARC age rating, price, date	You
9. Launch	Release; every patch re-certifies	You

Before you start#

Two things decide whether the rest is smooth or painful.

Your engine must be able to target the console. Console SDKs are NDA-protected, so console export is never free and open the way a Windows build is. Unity requires a Pro subscription and platform approval; Godot needs a commercial partner such as W4 Games; MonoGame has a console runtime used by shipped titles; GameMaker requires its console licensing. If your engine cannot reach the console at all, you are looking at a porting contract, not a build setting. Confirm this before anything else.

A track record helps your application. The portals accept solo developers, but a released game on PC, a studio website, and a real build to show all speed up approval and devkit allocation. Sony in particular has historically asked for proof of a registered company and a document describing the game.

The steps in detail#

1. Confirm your engine targets the console#

This is step zero because it can kill the whole plan. Check that your engine has a console export path and what it costs — a Unity Pro seat, a W4 Games subscription for Godot, or access to MonoGame's console runtime under NDA. If you are not sure, ask the engine's developer relations team directly; the answer is often "yes, under NDA after you are an approved developer," which is fine — just confirm the path exists.

2. Register on the developer portal#

Apply where the platform wants you to:

• Nintendo — Nintendo Developer Portal (developer.nintendo.com). Individuals can register.
• PlayStation — PlayStation Partners (partners.playstation.net). Have company documents and a game description ready.
• Xbox — ID@Xbox (developer.microsoft.com). Generally the most straightforward application.

The form asks for your studio details, website, and released games. Fill it in honestly; a thin application with no released work is the main reason for a slow or silent response.

3. Get approved and sign the NDA#

If the platform accepts you, you sign the developer agreement and an NDA. That unlocks the platform's SDK, the developer forums, and the private tools you need to actually build for the hardware. Expect roughly one to two weeks for a response, though Nintendo can take longer and a second application is sometimes needed.

4. Get your devkit#

You cannot run or debug a console build without devkit hardware. Nintendo loans devkits — you order one for a fixed period, test it, and return it for free or pay to keep it. Sony and Microsoft sell or lease devkits to approved developers. Because demand outstrips supply, there is often a queue; a real, playable build you can show the platform is the fastest way to move up it.

5. Port or build the game#

Now the engineering work begins. If your engine supports the console directly, this is a build target plus platform-specific configuration. If it does not, you contract a porting studio — for a small 2D game, roughly $5,000–$9,000 per platform — and they handle the SDK and performance work under NDA.

6. Integrate platform features#

A console build is more than the same game on different hardware. You wire in controller mapping, the platform's save system, trophies or achievements, user profiles, and the platform UI conventions players expect. Certification checks these specifically, so do not treat them as polish to add later.

7. Pass certification#

Submit your build for certification — Sony's TRC, Microsoft's TCR/XR, or Nintendo's Lotcheck. The platform verifies your game meets its technical requirements: it does not crash, handles the controller and online features correctly, saves and resumes properly, and follows the platform's conventions. Expect to fail the first submission, fix the issues, and resubmit. Two or three passes is normal, and each can take days to weeks.

8. Set up the store page#

While certification runs, prepare the store page: capsule images, a trailer, screenshots, a description, and an age rating. The IARC questionnaire assigns regional ratings for free and is required. You set the price and the release date. A page that is ready when certification passes means you launch on your schedule, not the platform's.

9. Launch — and re-certify every patch#

Once everything is approved, you release. From here the discipline is ongoing: every patch, update, or new build goes through certification again, so keep your submission process sharp rather than treating launch as the finish line.

Timeline and costs#

Phase	Typical time	Typical cost
Application + approval	1–4 weeks	Free
Devkit	Weeks after approval	Loaned (Nintendo) or purchased
Port/build	Weeks to months	~$5,000–$9,000/platform (small 2D) or your own time
Certification	Days to weeks per pass, often 2–3 passes	Your time
Platform cut	Ongoing	~30% of revenue

A realistic end-to-end figure, from approved developer to on the store, is several months for a straightforward 2D port and longer for anything complex.

Self-publish or use a publisher?#

You can do all of this yourself as an approved developer. Many indies instead partner with a console publisher or porting studio that already has devkit access, SDK expertise, and certification experience — trading a share of revenue for months of saved time and fewer failed submissions. This is especially common for a first console release, when the certification learning curve is steepest. The trade-off is the same as any partnership: you give up a cut of revenue in exchange for de-risking a process you have not run before.

Common mistakes#

Mistake	What happens	What to do instead
Starting before checking the engine	You get approved, then discover no console build path	Confirm console export exists and what it costs on day one
Applying with nothing to show	Slow or no response; delayed devkit	Ship on PC first; include a playable build with the application
Treating certification as a formality	Repeated failures, a slipped release date	Read the TRC/TCR/Lotcheck requirements early; pre-audit your build
Forgetting platform features	Failed certification for missing save or controller support	Wire in saves, controller, and achievements before submitting
Underestimating patch re-certification	A day-one fix takes weeks to reach players	Keep the submission pipeline ready; certify in batches when you can

How Egmatic fits#

Because Egmatic runs on the MonoGame runtime — the same runtime behind Stardew Valley on every console — the console build path is the engine's own export, not a separate port. Platform features such as controller input and save systems are handled at the engine layer, so your work is integration and certification rather than rewriting the game for new hardware. The platform's approval, devkit, and certification still apply, as they do for any engine, but starting from a runtime that already ships on consoles is what turns "can we even do consoles?" into a question of schedule rather than feasibility. For the conceptual background — what console publishing is, the revenue split, and the three programs — see our explainer on console publishing, and for desktop and mobile alongside consoles, our multiplatform export guide.

Conclusion#

Getting an indie game onto consoles is a nine-step process: confirm your engine targets the console, register on the developer portal, get approved and sign the NDA, receive a devkit, port or build the game, integrate platform features, pass certification, set up the store page, and launch. Approval and devkit delivery take weeks, certification usually takes two or three passes, and the whole path runs to months, not weeks. The developers who move fastest confirm the engine path first, apply with a real build to show, read the certification requirements before they submit, and keep their patch pipeline ready. Do those four things and the rest of the process is a calendar problem you can plan around — which is exactly how a closed platform is supposed to feel once you know the route.

---

Sources#

1. The console application is a web form — studio details, website, released games — and ID@Xbox is generally the most straightforward to apply to — Game Developer: How to get on consoles as an indie
2. Nintendo Developer Portal — register (including as an individual) and self-publish on the eShop — 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. Nintendo loans devkits to approved developers; Sony and Microsoft sell or lease them — Game Developer: How to get on consoles as an indie
6. Certification requirements: Sony TRC, Microsoft TCR/XR, Nintendo Lotcheck — Microsoft GDK: Console certification requirements
7. Console build paths are NDA-gated: Unity requires Pro; Godot needs a partner like W4 Games — W4 Games: W4 Consoles
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