Skip to main content

Where Summer stands

Summer Engine has no console export of its own. It exports Mac, Windows, Linux, web and mobile builds, and Summer Games runs your game on iPhone, Android, Mac and Windows. Nintendo Switch, PlayStation and Xbox versions are made outside Summer. Console SDKs are under NDA. Only developers that Nintendo, Sony or Microsoft approve get them. So a console version always needs:
  • approval from the platform holder (Nintendo, Sony or Microsoft);
  • the platform’s SDK and its dev kit hardware;
  • a console port of the engine, from a licensed porting studio or your own approved team;
  • the platform’s certification, and age ratings.
Summer Engine is built on Godot 4. Porting studios that have shipped Godot games on consoles can work with a Summer project.
We cannot give you console SDK files or get around platform NDAs. You get approval from Nintendo, Sony or Microsoft yourself, or you work with a studio or publisher that has it.

Two ways to get a console version

1. Work with a porting studio or publisher (most common)

Most indie console versions go this way. The studio or publisher already has the approvals, the SDKs and the dev kits.
  1. You provide: your game and its project, usually after a PC release.
  2. They handle: the console port, optimization, certification, and often publishing.
  3. You agree terms: a flat fee, a revenue share, or both. Terms differ a lot, so compare offers.
Some publishers fund the console port in exchange for a revenue share. They usually look for a game that already did well on PC. Questions about a console port? Email founders@summerengine.com with your game’s name and the consoles you want.

2. Apply to the console programs yourself

Each program usually asks for:
  • a registered company;
  • a pitch: what the game is, with screenshots or a trailer;
  • your team’s experience and release plan.
Once approved, you get the SDK, dev kit access and the platform’s documentation. You then still need a console port of the engine, which a porting studio usually supplies.

Certification

Each platform tests your game before release. Plan for these:

Technical

  • Performance: a steady frame rate on the console’s fixed hardware.
  • Memory: stay within the console’s memory limits.
  • Controllers: full gamepad support. No keyboard or mouse needed.
  • Save data: follow the platform’s save rules.
  • Suspend and resume: the game survives sleep mode.

Content

  • Age ratings: each platform and region needs one. Many digital stores use the IARC questionnaire; some regions and physical releases need a full ESRB, PEGI or other board rating.
  • Content rules: no content the platform forbids.
  • Localization and accessibility: some platforms or regions ask for them.
If the game fails a test, you fix it and submit again. Plan for several months from approval to release, and more for your first console game.

Should you release on consoles now?

Good reasons

  • Your game plays well with a controller.
  • It already did well on PC or mobile.
  • You have the budget and the time for approval, porting and certification.

Reasons to wait

  • It is your first game: release on PC first.
  • It needs a keyboard and mouse.
  • It is still early in development.
Most indie developers release on PC first (Steam, itch.io or Summer Games), prove the game, and then port to consoles with the revenue and the track record.

Questions?

Discord Community

Ask about console publishing in #game-dev

Start with PC publishing

Export for Mac, Windows, Linux and the web

Publish on Summer Games

Players on iPhone, Android, Mac, Windows and the web