# Port a game to console > Every console platform gates access. Approval, an NDA covered SDK, dev kits, and certification come before any build reaches a store. - URL: https://www.summerengine.com/port-a-game-to-console - Keyword: port a game to console - Related: https://www.summerengine.com/porting Porting a game to console requires approval from each platform holder, access to their SDK and dev kits under NDA, and passing their certification process. No engine offers a public one click console export, and the rules are the same for every engine. Approval is a business relationship rather than a purchase. You apply to Nintendo, Sony, or Microsoft with your studio details and your game, and they decide. A shipped title, a funded project, or a publisher attached makes approval far more likely. Once approved, everything about the platform toolchain is confidential, which is why public documentation ends at the application form. Summer Engine has no console export of its own. It is written in C++ with GDScript for gameplay, plus C# in the desktop editor, and it exports desktop builds you can ship on Steam while you pursue approval. What you can act on today is portability and budgets, and that is most of the work anyway. ## Approval and dev kits Each platform runs its own developer program with its own portal, agreements, and dev kit purchase. Applications ask for studio information, financial stability, prior releases, and a description of the game. Dev kits are hardware you buy or lease and must keep secured. Access is per platform, so being approved by one holder does not help with another. Most small teams launch on PC first to build the case for approval. ## Design for a controller and a television Console players sit farther from the screen and hold a gamepad. Text needs to be readable at three metres, UI needs focus based navigation with no cursor, and every action must be reachable from a controller including text entry. Support controller disconnect and reconnect mid game. Handle suspend and resume. Respect safe areas on televisions that overscan. None of this requires an SDK, and doing it early removes most of the console specific work later. ## Certification requirements you can anticipate Certification is a long checklist of platform behavior: save data handling and corruption recovery, user account and profile switching, correct button glyphs and system terminology, error message wording, trophy or achievement rules, network and offline behavior, and age rating compliance. Most failures are small and mechanical. Build the game so these are configuration points rather than assumptions baked into the code, and the pass rate improves sharply. ## Publishers and porting partners A publisher or a specialist porting studio already holds platform relationships, dev kits, and certification experience. They will port and submit the game for a fee, a revenue share, or both. For most small teams this is faster and cheaper than becoming licensed on three platforms. Keep the codebase clean, avoid platform specific shortcuts, and document the input, save, and rendering paths to lower their quote. ## FAQ ### Can any engine export to console without approval? No. Console SDKs are confidential and distributed only to approved developers. Any claim of a public console export button is inaccurate. ### How do I get approved? Apply through each platform developer program with studio details and your game. A shipped title, a working vertical slice, or an attached publisher makes approval much more likely. Launching on PC first is the common route. ### How much does console development cost? Dev kits cost money per platform, certification takes engineering time, and a porting partner charges a fee or revenue share. Budget for hardware, several weeks of compliance work per platform, and age rating fees. ### What can I do before approval? Make the game fully playable on a controller, readable on a television, stable at a fixed frame rate within a modest memory budget, and correct when suspended, resumed, or when a controller disconnects. ### Does Summer Engine support console targets? Not directly. Summer has no console export of its own. Console versions need platform holder approval, NDA SDKs and dev kits, and certification, and indie teams usually go through a licensed porting studio or publisher. Summer covers the rebuild and the desktop release. [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