# Port a game to Nintendo Switch > There is no self serve Switch export. Nintendo approves developers, provides the SDK and dev kits under NDA, and certifies every build. - URL: https://www.summerengine.com/port-a-game-to-switch - Keyword: port a game to switch - Related: https://www.summerengine.com/porting Porting a game to Nintendo Switch requires approval as a Nintendo licensed developer, access to the console SDK and dev kits under a non disclosure agreement, and passing Nintendo certification. No engine can hand you a public Switch export button, and any tool claiming otherwise is not describing the real process. What that means practically: you apply through the Nintendo Developer Portal, you get approved or not, and only then do the console specific parts of the toolchain become available to you. Everything after that point is covered by the NDA, which is why public documentation stops there. The alternative route is a porting studio or a publisher that already holds the license and ships the console version for you. What you can do today is build the game so the console step is short rather than a rewrite. Summer Engine exports desktop builds for Steam and itch.io, uses C++ and GDScript with C# in the desktop editor, and leaves you owning the project with no royalties. Summer has no console export of its own, so the Switch version itself goes through your own Nintendo approval or a licensed porting partner. Console readiness is mostly about design and budgets, and that work is entirely under your control. ## How developer approval actually works Apply through the Nintendo Developer Portal with your company details, a track record, and a description of the game. Nintendo reviews the application. Approved developers sign agreements, gain access to documentation and the SDK, and purchase dev kits. Middleware and engine support for the console is distributed to licensed developers, not published openly. Expect the application to be rejected without a shipped title or a credible plan, which is why many teams launch on Steam first. ## Prepare the game before you get access Build to a fixed performance budget on modest hardware. Assume around 1280 by 720 handheld and 1920 by 1080 docked, and make sure the game holds a stable frame rate at both. Keep memory tight. Design the UI to be readable at handheld size, roughly a 6.2 to 7 inch screen at arm length, which means larger text than a monitor needs. Make every interaction controller only, including text entry, menus, and any drag interaction. ## Certification is a checklist, not an opinion Console certification tests behavior, not quality: correct handling of controller disconnect, sleep and wake, user accounts and profile switching, save data rules including corruption handling, terminology for buttons and system features, error messages, and age rating compliance. Failures are usually mundane and fixable. Teams that read the requirements early pass faster, and teams that treat certification as a formality lose weeks. ## Publishers and porting studios Many console versions of indie games are handled by a porting studio or a publisher who holds the platform relationship. They bring the license, the dev kits, and the certification experience, and take a fee or a revenue share. This is a legitimate route and often the fastest one for a small team. Make it cheaper by keeping the codebase portable, avoiding platform specific hacks, and documenting your input and save systems clearly. ## FAQ ### Can I export a Switch build without Nintendo approval? No. Console SDKs are distributed only to approved developers under NDA. There is no public export path for any engine, and no legitimate workaround. ### How do I become a Nintendo developer? Apply through the Nintendo Developer Portal with company information and details of your game. Approval is at the discretion of Nintendo, and a shipped title or a strong prototype improves your chances significantly. ### Does Summer Engine support console? Not directly. Summer has no console export of its own. Console versions need platform holder approval and certification, and are usually handled with a licensed porting partner, while Summer covers the rebuild and the desktop release you can ship first. ### What should I do before I have access? Lock a stable frame rate at 720p and 1080p, keep memory use modest, make the entire game playable with a controller, design UI legible on a handheld screen, and handle sleep, wake, and controller disconnect. ### Is using a porting studio worth it? Often yes for a small team. They hold the platform relationship and know certification, which saves months. The cost is a fee or revenue share, and a portable codebase reduces what they charge. [Start the rebuild](https://www.summerengine.com/download) --- ## Machine-readable resources - Site index for agents: https://www.summerengine.com/llms.txt - Full inlined content: https://www.summerengine.com/llms-full.txt - Porting catalog: https://www.summerengine.com/llms-porting.txt - Structured catalog: https://www.summerengine.com/agent-catalog.json - Sitemap: https://www.summerengine.com/sitemap.xml - Developer resources: https://www.summerengine.com/docs